Unable to load the driver for ASIO4ALL v2

[thothsong]

I'm getting the above Failed to load driver dialog when starting up REW 5.20.4 with ASIO4ALL 2.15 Beta 2, which has worked fine with REW versions up until now. Maybe some Windows 10 update broke things? I can dismiss the dialog and then go into Preferences and successfully select ASIO4ALL v2 just fine. Log file shows:

Dec 04, 2021 7:11:17 PM roomeqwizard.RoomEQ_Wizard main
INFO: REW V5.20.4 running Azul Systems, Inc. JRE 1.8.0_302 64-bit on Windows 10
Locale: language en, keyboard US, windows-1252 at 96 DPI
Dec 04, 2021 7:11:20 PM roomeqwizard.RoomEQ_Wizard$5 run
INFO: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Dec 04, 2021 7:11:22 PM com.synthbot.jasiohost.AsioDriver <clinit>
INFO: Loaded jasiohost64.dll
Dec 04, 2021 7:11:24 PM roomeqwizard.E B
INFO: java.lang.NullPointerException

 

[thothsong]

Strangely, today the problem has disappeared.

 

[John Mulcahy]

If you attach a zipped copy of the whole REW log files folder I can take a look.

 

[thothsong]

Not sure how much help it will be, as old logs have cycled out.

 

[thothsong]

FWIW, this just happened again, current logs attached. In a session shortly before this one, I had a UMIK-1 and HDMI out to a sound system connected, no problems. For this subsequent launch, neither UMIK-1 nor HDMI out were connected.

 

[John Mulcahy]

I've added a bit more debug logging for the next build to see where the error occurs, but I guess it is related to trying to reload inputs or outputs which are no longer present. If you see it with the next build please attach the log folder again.

 

[thothsong]

Thanks, will do.

 

[pdiprete]

I don't know if this is related, but I have recently uninstalled and re-installed ASIO4All multiple times trying to chase down an issue with USB Microphone ordering (John knows about this one, too).

The first time starting REW after uninstall / reinstall of ASIO4All, REW reports that it's unable to load the device driver when "reload"ing the input devices. The stacktrace shows its in a ~getfilters~ call. I'm likely to do this again tomorrow, so I can capture the stacktrace when it comes up, if that's helpful.

NOTE that this is NOT FATAL. After the reload and opening the ASIO4All control panel, one can select the device and sample rate, and you can carry on.

 

[John Mulcahy]

The first time starting REW after uninstall / reinstall of ASIO4All, REW reports that it's unable to load the device driver when "reload"ing the input devices. The stacktrace shows its in a ~getfilters~ call. I'm likely to do this again tomorrow, so I can capture the stacktrace when it comes up, if that's helpful.

Yes, useful to see the error info.

 

[pdiprete]

I'll post later today... just waking up.

Would yesterday's stacktrace have been recorded in a log that I can find, or is it only available to the user at the time it occurs in the GUI?

 

[John Mulcahy]

It will have been logged.

 

[pdiprete]

Don't wait on me; I reinstalled both REW and ASIO4All for a different reason.
I didn't save the original log, and the error hasn't come up today; I'll post if I run across it again.