Probably because the safeguards would have to be part of the analog amplification circuit, and anything extra that you put there will potentially hamper sound quality.
This is why the safeguards are generally found in mid-range systems only. High end amps are engineered to not damage themselves in the presence of DC output into speakers which potentially offer only 1 or 2 ohm of DC resistance, and assume that you will match the amplifier with similarly well-engineered speakers. Low end amps skip them to save cost (as in the Dell case).
separately, what does everybody mean about VLC doing clipping of the waveform for movies? I don't understand this.
Many movies available on the net have the sound recorded too low. So VLC comes with an option to boost the audio beyond what is normally available from the PC's volume control by digitally boosting the level before passing it to the sound card. If this is used on a movie where the audio level is not recorded too low, then clipping can result, which can potentially destroy speakers and amps.
When I went there to see what the fuss was about, it was stories over 33% of the width, ads and other sidebar content 25%, and massive amounts of whitespace in between and at the sides.
JIT compilation happens the first time you run code. Its the runtime optimizations that require code to be run thousands of times so the VM can tell which code paths need optimising the most.
A lot of the people in that sector are utterly redundant.
I'm not so sure about that these days. Banks have rationalized their workforces, they just haven't passed any of the savings from that onto their customers, instead using it to fuel ridiculous bonus schemes for the employees they have left (except for the frontline retail staff, who are as underpaid as ever).
It eliminates it from devices on your network. But your devices still need to play nice with your neighbours' networks on the same channel. Part of the problem I think is that 802.11b wasn't really designed to play well with different networks operating on the same channel in close proximity. So later standards need to detect 802.11b traffic and avoid it - which means slowing down due to gaps in the communication at least.
Apple first-gen Airport cards cant connect to any 802.11n router whatever mode its in,
Realtek by any chance? I have an internet radio with an Realtek 802.11b USB dongle embedded. It crashes as soon as it sees any 802.11n router. For a while I was able to get by with running my router on channel 1 with n disabled so it would find it and connect before it got around to scanning my neighbours' routers, but eventually my neighbours figured out that it was pretty congested on channel 6, and started switching channels on their routers too.
With weak signals over long distances they'll get a better connection using g or n protocols at low speed than falling back to b protocols.
I was surprised by this story, because I have my router set to g/n only (I probably could switch to n only now I think about it, as my wife's laptop was the last g holdout, and got upgraded last year) and thought that was a standard option on most routers these days.
You can't just relicense someone elses work. BSD lets you release binaries without the source, or linked with GPL code, but the original source code is still BSD licensed. So it wouldn't be LLVM-NG(GPL), it would be LLVM(BSD) + NG(GPL) and proprietary vendors could still extract the BSD licensed portions to modify and close off at their will.
It kinda made sense back then, IE 6 and ActiveX was actually superior to Netscape and Java plug-in (or whatever it was).
It was superior to the 40-bit export quality encryption that US-based suppliers were allowed to include in their browsers (the US relaxed its export laws before the ActiveX controls gained widespread deployment, but with the momentum of a government project and the factor of national pride in having a homegrown encryption standard, they couldn't put the brakes on). But they could just as well have bundled it as an extension to SSL rather than a separate ActiveX plugin.
Per device fees don't really hurt the newcomers as much as the upfront certification fees and industry body membership fees that they already had. $0.75 per device is $0.75 whether you already sell millions of devices, or you are just starting out.
Good luck explaining to customers why a large number of third party apps that rely on Google APIs suddenly won't work on your new phones. They would be better off switching platform entirely than trying to fork Android.
They weren't charging per device before, just requiring membership of OHA and requiring the device to be certified as passing some tests to ensure compatibility.
$0.75? How about you leave that out and I'll take it for $2.00 less? How does that logic work?
Profit margins and overheads for manufacturer, distributor and retailer. That's about the right ratio by the time this gets to retail shelves. Except that at retail they'll likely want to round it to XX9.95 or XX9.99, so the end effect on the price is either $0 or $10.
Nexus 5 has dedicated voice recognition hardware that listens even when the main CPU on the phone is in sleep mode. It can wake the main CPU when it hears a magic phrase ("OK Google"). Google Now isn't listening on the mic though - if the magic phrase has not been detected, the audio never leaves the dedicated voice IC.
When more people use taxis, it will make more sense to provide more of them, so there is more chance that one is nearby when you want it. At peak times it makes more sense to use buses (where trains are not available).
The protesters are part of a group that are upset about gentrification. In the event that you don't know what that is, I'll explain since all the posters so far clearly didn't read the actual article (another day on/.). Quite simply -- it's when people with significant wealth and/or income move into an area of people with less wealth/income and thereby drive up real estate prices beyond what the established population can potentially afford.
It's sad for the people who are driven out, but this process is basically what stops cities from becoming Detroit. Regular renewal is needed to keep cities alive.
As there seems to be quite a buzz around the "internet of things" right now, why not leverage your existing expertise by focusing on that rather than mobile and web. Focus on web services rather than web pages, familiarize yourself with HTTP rather than HTML and stick with C and maybe Java and Python (a lot of "embedded" devices are running Linux under the hood and some Android, and other uses of Java such as Bluray get embedded) as higher level languages that are less stressful to code networked apps in than pure C or even C++.
Slashdot Mirror
This is why the safeguards are generally found in mid-range systems only. High end amps are engineered to not damage themselves in the presence of DC output into speakers which potentially offer only 1 or 2 ohm of DC resistance, and assume that you will match the amplifier with similarly well-engineered speakers. Low end amps skip them to save cost (as in the Dell case).
Many movies available on the net have the sound recorded too low. So VLC comes with an option to boost the audio beyond what is normally available from the PC's volume control by digitally boosting the level before passing it to the sound card. If this is used on a movie where the audio level is not recorded too low, then clipping can result, which can potentially destroy speakers and amps.
When I went there to see what the fuss was about, it was stories over 33% of the width, ads and other sidebar content 25%, and massive amounts of whitespace in between and at the sides.
Please put beta.slashdot.org behind a paywall and keep those who don't pay on the classic site.
JIT compilation happens the first time you run code. Its the runtime optimizations that require code to be run thousands of times so the VM can tell which code paths need optimising the most.
I'm not so sure about that these days. Banks have rationalized their workforces, they just haven't passed any of the savings from that onto their customers, instead using it to fuel ridiculous bonus schemes for the employees they have left (except for the frontline retail staff, who are as underpaid as ever).
It's only more efficient for low speed and weight. Aircraft are still better off with current designs.
It eliminates it from devices on your network. But your devices still need to play nice with your neighbours' networks on the same channel. Part of the problem I think is that 802.11b wasn't really designed to play well with different networks operating on the same channel in close proximity. So later standards need to detect 802.11b traffic and avoid it - which means slowing down due to gaps in the communication at least.
Realtek by any chance? I have an internet radio with an Realtek 802.11b USB dongle embedded. It crashes as soon as it sees any 802.11n router. For a while I was able to get by with running my router on channel 1 with n disabled so it would find it and connect before it got around to scanning my neighbours' routers, but eventually my neighbours figured out that it was pretty congested on channel 6, and started switching channels on their routers too.
[citation needed]
With weak signals over long distances they'll get a better connection using g or n protocols at low speed than falling back to b protocols.
I was surprised by this story, because I have my router set to g/n only (I probably could switch to n only now I think about it, as my wife's laptop was the last g holdout, and got upgraded last year) and thought that was a standard option on most routers these days.
You can't just relicense someone elses work. BSD lets you release binaries without the source, or linked with GPL code, but the original source code is still BSD licensed. So it wouldn't be LLVM-NG(GPL), it would be LLVM(BSD) + NG(GPL) and proprietary vendors could still extract the BSD licensed portions to modify and close off at their will.
It was superior to the 40-bit export quality encryption that US-based suppliers were allowed to include in their browsers (the US relaxed its export laws before the ActiveX controls gained widespread deployment, but with the momentum of a government project and the factor of national pride in having a homegrown encryption standard, they couldn't put the brakes on). But they could just as well have bundled it as an extension to SSL rather than a separate ActiveX plugin.
You'll most likely spend more time waiting for that taxi at peak times than you saved by the taxi driver using rat runs to avoid the traffic.
It'll be around forever, just like AOL, which similarly did well in getting silver surfers online in the '90s.
Per device fees don't really hurt the newcomers as much as the upfront certification fees and industry body membership fees that they already had. $0.75 per device is $0.75 whether you already sell millions of devices, or you are just starting out.
Good luck explaining to customers why a large number of third party apps that rely on Google APIs suddenly won't work on your new phones. They would be better off switching platform entirely than trying to fork Android.
They weren't charging per device before, just requiring membership of OHA and requiring the device to be certified as passing some tests to ensure compatibility.
Profit margins and overheads for manufacturer, distributor and retailer. That's about the right ratio by the time this gets to retail shelves. Except that at retail they'll likely want to round it to XX9.95 or XX9.99, so the end effect on the price is either $0 or $10.
Nexus 5 has dedicated voice recognition hardware that listens even when the main CPU on the phone is in sleep mode. It can wake the main CPU when it hears a magic phrase ("OK Google"). Google Now isn't listening on the mic though - if the magic phrase has not been detected, the audio never leaves the dedicated voice IC.
When more people use taxis, it will make more sense to provide more of them, so there is more chance that one is nearby when you want it. At peak times it makes more sense to use buses (where trains are not available).
It's sad for the people who are driven out, but this process is basically what stops cities from becoming Detroit. Regular renewal is needed to keep cities alive.
Since the results clearly show that Tor is a half-baked solution the story authors felt it appropriate to use 13 as the reference value for a dozen.
As there seems to be quite a buzz around the "internet of things" right now, why not leverage your existing expertise by focusing on that rather than mobile and web. Focus on web services rather than web pages, familiarize yourself with HTTP rather than HTML and stick with C and maybe Java and Python (a lot of "embedded" devices are running Linux under the hood and some Android, and other uses of Java such as Bluray get embedded) as higher level languages that are less stressful to code networked apps in than pure C or even C++.
Before you try this over your mattress, you might want to check the size of your coffee cup.