ASIO and Intel Display driver distortion/noise

[phil faulds]

HI all,
First let me say that REW is one of the best examples of web democratization I know of (along with Notepad++). John M. is a hero, and I donate to the project every year or so. You could spend a lot of money for software that's nowhere near as good (and I have.)
At some point since I last used REW to EQ my surround system (Dec 2023), I think a Windows 11 update has sabotaged me. Basically the setup is W11 PC/laptop->Intel Display Driver->Outlaw 976 over HDMI. It has been working perfectly up till now. Now I get static popping and dropouts when I send test signals or sweeps (spitting, machine gun type noises.)
A web search turned up a thread from 2021, and I followed all the suggestions there re: buffer size etc. to no avail. Also backed out the latest version of REW, and tried previous version(s). So far, nothing has worked.
Has anyone else encountered these problems (ASIO+Intel HDMI) recently? And is it time for a Linux REW or am I just a dreamer?
Thanks,
Phil

 

[John Mulcahy]

Instead of ASIO try the Java WASAPI Exclusive drivers, select Java and pick device names that start with EXCL.

 

[phil faulds]

Thanks John
The surround channels are available.
Now I can't seem to get the Motu M-2 to work with Java EXCL or regular drivers.
No matter what bit rate I try, I get one of these (32-bit for EXCL, 16-bit for regular.)

The Motu seems to be 24 bit exclusively and doesn't allow 16 or 32 bit options:

Can't see any setting in REW to change this either: "Treat 32-bit data as 24-bit" doesn't seem to do anything.
Any ideas?

Thanks
Phil

 

[John Mulcahy]

The issue there isn't the bit depth, the driver is refusing to provide a data connection. That could be because something else has locked the interface for its own use, or perhaps there is some issue with the WDM drivers. It might be worth trying to reinstall the latest MOTU drivers. Alternatively, if you were previously using ASIO4All you could try FlexASIO.

 

[phil faulds]

Thanks so much for that clarification. I have no idea why that was happening on my HTPC, but I switched to my laptop and the Java drivers work just fine.