© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
(In reply to comment #122)
> ... Blaming that on kernel issues is the
When more that 230 ms come from the kernel it is fair to blame the kernel. The Fedora kernel gives less than 5 ms in the same scenario. On the current Fedora system you don't have these latency issues with PulseAudio.
On a good configured system you don't need to change anything for 99% of the users and 99% of the use cases.
"Hard Core" gaming with PulseAudio is just fine.
This is how it should be.
To ask casual computer users to switch off PulseAudio in order to get Wine working will not work on the long run.
> *) PulseAudio is like the 15th sound API on Linux. All the reasons cited why
> PulseAudio is good were cited for ESD and Arts before. I am still not convinced
> why Pulse is suddenly going to fix all that. ESD and Arts were dropped for good
> reasons.
And PulesAudio was developed for good reasons and has learned a lot from the "14" predecessors. It is far more than a network daemon and software mixer. It is the integrated sound system LINUX/Unix was missing so bitterly.
ESD was not simply dropped, it was replaced by PulseAudio.
It is fine when DMIX is enough for your needs, but you can't reduce the level of sound support on this level. It is simply not sufficient for average users any more.
> /me anticipates the same flamewar in one or two years when Wine urgently needs
> to support, say, SpeedAudio, which will be the definite solution to all sound
> issues on Linux.
This time it is not just a KDE or Gnome project. Not even a LINUX project. It is on the way to become the standard desktop sound system at least on LINUX for normal desktop usage. Give it a chance. I don't believe that we will see SpeedAudio in the next ten years ...