Verified in PT11 - same issue. If any cockos developers (or anyone with the source knowledge
) know this it would really help me to figure this issue out. Most apps perform these steps when instantiating an ASIO driver.
1.) Enumerate HKLM\Software\ASIO to get the driver CLSIDs
2,) Instantiate the CLSID of your choice, via CoCreateInstance(clsid from above)
.
.
.
More steps though they're irrelevant as in this failure case, CoCreatInstance() is never getting called.
Normally, behind the scenes, Windoze directs the app to either the actual key or the Wow6432Node… based on the app’s “bit-ness;” 64 or 32 bit respectively. Its as though some sort of pre-instantiation sanity test is failing...
Thanks again,