SDK5.1 screws up standalone ASIO (XTC) -here's how to fix it
Posted: Mon Mar 09, 2015 1:41 pm
Having Scope v 5.1 and installing SDK 5.1 afterwards, standalone ASIO mode in which you can load XTC plugins doesn't work - the driver cannot be found.
It is caused by SDK's setup overwriting some registry values with wrong data.
Start regedit and search for DD320B40-17F0-11d2-9CAD-006097A97422
There you will find InprocServer32 subkey and see the 'default' value under it.
It may say C:\Program Files\SCOPE SDK PCI\App\bin\AsioScope64.dll
It's wrong! Make sure that it points to your main Scope installation path, not SDK, so that it reads C:\Program Files\SCOPE PCI\App\bin\AsioScope64.dll
That is for Scope under 64bits, adjust for 32 accordingly
It is caused by SDK's setup overwriting some registry values with wrong data.
Start regedit and search for DD320B40-17F0-11d2-9CAD-006097A97422
There you will find InprocServer32 subkey and see the 'default' value under it.
It may say C:\Program Files\SCOPE SDK PCI\App\bin\AsioScope64.dll
It's wrong! Make sure that it points to your main Scope installation path, not SDK, so that it reads C:\Program Files\SCOPE PCI\App\bin\AsioScope64.dll
That is for Scope under 64bits, adjust for 32 accordingly