Linked by Thom Holwerda on Sat 4th Apr 2009 16:36 UTC, submitted by Accident
Thread beginning with comment 357567
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-06
I don't think it is _quite_ as complicated as it sounds. Really, the "official" sound api is ALSA, as this is supported in the kernel. Older apps may use OSS, so ALSA also provides a "backward-compatability" mode for OSS, so apps shouldn't have to worry. As far as I can tell, PulseAudio, etc are frameworks on top of lower level frameworks like ALSA. If I am wrong, someone can correct me. This reminds me of graphics frameworks in Windows. There is GDI, DirectX, WPF, etc. Sure, your graphics card may work with your driver, but your driver must support GDI and DirectX. I think WPF is built on top of GDI, but I am not sure. People run into this problem when a game requires DirectX 10 but the card only has a DirectX 9.0c driver. Even sound has layers under Windows. Is the app using Win32 calls, MFC calls, DirectX calls, .NET calls, etc. There are more frameworks in Windows than you the end user may realize.