Open GForceWeb opened 1 month ago
Follow Up.
By deleting the OBS-ASIO sources from my scene collection while in Safe Mode so that OBS would start with my scene collection I was able to test adding new OBS-ASIO sources which I found didn't crash.
In OBS31 I was able to select my Rodecaster Pro II directly from the device menu which wasn't possible in OBS30 (I had to use ASIO4ALL) and using this method gives correctly labelled multitrack outputs which wasn't possible in OBS30
So all up I'm not too sure what's going on but something about the OBS-ASIO sources created in OBS30 were causing OBS to crash when moved to OBS31, whereas brand-new OBS-ASIO sources created in OBS31 don't appear to have an issue.
Very Strange
I've been doing some beta testing with OBS31 as it has the capacity for a new profiling tool that's incredibly helpful for optimization and found that OBS was crashing on launch with my scene collection. After a few hours of debugging and trying a bunch of stuff I narrowed it down to the OBS-ASIO plugin.
Running the latest version of OBS-ASIO.
With no other changes:
Logs:
OBS31 is still a 1st beta so there may be something on the OBS side causing this behavior that might get resolved, but it's also possible that an intentional change in OBS31 is causing OBS-ASIO to freeze. I couldn't see much in the logs to point to a cause.