uOS provides API to play audio as well as to decode audio from a file.
OpenAL provides API to play an audio only.
That places OpenAL or a lower level, compared to uOS. As well as OpenAL's "working" is strictly limited to playing/recording audio samples only, where uOS also provides a mean to decode/encode it to different storage (file) formats.
Hum, afaik, with wavopenal.pas demo, you get sound.
So, how openal library does to connect to audio port ?
If openal library is a "low level" library, it should deal (and have code to do this) with audio port too.
But it is not the case.
But, maybe, our "low level" understanding differs.
By the way, many thanks for (your?) wavopenal.pas demo.
If the author (you?) agrees, I will add the wav decoder of the demo in uos (so it will be possible to decode wav files also without loading SndFile.so audio library).
But, till now, I do not see advantage of openal.so vs portaudio.so (both are limited to playing/recording audio samples, but portaudio can deal directly with audio devices (or use the installed sound system). Openal can only deal with a installed sound system, like ALSA, OSS, Pulse, ...
Fre;D