On Sun, Dec 28, 2008 at 02:13:47AM -0500, Brad wrote: > On Thursday 25 December 2008 13:20:07 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? > > IMO audio apps should be focusing on sndio. If an app has sndio > support then try to disabe the Sun/OSS support if it isn't too diffcult but > ultimately sndio is the default/preferred API. aRts/esound support should > be removed from ports and not introduced unless the port(s) require the > use of aRts/esound (some KDE apps for aRts...), and that is referring to > anything that might be in the ports tree at the very moment. Simplify > the sound handling/options with OpenBSD in the ports tree and that > means narrowing down the options in general to sndio/JACK. Jacob > seems to agree. > > If Jacob seems to not want new JACK (1) stuff introduced then I think this > should just be dropped. Pick up the JACK support when JACK 2 comes > around.
I agree 100%. there's no point in spending time on anything other than sndio. ossaudio(3) is a hack, and offers nothing over audio(4). esd is sloppily maintained upstream. aRts is dead. pulse is bloated garbage. why spend time on something you ultimately have no control over, when there is a much better alternative (aucat outperforms *everything* in terms latency, reliability and usability) that is part of OpenBSD? -- [email protected] SDF Public Access UNIX System - http://sdf.lonestar.org
