There are ASIO drivers that can cause compatibility issues with the Measure 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 Measure 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 Measure app.
How to blacklist an ASIO driver in the SoundID Reference Measure app
- Go to
C:\Users\your username\AppData\Local\Sonarworks\SoundID Reference\Measure
N.B. The AppData folder is hidden by default - you will need to allow Explorer to show hidden files.
- 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 Realtek ASIO 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
- Copy the file to SoundID Reference Measure folder:
C:\Users\your username\AppData\Local\Sonarworks\SoundID Reference\Measure(AppData is a hidden directory by default - to access it you might need to allow showing hidden files as per instructions here)
5 comments
Instead of trying to work out the following directory
C:\Users\your username\AppData\Local\Sonarworks\SoundID Reference\Measure- Just visit '
%localAppData%' which will take you straight to C:\Users\<your username>\AppData\Local\====
I have some questions too. I've installed on two PC's that both use Native Instruments ASIO drivers along side Focusrite ASIO Drivers, both machines have refused to run 'Measure' app and crashed in the desribed fashion. Why can't this ~£300 application get around this crash without manual user intervention and why can't it auto submit crash logs into a ticket without manual uploading of logs?
The above doesn't feel great for those who aren't 'savvy' with Windows Registry and editing configuration files. It feels like an incomplete product in that sense.
I would have expected the app to show at least some sort of error code or reason for crash rather than just a link to create a ticket with support?
I'm most happy to help where I can to test and gather logs to help move forward with this one.
Hi @..., thanks for your comment, sorry to hear you have encountered some trouble.
The Measure app will blacklist drivers which are known to cause some issues to avoid the app from crashing. There might be others potentially problematic drivers which the app does not blacklist automatically though, thus they will have to be blacklisted manually by the user. In these cases, we can also take note of what the problematic driver was for future knowledge.
I've shared your feedback regarding the crash log submission - thanks for your input on this! At the moment, we don't have such a feature in place for the Measure app, but log files can still be sent to our support team for further investigation. I will open up a support request on your behalf, so we can look further into the issue you are experiencing. You will receive a notification about this.
To help us out, it would be great if you could recreate the issue and extract the latest Measure log files from the Sonarworks folder, for locating log files, see our guide here: Locating SoundID Reference log files (find the newest folder with the 'SoundIDReference Measure' mentioned in tje title, recognize it by the date and timestamp).
It also seems we had some information regarding the hidden AppData folder missing in the guide, I've updated this as well, thanks!
I've had this product 2 months now and haven't been able to use it, even with support remoting in to my pc to sort it out, I'm getting them blaming my equiptment, but other apps can measure no problem.
The software is so bad, if the distance is wrong so you measure again it keeps doubling the distance, so for instance I measured my distance was 199cm, I sit around 90cm from the speakers, so I ran it again and now it's showing 854cm on the left and 309cm on the right, it doesn't matter what signal type I use either, I asked for a refund but because support took over 2 weeks to get back to me they said I was soutside of the 2 week cooling off period, I would avoid this company until they sort out their product and customer service.
Folks, I really hope you make this blacklist issue more visible. Like at the top of the list.
More like a topics on how to UN-BLACKLIST an ASIO driver.
I wasted hours trying to get this thing to work, only to realize that it was trying to use a Generic ASIO driver in place of the actual ASIO driver for my Apollo. Apparently, at some point (unbeknownst to me, as I'm a new user), the ASIO driver for the Apollo got blacklisted.
You really should put in BIG PRINT on the “Select your microphone input channel” that "If you DON'T see your sound card's ASIO driver listed, it may have been mistakenly blacklisted. And please check here to learn how to resolve.
But even better, like other applications on the market, it really shouldn't be a big deal to add a button on the “Select your microphone input channel” screen which says, if you don't see your ASIO driver listed above, please click here, and then present a UI, where the blacklisted drivers are shown, and you are provided with the means to de-blacklist an ASIO driver and reload the software.
I have yet to go back and try to complete the room measurement portion. And while I appreciate that it's really cool to do real time delay calculations, it's a real hassle where the app is guiding you to place the microphone in particular positions that you consider an option where you:
a) do your normal process, where the app guides you where to place the mic, does the sample, and then moves on through the 37 different samples.
or
b) provide a manual method (where god forbid, similar to IK Multimedia's ARC), where you simply provide approximate locations to place the mic, and then your app does the measurement.
I really prefer to put the mic on a mic stand, place it in the necessary locations, one at a time, and then have the app do the measurement.
Planning my switch from REW, as I want to get more serious.
I’m currently using the free trial of SoundID Reference. My Native Instruments interface channels wouldn’t show up.
“3 out of 11 found this helpful.”
This manual wasn’t helpful. There are no additional manuals for troubleshooting. There are no proper error codes in SoundID Reference, no ASIO drivers to be found in Regedit, and I’ve reinstalled all drivers. There’s no indication of which driver is supposedly causing the problem.
This is not what I expect from professional paid software. There should be an error code or at least a visible log showing what the issue is.
0/10 Lost a potential customer. I’ll be looking into competitors.
Huge L
gg