Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Pulseaudio misconceptions (Score 4, Informative) 755

Try the settings - standard kernel options for linux don't work for this.

The only options that work today are using driver level code for audio processing or a real time Xenomai task.

Please support Thomas Gleixner via the Linux Foundation to help to fix this limitation of Linux: http://lwn.net/Articles/572740...

Until then, all high performance low latency audio processing in linux needs to not use any user level tasks.


Comment Re:Pulseaudio misconceptions (Score 5, Informative) 755

Software mixing you say? It's called dmix.

Why the fuck do you want to round a *sound mixer* inside your *kernel space* ?! Do you run your video decoder and webbrowser there too ?
I prefer to run unnecessary things like sound as daemons in userspace. Thank you very much.

... Because I need less than 125 microseconds mixing processing latency (12 samples at 96 kHz) so that in-ear monitor mixing for live performance can be useful - requires a total latency from microphone to wireless receiver to CPU to processing to wireless transmitter to in-ear monitor of less than 5 ms. Until Linux user tasks can be scheduled with this kind of hard real time timing accuracy, mixing real time audio in user tasks doesn't cut it for live audio. So I myself am required to do my mixing and processing for real time audio either in the kernel driver, in a RTLinux task (in kernel space), or in a Xenomai task (see xenomai.org ) running at a higher priority than Linux.

Comment Re:MITM legalized at last (Score 3, Interesting) 294

Until relatively recently, these re-directions would adversely affect a debian/ubuntu linux system update procedure. A cron job would apt-get update and pull in new index files. Since the transport was not encrypted, the index files would not be what the apt system were expecting. It would store the content of the redirected web page instead of the proper index files into a cache and then apt-get update would be forever broken until you manually figured out how to delete the corrupted files someplace in /var/*/apt

ISP's and WiFi Access points that do this redirection are the reason why HTTPS everywhere is a good idea.

Comment Re:Free market (Score 1) 353

(reposted as my account since i accidentally was AC)

The scariest taxi ride I ever had was in the Seattle area, heading back to the Airport after the C++ conference. The taxicab was a Prius which was broken and dirty inside - you could see the airbag. The car's signal lights did not work. The driver was weaving in and out of traffic and just about killed a couple on a motorbike, causing a big road rage incident. The taxi driver was angry that we didn't tip him. If we had tipped him a normal amount, then the total cost of the trip would have been the same as the Uber ride that we took from the Airport to the same hotel.

As a consumer I want the choice to choose a safe, reliable, and trustable source. For me that is Uber.


Comment Re: Or maybe... (Score 1) 399

A more interesting side to this story is how people were able to figure out which airport she was flying to just by googling her name: https://www.twitter.com/Zac_R/status/414249210641653761/photo/1?screen_name=Zac_R

I'm not sure how that was possible by google - but it sure is a creepy thing.

The person who made that tweet ( @Zac_R ) was apparently able to talk to Justine's father before she landed, and took the pictures of her at the airport:


Slashdot Top Deals

Technological progress has merely provided us with more efficient means for going backwards. -- Aldous Huxley