Pwned. It also makes me weep that I never saw fit to get an account when I was younger.
My current UID is not too shabby, but this is actually my first account at Slashdot. I forgot my password and lost the email address I used to sign up so I had to register another user, this one. Whenever some 3-digit user (almost always 400+) enters UID pissing contests I want to remember the password for Guybrush so badly I almost start to weep. I CAN piss longer than this, I promise!
Do you honestly think a half dozen audio codecs, and another half dozen video codecs would make for a "small" DLL?
libavcodec currently has decoders for 242 audio and video codecs, encoders for 100, demuxers for 129 container formats and muxers for 89.
The resulting DLL is about 7 MB.
Yes, and pulseaudio devs will make no effort to fix those bugs, get them fixed, or get their software to play nice.
Yes, this is why Lennart and the other PA devs are regularly contributing patches to ALSA and working with them to resolve bugs in drivers.
I don't find any "terrible attitude" in that thread. They get a bug report, find that the kernel driver is failing and assign it to the kernel devs. The tone was very professional, no flamebaiting or otherwise bad attitude. Also, if you bothered to follow the links you'd see that the error was triggered with or without PulseAudio, meaning that it happens even without PulseAudio. The error is that VMWare's hardware emulation of the ens1371 sound card is incomplete.
Wrong. It doesn't need that much CPU time, it just needs its CPU time at very exact intervals. Given realtime privileges it can preempt at those very exact intervals without needing to hog the CPU in between.
There are many different problems with the Linux audio stack. The stack includes the Linux kernel, the in-kernel ALSA drivers and subsystem, the ALSA userland and PulseAudio.
PulseAudio has its share of bugs and missing/incomplete features and so has the other parts of the stack.
In Ubuntu, a lot of the problems are caused by its kernel configuration, mainly its too low resolution timer and disabled preemption. This cause PA to get much higher latencies than it should get and it has to use much more CPU time to keep the timing 100%. It can also cause sound to stutter when the CPU load is 100%.
Then there are other bugs in PulseAudio and the rest of the stack. These will of course affect all distributions, including Fedora 10.
The community is working hard to fix these bugs. If you look at each PulseAudio release, the changelog is massive. If you look at ALSA's driver changelogs you will notice that they have begun to get pretty massive as well. This means that tons of bugs that have been there for a long long time are now getting fixed because PulseAudio requires bugs to be fixed at the source instead of trying to work around everything. Yes, this is a good thing in the long run.
In the days of yore, people normally didn't run any audio servers at all.
If they did, they either had a lot worse latency than PulseAudio currently has (arts, esound) or they drained laptop batteries much faster than PulseAudio currently do (JACK) or couldn't mix audio coming from different user accounts (JACK). All of them had worse backwards compatibility than PulseAudio.
If they didn't, they could only have one application at a time play sound unless they had one of those relatively rare sound cards that had both hardware mixing and Linux support.
A sound server is by its nature not a normal application. It has many somewhat conflicting requirements that just about no other type of application has to deal with. It's a userspace program that has to do a lot of things traditionally done in kernel space.
As it's very sensitive to timing, realtime priority is optimal but not needed for a usable desktop setup. Ubuntu's default kernel doesn't even have full preemption enabled though. In 2009. Under those conditions you can't run something as timing critical as a low latency sound server reliably.
A lot of the problems with Pulseaudio are caused by the misconfiguration of Ubuntu's default kernel. It seems that they will be making the upcoming Karmic Koala even worse, according to a small rant on Lennart's blog today.
Now if only it would actually play music without skipping, freezing, or using 30+ percent of the CPU. Sheesh!
It will, if both your kernel and Pulseaudio are properly configured for low-latency desktop usage (realtime privileges, 1000hz timer, etc). While I fully understand you being annoyed that your current distro/version ships with a default configuration that isn't fully adjusted to this very common usage pattern, it also means that the situation will get better as distributions learn how to properly integrate Pulseaudio and the remaining bugs in Pulseaudio itself are fixed and it gets better at automatically detecting and adjusting to different hardware setups. This includes making the ALSA drivers better at reporting which jacks are plugged in and things like that.
I'm not sure how it is nowadays but when I got an STD (chlamydia) some 13 years ago (in Sweden) I was required to tell the doctor how many I've had sex with the last 6 months. Then I was required to tell these persons and make them do the test while giving their doctor my name so the number could be verified. I also had the option to give my doctor addresses, phone numbers or other ways of contacting them and then they would take care of that part.
The most bizarre thing is that I've been contacted by doctors TWICE (about a year apart) because someone had given them my name/address and told them they've had sex with me the last 6 months when it was impossible that it could had happened as I had only had sex with my partner for at least a year at that time. When doing the test (as required by law when you've been contacted) I was clean as expected, both times.
No, it's actually the purely object oriented, dynamically typed, late bound, garbage collected, message passing, compiled-to-machine-code child of C and Smalltalk.
I don't go to the cinema anymore because I don't want to sponsor the mafiaa, but I've actually brought a hamster cage (without hamsters at the time) into a cinema once.:)
I live in a city where parking spots are scarce and most people take the metro or a bus when they travel between city centre and home. Cars are mostly used for the outer suburbs and transportation (not counting the few ones living in the city, lucky enough to afford an insanely expensive garage space). Going home just to drop whatever you had shopped that day or had to carry from work is not an option so if you can't bring your stuff with you, you simply just skip the film instead. Cinemas know this so unless it's an almost sold-out film they let you bring as much junk as you need.
"But, yes, when you admit that Star Trek has as much to do with plausibly extrapolated science as The A-Team has to do with a realistic look at the lives of military veterans, life gets easier. "
Qt and SQLite. Seriously. LGPL and kick-ass! Also, Qt can be compiled to have SQLite completely built-in. No extra libs/dlls needed. It handles networking, threading, IPC, SQL and much more. No need for platform-specific ifdefs.
Slashdot Mirror
Like 8< or K ?
Me too!
While you're at it, do it correctly and name them Belgian Fries or just "Pommes Frites" instead. :)
Pwned. It also makes me weep that I never saw fit to get an account when I was younger.
My current UID is not too shabby, but this is actually my first account at Slashdot. I forgot my password and lost the email address I used to sign up so I had to register another user, this one. Whenever some 3-digit user (almost always 400+) enters UID pissing contests I want to remember the password for Guybrush so badly I almost start to weep. I CAN piss longer than this, I promise!
No, zee FS in not zee FS, but zed FS is. Parse that, monsieur!
Do you honestly think a half dozen audio codecs, and another half dozen video codecs would make for a "small" DLL?
libavcodec currently has decoders for 242 audio and video codecs, encoders for 100, demuxers for 129 container formats and muxers for 89.
The resulting DLL is about 7 MB.
Yes, and pulseaudio devs will make no effort to fix those bugs, get them fixed, or get their software to play nice.
Yes, this is why Lennart and the other PA devs are regularly contributing patches to ALSA and working with them to resolve bugs in drivers.
I don't find any "terrible attitude" in that thread. They get a bug report, find that the kernel driver is failing and assign it to the kernel devs. The tone was very professional, no flamebaiting or otherwise bad attitude. Also, if you bothered to follow the links you'd see that the error was triggered with or without PulseAudio, meaning that it happens even without PulseAudio. The error is that VMWare's hardware emulation of the ens1371 sound card is incomplete.
On a more serious note, I'm more interested in which planets are Class M.
Apple didn't block the Pre from anything. The Pre was using the iPod/iPhone USB identifier.
Not at first. They switched to using the iPod/iPhone USB identifier only because Apple blocked the Pre from using iTunes...
Wrong. It doesn't need that much CPU time, it just needs its CPU time at very exact intervals. Given realtime privileges it can preempt at those very exact intervals without needing to hog the CPU in between.
There are many different problems with the Linux audio stack. The stack includes the Linux kernel, the in-kernel ALSA drivers and subsystem, the ALSA userland and PulseAudio.
PulseAudio has its share of bugs and missing/incomplete features and so has the other parts of the stack.
In Ubuntu, a lot of the problems are caused by its kernel configuration, mainly its too low resolution timer and disabled preemption. This cause PA to get much higher latencies than it should get and it has to use much more CPU time to keep the timing 100%. It can also cause sound to stutter when the CPU load is 100%.
Then there are other bugs in PulseAudio and the rest of the stack. These will of course affect all distributions, including Fedora 10.
The community is working hard to fix these bugs. If you look at each PulseAudio release, the changelog is massive. If you look at ALSA's driver changelogs you will notice that they have begun to get pretty massive as well. This means that tons of bugs that have been there for a long long time are now getting fixed because PulseAudio requires bugs to be fixed at the source instead of trying to work around everything. Yes, this is a good thing in the long run.
In the days of yore, people normally didn't run any audio servers at all.
If they did, they either had a lot worse latency than PulseAudio currently has (arts, esound) or they drained laptop batteries much faster than PulseAudio currently do (JACK) or couldn't mix audio coming from different user accounts (JACK). All of them had worse backwards compatibility than PulseAudio.
If they didn't, they could only have one application at a time play sound unless they had one of those relatively rare sound cards that had both hardware mixing and Linux support.
A sound server is by its nature not a normal application. It has many somewhat conflicting requirements that just about no other type of application has to deal with. It's a userspace program that has to do a lot of things traditionally done in kernel space.
As it's very sensitive to timing, realtime priority is optimal but not needed for a usable desktop setup. Ubuntu's default kernel doesn't even have full preemption enabled though. In 2009. Under those conditions you can't run something as timing critical as a low latency sound server reliably.
A lot of the problems with Pulseaudio are caused by the misconfiguration of Ubuntu's default kernel. It seems that they will be making the upcoming Karmic Koala even worse, according to a small rant on Lennart's blog today.
Now if only it would actually play music without skipping, freezing, or using 30+ percent of the CPU. Sheesh!
It will, if both your kernel and Pulseaudio are properly configured for low-latency desktop usage (realtime privileges, 1000hz timer, etc). While I fully understand you being annoyed that your current distro/version ships with a default configuration that isn't fully adjusted to this very common usage pattern, it also means that the situation will get better as distributions learn how to properly integrate Pulseaudio and the remaining bugs in Pulseaudio itself are fixed and it gets better at automatically detecting and adjusting to different hardware setups. This includes making the ALSA drivers better at reporting which jacks are plugged in and things like that.
I'm not sure how it is nowadays but when I got an STD (chlamydia) some 13 years ago (in Sweden) I was required to tell the doctor how many I've had sex with the last 6 months. Then I was required to tell these persons and make them do the test while giving their doctor my name so the number could be verified. I also had the option to give my doctor addresses, phone numbers or other ways of contacting them and then they would take care of that part.
The most bizarre thing is that I've been contacted by doctors TWICE (about a year apart) because someone had given them my name/address and told them they've had sex with me the last 6 months when it was impossible that it could had happened as I had only had sex with my partner for at least a year at that time. When doing the test (as required by law when you've been contacted) I was clean as expected, both times.
No, it's actually the purely object oriented, dynamically typed, late bound, garbage collected, message passing, compiled-to-machine-code child of C and Smalltalk.
I don't go to the cinema anymore because I don't want to sponsor the mafiaa, but I've actually brought a hamster cage (without hamsters at the time) into a cinema once. :)
I live in a city where parking spots are scarce and most people take the metro or a bus when they travel between city centre and home. Cars are mostly used for the outer suburbs and transportation (not counting the few ones living in the city, lucky enough to afford an insanely expensive garage space). Going home just to drop whatever you had shopped that day or had to carry from work is not an option so if you can't bring your stuff with you, you simply just skip the film instead. Cinemas know this so unless it's an almost sold-out film they let you bring as much junk as you need.
That doesn't mean that Java is more programmer-friendly than Objective C.
"But, yes, when you admit that Star Trek has as much to do with plausibly extrapolated science as The A-Team has to do with a realistic look at the lives of military veterans, life gets easier. "
Relevant YouTube video.
And the Star Trek version of Knights of the Round Table has over 2 million views. 2129223 to be exact.
Yes, I find that highly illogical.
Qt and SQLite. Seriously. LGPL and kick-ass! Also, Qt can be compiled to have SQLite completely built-in. No extra libs/dlls needed. It handles networking, threading, IPC, SQL and much more. No need for platform-specific ifdefs.
But some girls want to look just like that...
(in Debian GNU/kFreeBSD, the k stands for "kernel".)
...and it's pronounced as "nuke free beast".
It's about this.