Graceless Shadow
I'm using a Windows laptop and a Hercules Inpulse 500 controller, and I've been having trouble with VirtualDJ freezing/dying in the middle of my sets, both when music I'm mixing and when it's been sitting idle. The app will just stop the music playing and won't respond to any input involving playing music, either with the controller or mouse/keyboard. When I go into the audio settings, there are error messages where the sample rate should be. I have to disconnect/reconnect my controller and restart the software to get it to go again.
When I go into the event viewer in windows, the problem was listed as an application hang, just says "The program virtualdj.exe version 8.5.9295.0 stopped interacting with Windows and was closed"
It seems like the program is randomly losing communication with the controller, but I don't know why, or if it's a problem with the program or controller.
Pertinent info:
-using the newest version of VDJ, pro license.
-all drivers are updated, I've reinstalled the Hercules Asio drivers.
-all of my usb ports are set to not allow the computer to turn them off for power saving.
-computer is brand new, about a month old. I5 ultra processor. I've gotten rid of as much of the bloatware that came on it as I can. Controller is a few years old.
-have tried different USB cords, both usb A and usb C, no usb hubs just direct connection, doesn't seem to matter.
-the Hercules is not assigned as the windows audio output device.
-Asio driver defaulted to 256 samples, not sure if changing that would help.
I can post the extended problem reports on them if that would help at all. It's only happened a handful of times but that's too many. Any help/suggestions are greatly appreciated as I have a show on the weekend and would very much not like for it to die in the middle of that.
When I go into the event viewer in windows, the problem was listed as an application hang, just says "The program virtualdj.exe version 8.5.9295.0 stopped interacting with Windows and was closed"
It seems like the program is randomly losing communication with the controller, but I don't know why, or if it's a problem with the program or controller.
Pertinent info:
-using the newest version of VDJ, pro license.
-all drivers are updated, I've reinstalled the Hercules Asio drivers.
-all of my usb ports are set to not allow the computer to turn them off for power saving.
-computer is brand new, about a month old. I5 ultra processor. I've gotten rid of as much of the bloatware that came on it as I can. Controller is a few years old.
-have tried different USB cords, both usb A and usb C, no usb hubs just direct connection, doesn't seem to matter.
-the Hercules is not assigned as the windows audio output device.
-Asio driver defaulted to 256 samples, not sure if changing that would help.
I can post the extended problem reports on them if that would help at all. It's only happened a handful of times but that's too many. Any help/suggestions are greatly appreciated as I have a show on the weekend and would very much not like for it to die in the middle of that.
Posted Tue 16 Jun 26 @ 2:11 am
luneknight85
Just found out windows broke Midi this year, gg Microsoft.
Posted Tue 16 Jun 26 @ 4:19 pm
locoDog
they actually didn't, no undeserved love nor hate to m$. (and everyone has reasons for both)
They updated to midi 2.0 spec and in the process broke some bodged 3rd party drivers.
Only fault on m$ is they pushed the update with a blind spot for controllers, they had a midi guy and he worked with instrument makers and DAWs, it just wasn't considered that some controller makers have janky drivers.
They updated to midi 2.0 spec and in the process broke some bodged 3rd party drivers.
Only fault on m$ is they pushed the update with a blind spot for controllers, they had a midi guy and he worked with instrument makers and DAWs, it just wasn't considered that some controller makers have janky drivers.
Posted Tue 16 Jun 26 @ 6:57 pm
Graceless Shadow
locoDog wrote :
they actually didn't, no undeserved love nor hate to m$. (and everyone has reasons for both)
They updated to midi 2.0 spec and in the process broke some bodged 3rd party drivers.
Only fault on m$ is they pushed the update with a blind spot for controllers, they had a midi guy and he worked with instrument makers and DAWs, it just wasn't considered that some controller makers have janky drivers.
They updated to midi 2.0 spec and in the process broke some bodged 3rd party drivers.
Only fault on m$ is they pushed the update with a blind spot for controllers, they had a midi guy and he worked with instrument makers and DAWs, it just wasn't considered that some controller makers have janky drivers.
Yeah I've been on the midi discord talking to the dude from Microsoft and a guy from Hercules. The cause seems to be related to a kernel level hang with the Hercules driver. So not midi related but still haven't been able to find out why.
Posted Thu 18 Jun 26 @ 11:40 pm