No microphone inputs channel option!!

Hi 30108282 k, thanks for your post, sorry to hear there is some trouble!

If there are no microphone input channels showing up in the Measure app, it's most likely that the Measure app has blacklisted the audio device. For steps on how to resolve this, please see our guide here: No inputs available in SoundID Reference Measure [WIN].

Let us know how it goes and if an issue still persists!

Have the same issue, need help fast. Link above doesn't work.

Same issue here. No microphone inputs appear in the measure app. All drivers are up to date and the measure app is not blacklisted in windows.

Without SoundID Reference the microphone works well.

Audio interface is Steinberg UR22 MKII

Mic is a SoundID Reference Measurement Microphone

Support needed!

Try to look for Asio drivers for UR22. I don't know UR22 MK2 but if it uses general purpose usb driver or some kind of universal driver, you need to find Asio for you dedicated for your machine. Try to search at forums, or YouTube. Maybe older driver would work better. 

In my case, behringer umc 22 didn't work either on current driver. I've found old, obsolete drive for this device and it works properly. 

retip66 Alexander Olk thanks for commenting! 

Some content has been merged and moved, and it looks like the article link above stopped functioning. I've fixed it, you will find the answer to the issue here: [WIN] No inputs available in SoundID Reference Measure.

Let me know if you're able to resolve it via the blacklist file, thank you! 

I have removed the blacklist file, but this has lead to a crash of the measure app.

retip66 Unfortunately I couldn't find any other drivers than the ones from Steinberg itself.

There is still no solution for me.

Edit: I gave it a final chance and suddenly it worked. The microphone input was detected while the phantom voltage was switched off. After switching it on, also an input level was there. At the weekend I will try to run a measurement session.

Thanks already for your support so far!

Update:

A) Firmware and driver of the Steinberg UR22 MK2 are up to date.

     Unfortunately Windows doesn't let me (that easy) installing an older driver for the UR22 MK2.

B) When I start the systemwide app, no microphone input appears.

C) Starting directly the measure app, both microphone inputs appear and I can select one of them. But after selecting the audio interface, I got the message that I'm using different audio devices for input and output. Well, input and output is both on the UR22 MK2. If I ignore this message, I can proceed to the room measurement, but I stuck at the 37 measurement points. The indicator is jumping around and the measurement doesn't work.

I assume that the wrongly detected audio interface is the reason for the jumping indicator.

Kārlis Stenders Are there any further options?

Alexander Olk The blacklist file is updated following such crashes, and the problematic driver (the one that led to the crash) is blacklisted. In most cases, the crash would have been a one-time occasion only due to some unique circumstances at the time, so usually removing the entry from the blacklist resolves the issue. But in rare cases, the crash may be constant too, which means it crashes again after removing the entry from the blacklist, resulting in a crash/blacklist removal loop. 

I cannot be sure what exactly resolved it in the end (I'm guessing some configuration/setting aspect on the device/driver), but nevertheless, I'm glad to hear it's resolved now and you're able to proceed further! 

For the follow-up issue with “jumping mic” on screen, please follow the directions here (especially the Extended Setup Checklist and Hardware Setup sections): SoundID Reference speaker measurement troubleshooting guide

Sorry for my late response, I was on vacation.

It isn't yet solved. The issue still persists and I followed all your troubleshooting guides (incl. the one for the "jumping mic").

Well, it seems that I have to give it up now. Maybe I should try it with another audio interface.

Hi, just a short update from my side. After the latest update, I started the measurement again and it worked perfectly.

Thanks!