Problem with RTA measurement

[Robin1]

Hello.
I have been having problems with RTA measurement for some time. Often, after pressing the "Start RTA" button, the frequency response measurement does not start. A strange graph appears. The microphone is inactive. I have to restart the RTA measurement. Then the measurement starts. Sometimes I have to restart it several times in a row. I use Umik-1. I made a video of this problem. At 0:04, I start the measurement, but it is blocked. Then, at 0:16, I restart the measurement and it measures correctly.

Thanks for help. Sorry for my english.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[John Mulcahy]

The video is blurred so I can't see what the input is, what driver you are using or what REW version. If you are on Windows use the Java drivers and choose the input for the UMIK that starts "EXCL".

 

[Robin1]

OK. I made better quality video. I made three attempts to run the RTA measurement. The first two failed. Only the third attempt was successful.

Im on Windows 11 Home 24H2 64bit

 

[John Mulcahy]

That's certainly pretty strange behaviour, I haven't seen anything like that before. You could try the mic in another application to see how that behaves.

 

[Robin1]

I discovered two things:
If the measurement is blocked after starting RTA, it will unblock itself after about 15 seconds and start measuring (see the new video in the first post).
And the second thing: I installed REW on another computer (Win10) and everything works fine.

 

[John Mulcahy]

There were some Win11 USB audio issues reported a little while ago, but I don't know which builds were affected.

 

[Robin1]

OK. I'll try to do something with Windows. Thanks.

 

[Robin1]

It's definitely a Windows11 issue.
I just installed REW on a desktop computer running Windows11, and the error occurs just like on my laptop.
I'm just surprised that no one is reporting this error.