[Bug Report] Connecting a Midi Controller while Standalone Bias FX2 is Active causes crash and locks out Asio Driver. Windows 10
-
Issue: Connecting a Midi Controller while Standalone bias Fx2 is running causes a crash.
Platform Affected : Standalone Windows Application
Driver Mode : Asio
Steps to reproduce
Boot Bias Fx2 and select preset with Midi enabled or have global midi enabled.
Plug in controller
Application Crashes.Tested against VST and did not see the same behavior.
Midi Controller used, Line6 Hd500x
Also tested with a software midi controller emulation
https://sourceforge.net/projects/vmpk/
caused the same issue this is a hassle and a half to setup so don't recommend it if you can do it with a hardware one. -
@jccunnin3
Solution:
Boot Windows 10
Plug in controller
Launch BIAS FX 2
Enable MIDI
Application works :)Seriously though, you should never plug in controllers while the application that is using them is already running. That's been a long standing no-no in Windows since Windows began. It can work, but there's also a chance you get a crash like the one you experienced.
-
I know how to make it work. This was a live usage issue.
What you posted is not a solution it is a workaround.
-
@jccunnin3 Thanks for bringing this to our attention, we will try to reproduce this issue from here, thank you
-
@myxolydian I agree, while not a recommended practice, I have found that most applications that can use midi hardware have robust ways of handling the presence or absence of a controller. As an example, in Reaper, I can start the program and then plug in all 4 of my USB controllers and then tell Reaper to refresh the device list and BOOM, they are all there.
I think the way BFX2 handles MIDI devices may need some fortifying, as it seems to be good for the average situation, but the outliers bring it down hard.
-
@paul-jones32 We're on this now, thanks
-
@mike I know :-)
