Max Kellermann schrieb:
The problems with enabling dmix (very bad sound quality, high CPU
usage, random crashes due to ALSA bugs) usually outweigh the problems
of two applications accessing the same hardware device.
In the meantime I've read some more and learned that MPD falls back to
using dmix, since it's activated by default in ALSA now. Didn't know
that before.
So there IS a good reason for these options. ;)
The worse sound quality and the higher CPU usage happen due to the
resampling to 48 kHz, that dmix does in the background. It can be
addressed by forcing dmix to resample everything to 44.1 kHz instead.
Since most music uses that there's nothing to do for dmix most of the
time when listening to music (meaning no decrease in quality and no CPU
usage).
But of course after that the same problems are there e.g. when watching
DVDs (that use 48 kHz).
So unsetting the options mentioned above by default isn't the best option.
I don't know enough about the possibilities of deb packages (yet), but
would it be possible to have these options enabled or disabled according
to the computers sound chipset? Something like " if (manufacturer ==
'intel') { echo 'Your sound hardware sucks.'; enable_demix(); } "?
I guess my next reading will be about pulseaudio... ;)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
