I’m having an issue where when my audio interface is disconnected while GP is running, I get the red screen telling me to reconnect or select a new interface from the options dialog. When I reconnect, the program never returns to normal.
The audio interface works with other programs when it is reconnected but GP remains hung up with no ability to do anything. My audio interface is an iConnectAudio 4+ with the latest drivers.
I need this program to be able to recover from a pulled USB cable fairly cleanly in order to use it in a live situation and the error message seems to tell me, this should behave differently in this situation
Direct connection. Same slot. It’s being unplugged from the interface side. I’m simulating a problem I’ve had in the past where the plug comes out in the rack
Good suggestion, but same behavior. I even made sure my PCs internal sound card was the card that ASIO4ALL was set up with and it still won’t fallback to it
This seems to be completely driver dependant on Windows systems. If the driver somehow crashes because one just pulls the cable out we’ve seen devices that must be powered off and then back on before they continue to work.
I’ve had similar instances with my Focusrite 18i20 2 gen audio interface on Windows, with all drivers through to current version for as long as I’ve own GP (a couple years). If the rack-mount audio interface gets disconnected or loses power, GP crashes (locks up), and most times, Windows does as well (locks up). However, I don’t think Windows locks up if GP isn’t running and the audio interface is disconnected. I just try to make sure that my connections are tight.
Sounds like a job for some hot glue as once the computer is in my rack I will not be unplugging the cable.
With my new setup, it will be less of a problem as it’s just going from the interface to a rack PC. My current setup has the wire going out of the rack and up to my Surface Pro tablet which makes it much more susceptible to the other end loosening
I’m kind of getting it to work (don’t ask me how), but getting some other weird issues with this interface so it may be a hardware issue. This is my old live rig interface which I switched out after having some strange gremlins, so it’s likely to be related to this problem.
I will test it out with my live rig when I get a chance to see if that works better. Either way this interface is discontinued, and I may just go with a different one moving forward. I’ll post another topic for suggestions on that. Thanks for everyone’s help!