ASIO Message

TomG wrote on 5/5/2004, 6:32 PM
Every time I crank up V5, I get a pop-up that states "CTASIO Warning - There are no Creative audio products installed and running that support ASIO". I am using a 3 year old Creative SB Live card and I'm not even sure what the ASIO does. But I don't recall seeing this message when I was on V4. Is there a setting which would disable that warning?

Thanks,
TomG

Comments

MJhig wrote on 5/5/2004, 7:55 PM
What do you have selected in Vegas' Preferences > Audio Device?

MJ
pwppch wrote on 5/5/2004, 9:34 PM
Have a look in our Knowlegebase, article 723.

This explains the problem and tells you how to fix it.

Peter
Hunter wrote on 5/6/2004, 6:49 AM
Would this "fix" work with kx project drivers, I get same message at start up.

Hunter
TomG wrote on 5/6/2004, 7:17 AM
Thanks, Peter.

Maybe it's just me, but when I search the KB for "asio" under Vegas/Vegas 5, I got no hits. It took me a while to find #723 but I have found and printed the answer and will try it.

TomG
fherr wrote on 5/6/2004, 7:23 AM
I had the same problem, but then I found a way to search for the KB article number. It's in the drop-down that says "Search by": select "Answer ID" and type in 723. Kind of hidden a bit ...
pwppch wrote on 5/6/2004, 11:21 AM
Should. The problem is basically the same. When you originally installed the Creative driver set, it registers the ASIO driver. When you migrated to the KX driver, the Creative ASIO driver is left registered.

FWIW: The real problem is that the Creative ASIO driver is brain dead. The way ASIO works is that the host must "grovel" for all ASIO drivers. The only way to determine whether the device that the ASIO driver references is actually available/function is to ask the driver. The Creative ASIO driver detects that the hardware is not available (or other components are not installed/active in the case of the KX driver replacement) and instead of just quitely failing, it pops up a nag dialog. Sadely, we have no control of this behavior.

Peter
TomG wrote on 5/6/2004, 3:24 PM
Well, I followed the instructions on 723. Only found one entry that referenced creative labeled CLSID, the other entry was default. Changed the CLSID to xCLSID. That seemed to eliminate the problem and the sound card still appears to be working OK.

Thanks for your help. Would never have found that solution in a million years.

TomG