ASIO4ALL and MiniDSP Umik-1 issue

alandbush

Registered
Thread Starter
Joined
Jun 30, 2017
Messages
6
Hello John,

Windows 10 Home 64 bit laptop
Java 8 update 191 (64-bit)
REW V5.19 Beta 11 64 bit
MiniDSP Umik-1

Setting the Soundcard preferences to ASIO, 48kHz, ASIO4ALL v2, I am able to select the Umik as input via the ASIO control panel.
No issues and all works very nicely.

Update to REW V5.20 beta 2 and ASIO4ALL indicates that the Umik is in use by another application. Needless to say, I don’t think it is.

I made the mistake of starting the new beta install whilst REW was running. An appropriate message popped up to indicate my stupidity and after closed REW continued the install successfully. I wondered if a ‘Umik in use’ marker had been set during this process.

I subsequently ‘updated’ back to V5.19 and found that all worked again as before.
I closed V5.19 and installed V5.20 only to have the same issue of the Umik in use.

I have rebooted the laptop a few times, even uninstalled and installed the Umik, but all to no avail.

I know you have replied on other threads that ASIO has been tested but I have run out of ideas as to how to progress.
 

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,298
Thanks, I have been able to reproduce this, though I don't know what is causing it yet. ASIO4All looks to work OK with the V5.19 release version. FlexASIO V1.1 works with V5.20 beta 2, though it is more complicated to set up as it lacks an interface, a config file (FlexASIO.toml) is required. Here is a simple example of the one I used if that is of interest, but I'm not using an HDMI output:

backend = "Windows WASAPI"

[input]
device = "Microphone (Umik-1 Gain: 18dB )"

[output]
device = "Analog (1+2) (RME ADI-2 DAC)"
 

alandbush

Registered
Thread Starter
Joined
Jun 30, 2017
Messages
6
Phew! I’m glad that I’m not wasting your time unnecessarily.

Thankyou for mentioning the alternative universal ASIO driver which I was unaware of. I’ll try this out some time.

Meanwhile, I’m more than happy with V5.19. It was the improved accuracy of the timing reference that intrigued me.

Good luck in debugging the issue.
 

John Mulcahy

REW Author
Joined
Apr 3, 2017
Messages
7,298
The 'UMIK in use' problem has stopped happening of its own accord on my test system, unfortunately. There was a Windows update in the meantime, though no indication anything in that update should have affected ASIO4All or the UMIK. I've made a couple of tweaks in the ASIO handling anyway, but I couldn't find any reason the UMIK should have been flagged as in use.
 

alandbush

Registered
Thread Starter
Joined
Jun 30, 2017
Messages
6
Thanks for the update.

I also received a Windows update, on the 12/12/2018, and so with hopes raised I tried v5.20 beta 2 again. Unfortunately, these hopes were quickly dashed as the Umik is still considered to be in use.
 

Manos

Registered
Joined
May 24, 2017
Messages
1
Hello i have the same problem with the 5.2 version.
LAPTOP :Lenovo T420 win 01 64 bit.
With the 5.19 version i did not have this issues.
 

EarlK

Member
Joined
May 22, 2017
Messages
221
Hello i have the same problem with the 5.2 version.
LAPTOP :Lenovo T420 win 01 64 bit.
With the 5.19 version i did not have this issues.

Manos,

After reading your post I dusted off my ( mostly ) retired UMIK-1 to see if it still worked on this Win10 64bit machine ( REW 5.20 beta6 ).

Now it had been working earlier this year, but yes indeed it was no longer accessible through ASIO4ALL ( v2.13 ) > though as always, it was available for use with the JAVA drivers.

I guess another Windows update ( or graphics driver update ) was loaded auto-magically and broke a working system ( again ).

Anyways, its now working ( after about 5 minutes of effort ).

I eventually went to Windows "Open Sound Settings", choose a different default input for my Windows machine ( in my case the builtin 2-chnl Realtek soundcard ) leaving the "Exclusive Settings" as they were found ( both check-marked ) and then rebooted my computer twice ( just for good measure ).

This freed up the UMIK-1 mic making it a "selectable" choice within ASIO4ALL ( where previously it had the dreaded big red X across it > denoting it was "in use and unavailable to ASIO4ALL" ) .

You might try this method to "disconnect > un-stick" the UMIK-1 from being committed to the Win10 systems software.

:)
 
Last edited:
Top Bottom