chrismorgan@rcn.com wrote:
So the external tool would try to load each driver and put the detected one into the appropriate location in the registry?
the tool(s) would need to: - detect all runnable sound drivers - let the user pick the one(s) he/she wants to run. it would have to detect that a wineoss and winealsa would in fact output to the same physical Linux device, so there's no need to install both of them. Things are a bit more complicated for aRts vs OSS for example where you get audio mixing/sharing with aRts and better RT capabilities (esp. for games) with OSS. - let also the user decides of the default driver (the one the mapper will open by default) - when this is decided, the registry should be populated accordingly
but, this should also be part of a more generic user oriented configuration program, going much further than the pure audio driver configuration
A+