|
libao DriversLibao supports both live output drivers and file output drivers. Live output drivers send audio data to sound cards and sound daemons. File output drivers write audio to disk using a particular file format (such as WAV, AU, etc.). You must invoke the ao_open_????() function that corresponds to the type of driver you are using, but otherwise live and file drivers are treated identically in libao. Live Output DriversnullNull driver. This is just a test device which does not write the audio data anywhere.Option keys:
alsaAdvanced Linux Sound Architecture. This driver borrows some code from Jaroslav Kysela'sOption keys:
alsa09Advanced Linux Sound Architecture, version 0.9.x API. This is essentially the alsa driver modified to use the newer API.Option keys:
esdESounD audio driver. This sound daemon is used on some Linux systems. It permits multiple programs to play sound simultaneously and sound to be sent to networked computers.Option keys:
irixIRIX audio driver. This was inherited from the original libao, but has not been tested. Use at your own risk. (Better yet, fix it! I don't have access to an IRIX system.)Option keys: None.
ossOpen Sound System driver. This is the audio system for Linux and FreeBSD as well as some other UNIX-like systems.Option keys:
sunSun audio driver. This is the audio system for NetBSD, OpenBSD, and Solaris.Option keys:
File Output DriversauSun audio file driver. Writes a .au file from audio output. This driver can write usable data to unseekable files (like standard out), which the wav driver cannot do.Option keys: None.
rawRaw sample driver. Writes the sound to disk in uncompressed, headerless form using the byte order specified.Option keys:
wavWindows sound file output. Because of the way WAV files are structured, this driver cannot correct files unless the target file is seekable. Writing WAVs to stdout will result in broken files. Use either the raw or the au driver instead.Option keys: None.
Default Driver DetectionIn the absence of configuration files to explicit identify a default driver, the library will try to detect a suitable default driver. It does this by testing every available live output driver (using ao_plugin_test()) and finding the driver with the highest priority (see the ao_info struct) that works. Drivers with priority 0, such as the null and file output drivers, are never selected as the default.The ranking system currently used is:
Clearly, any ranking scheme will fail to make everybody happy. For
such cases, the configuration files can be
easily used to define an appropriate default output device
|