Yes, we're now letting the user pick from enumerated 1.1 drivers, so
for now he only has "Generic Hardware" and "Generic Software" choices
in his list. I just wanted to make sure we weren't completely missing
the boat on existing 1.1 implementations, but you cleared that up
perfectly with your answer.
Looking forward to real 1.1 hardware drivers in May!
On Dec 15, 2005, at 9:10 AM, Garin Hiebert wrote:
Is there currently any such thing as a real hardware driver for 1.1?
For example, is there a version of CT_OAL.DLL out there somewhere
that is OpenAL 1.1, complete with capture API, etc.?
We're shooting for hardware 1.1 support in May 2006 (X-Fi cards
certainly, and I think most Audigy models as well at the same time).
What you _must_ do if you want to deploy an application which uses
1.1-specific features and wants to have hardware support when
available is use the enumeration mechanism to enumerate all devices
and figure out which ones have 1.1 API support. Then, your app only
selects among the implementations which have 1.1 support...
The good news is that there is sample code available which shows you
how to do all of this -- in the OpenAL 1.1 SDK available at openal.org
and/or developer.creative.com.
There is a report in another thread of potential corruption in the
library/libraries supplied with the SDK. I'll be investigating that
later this morning, so I'll be posting to the openal list if there are
any updates to the SDK and/or OpenAL installer.
We can work around this by forcing using of the generic hardware
wrap_oal, but can Creative users download updated 1.1 drivers? Do
they exist yet?
If you use the enumeration mechanism plus a 1.1 filter to get rid of
enumerated 1.0-only implementations, then you can have code which
works sensibly now and in the future.
Garin
_______________________________________________
openal-devel mailing list
openal-devel@xxxxxxxxxxxxxxxxxxxxxxx
http://opensource.creative.com/mailman/listinfo/openal-devel
|
