レナート   Wunschkonzert, Ponyhof und Abenteuerspielplatz   ﻟﻴﻨﺎﺭﺕ

Posted by Tristan at Thu Aug 28 23:25:55 2008
This could lead to a fun new game: the longest chain of libraries in action between an application and your speakers. For example:

libcanberra -> GStreamer -> SDL -> Alsa -> Pulseaudio -> Alsa -> Sound card

I'm sure other people can do "better", though...

Posted by Zeeshan Ali at Fri Aug 29 23:29:28 2008
I am affraid tristan might be very right here. Do you really need multiple backends in libcanberra? Shouldn't it just use gstreamer and let gstreamer decide the elements/backends to use. Unless I am underestimating the scope/context of this library.

Posted by Lennart at Sat Aug 30 01:36:41 2008
Zeeshan: libcanberra is a layer that is supposed to translate XDG sound event names to the way sound events are generated on the local platform. Only for Unix platforms this means reading sound files and sending them to an audio device device. On Windows this measn playback should happen via the PlaySound() API. On MacOS via SystemSoundPlay().

Then, libcanberra also wraps cacheing of sound samples and passes metadata to the underlying subsystem, such as cursor positions needed for positional event sounds in PA.

Final libcanberra is supposed to be portable and usable in other toolkits like Qt, too.