[vorbis-dev] Systemwide default for ogg123

volsung at asu.edu volsung at asu.edu
Thu Jan 25 15:09:34 PST 2001

On Thu, 25 Jan 2001, Ingo Saitz wrote:

> On Thu, Jan 25, 2001 at 10:40:18AM -0800, Ralph Giles wrote:
> > I never understood what was wrong with the compiled in default.
> I don't think that the null output plugin is a good choice for an
> easy use of ogg123. I'd expect calling "ogg123 file.ogg" produce
> some sound without the need to specify any options.

Once upon a time, the configure script automatically selected the best output
plugin (ESD, ALSA, then native) unless told otherwise and made that the
compiled in default.  That, however, was bad for binary packagers who don't
get to know what sort of audio library support the target platform has.

To put on the TODO list for libao that Michael has suggested: A library
function that will return the number of the "best" plugin given the available
hardware.  This has to be done at runtime in order to deal with changing
library support.  This in turn will require some sort of "can you
run?" function in each of the plugins.

A side question:  What happens if you try to load a plugin (say alsa) which
requires a library that you don't have on the system?  Can you catch the error
gracefully and decide that the library is in the "not available on this
platform" category?

Stan Seibert

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.

More information about the Vorbis-dev mailing list