how do padsp aoss and other OSS sound wraper work?
Hi
I am still grappling with old OSS applications that accept nothing else than /dev/dsp.
ALSA has a compatibility layer that produces a /dev/dsp and routes it into ALSA, but I am using both Jack and Pulseaudio, since they don't lock up the soundcard like ALSA does. (Alsa, the big deceiver once wanted us to believe that it is better than OSS and would not lock the soundcard) ;-)
Now there are utilities that are supposed to lead OSS applications into either jack (jacklaunch) or pulseaudio (padsp) but I have not seen them work once!
Everytime I launch an application with them, they complain that there is no file /dev/dsp.
How do they work? Arent't they supposed to give the applications a /dev/dsp to open? How else is a OSS applications going to work?
Both compatibility programs use LD_PRELOAD to load some libraries which in term then should reroute OSS. How is this done? How are these libraries supposed to work? (without an applications that guides it?)
cheers
Markus
|