There are ASIO drivers that can cause compatibility issues with the SoundID Reference app. This guide provides steps on how to blacklist unusued and problematic ASIO drivers.
In this article:
Problematic ASIO drivers
Some ASIO drivers showing in the SoundID Reference app might not be of any value to the user, or be subject to compatibility problems resulting in serious usability issues (crashes, audio artifacts during playback, etc.)
Problematic ASIO drivers can be manually disabled by the user for any reason they deem necessary - blacklisted ASIO drivers will not show up in the SoundID Reference app.
How to blacklist an ASIO driver in the SoundID Reference app
- Navigate to C:\Users\you username\AppData\Local\Sonarworks\SoundID Reference\Systemwide (note that AppData is a hidden directory by default - to access it you might need to allow showing hidden files as per instructions here)
- Open audiodeviceblacklist.config file with Notepad and keep it ready for editing:
- Type 'regedit' in the Windows search bar to open Registry Editor
- Navigate to the ASIO directory shown below - all installed ASIO drivers are listed here:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ASIO
- Click on the driver you wish to blacklist (we have blacklisted ASIO4ALL v2 in the example below)
- Double-click on CLSID and copy-paste the displayed value into the blacklist file ID field:
- Double-click on Description and copy-paste the displayed name into the blacklist file Title field:
- Close and Save the blacklist file - you're done!
You can go ahead and relaunch the SoundID Reference app - the blacklisted driver should now be gone. If the blacklisted device is still showing in the app, please go back and check the steps one by one to make sure you've done everything correctly. If there are still any issues, contact us by submitting a support request below!
NOTE: You can blacklist multiple ASIO drivers if you need to - simply copy the entire <BlacklistedDevice> section in the blacklist file and fill the ID and Title fields with appropriate driver details from the Registry Editor:
0 comments