On Thu, Dec 25, 2008 at 07:20:07PM +0100, Christian Weisgerber wrote: > This is a rough diff to enable the EsounD and JACK output plugins > that are included with mpg123. They are split out into subpackages, > and there are even pseudo-flavors do disable them since mpg123 > itself has rather little in the way of dependencies. > > I haven't actually tried to use these output plugins. People who > have esd and jack setups can do that. > > Is there any interest in this? Is this a direction we want to take? >
My opinion is not very relevant since i use neither esd nor arts. IMO aucat has by accident most (all?) of the requred features for desktop apps, currently it can't do the following: - upload short .wav files into the server so apps can call them when needed. - authenticate clients and work across network On the other hand it could allow any application to work reliably with a controlled latency on any hardware we support (afaik esd/arts can't). [...] My sweet dream is to simplify audio and audio porting, so one day we can stop improving^W tweaking audio, and concentrate on wrinting real code for audio. Having esound/arts neither contributes to this nor hurts it, afaik. I mean, audio by itself is very simple, and bringing it to the complexity it deserves will add robustness and will give us more time for interesting stuff. [...] jack is very different from esd/arts/pulse, it's a framework around which apps for music are developped. IMO classic apps with audio backends don't need jack backends as long as they can work without jack. Advanced audio apps are built around jack and cannot be ported to something else because they use features that only jack has (eg. synchronization between apps) The last year jack was the only way to get sound from envy(4) or to get full-duplex right, so jack backends were very useful to me. Now they're no more useful. my 2 cents. -- Alexandre
