Latentcy is (was) a problem. I always have to offset mplayer to watch stuff. Yet, a kernel level version of artsd (and I'm no champion of any particular thing), or something like it, would no doubt deal with that latentcy. Unix/Linux is not so good with real time stuff, never has been, but abstracting into the kernel would bring VERY efficient access to everything, and "kernel" level and class of peer review (kernel.org) would be helpful. I like the idea of mixing at the bottom level. Its a natu...
Sorry about that. It explains a few things, though. Regardless, I like the idea of a kernel level application, like tux or netfilter, on which we can lay and mix legacy methods, a new KDE method, and allow for future methods. Given the ease of module aliases, would it be hard to go between current audio modules, and applications that call on them? What I'd like to see is a better system of autonomous configuration. What we have now is hard to configure, and very easy to break. It's too bad about...
artsd provides multiple audio availability, because it acts as the audio device, and can mix all sorts of things in software, which it then feeds to the audio device. Likely, your programs are using audio directly to another method, rather than through artsd. I've run lots of audio, such as xmms and mplayer at the same time, with them both playing at the same time. David Weeks
I hope whatever we do, that it clears up the mess we have right now in Linux et. al. audio support. With oss, alsa, artsd, "legacy support", and the "collective" distribution of audio software --- this rich diversity causes LOTS of configuratin and inter-operation problems. We need a hard and fast standard, that provide superior native facilities, seamless legacy support, and accesability(sp?) for other audio standards. artsd provides that, and has an unbelievable power over the processing of au...
This looks like a permission issue: ls -l /dev/dsp shows you the owner, group and permission flags for that file. I don't know how much you know about permission, but you have there are three classes: owner, group and other, in that order. If you're neither the owner, nor a member of the group, then you are other. Regardless, make sure you have rwx permission for what ever applies to your status as a user. Don't think that because you are the owner, or a member of the file's group, that you have...
