On Sat, Jul 07, 2007 at 02:41:05AM +0000, William Pitcock wrote: > The most fucked up thing that I can think of about the current state of > affairs in ALSA is dmix. Every other UNIX sound system like ALSA does it's > software mixing in kernel space. The applications never even know about > it. It's not only until recently (2005-2006 or so) that ALSA came close to > this, but there are still problems. Many cards need workarounds to make > dmix work because of the way it works, and the way that ALSA buffers data > around.
I have to agree. I am not an audio programmer, just a user; but the bottom line is simply: It is WAY to hard to get things working (if at all possible). At one point I tried to get sound from xmms and ut2004 at the same time (on my new machine). I was ASTONISHED that it didn't Just-Work! After trying many complex things-- I gave up and put my old soundblaster Live! in the new PC - because that card has hardware support for this. Now I was lucky to HAVE that other soundcard, but what about all those other users out there who just buy a new PC, with a sound chip on the motherboard and then, being simple, ordinairy users, have to face this ALSA configuration hell to do something as simple as having two audio applications play sound at the same time? > For the non-technically inclined, ALSA only keeps two fragments for > input/output data each. This is horribly unusable because most soundcard > fragments are only 1KB, so applications have to adopt ringbuffers to pass > data to ALSA. If you're doing video, this leads to possible timing issues > unless you sit down and well design your abstraction layer for audio I/O. Worse-- the two fragment limit is passed on to the OSS emulation (or at least it was in 2005; but if this is still true for the ALSA API in 2007, then my guess is that it's also still true for the OSS emulation). The result is that applications written for OSS do not work anymore when using the OSS emulation of ALSA and therefore the argument of providing backwards compatibility doesn't exist. ...snip... > Hannu has ideas on how that could work. I suggest all of the kernel > developers listen, and listen well, or this mess will never be fixed in a > way that is truly usable. > > -nenolod Good post, nenolod. -- Carlo Wood <[EMAIL PROTECTED]> PS I am NOT saying that I want ALSA to be removed from the kernel. I am just saying that I agree with those who think that the ALSA API is too complex, hard to use and has serious flaws that should be addressed. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
