[Openal] OpenAL Soft's alcOpenDevice returns null

[Stephen A.]

>
> Does the VMWare system have DirectSound capabilities? If so, make sure  
> OpenAL Soft is building with DSound support (check the output during  
> cmake). If it doesn't, then it's possible that Creative's drivers can  
> use the old WaveOut API, while OpenAL Soft doesn't.

It should have (at least dxdiag says so). I'll rebuild and check again to  
make sure.

>> The same call also fails on Ubuntu 7.10
>> (only tested with the default implementation, not OpenAL Soft), which
>> leads me to believe I may be doing something wrong.
>
> The device names returned by enumeration are implementation specific.
> Passing "Wave File Writer" to implementations other than OpenAL Soft is
> likely not to work. NULL is the only legal value that's gauranteed across
> platforms (to select a default). Also, the default implementation isn't  
> very good with enumeration (especially version 0.0.8).

There are no hardcoded values - the code tries in turn the default device,  
the first enumerated device and, if everything else fails, null. Version  
0.0.8 does not support any device enumaration whatsoever, so the code just  
passes null and hopes for the best.

Could alcOpenDevice fail because the device is locked up by another  
application? (e.g. /dev/dsp for ALSA) This might explain the behavior on  
Ubuntu, as OpenAL could conflict with VMWare trying to access the hardware  
at the same time. VMWare reports this error whenever another application  
is using the sound hardware:
Failed to open sound device /dev/dsp: Device or resource busy
Failed to connect virtual device sound.


> _______________________________________________
> Openal mailing list
> Openal at opensource.creative.com
> http://opensource.creative.com/mailman/listinfo/openal

-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/