payukon

I GOT IT TO WORK !! Instead of disabling the 'FBV Shortboard Mk II' device, disable the 'USB Composite Device' to where the shortboard belongs For example if the Shortboard has a hardware id of USB\VID_0E41&PID_5056&MI_00, then disable USB\VID_0E41&PID_5056 without the last &MI_00 That powers off the Shortboard and then to power it on just enable the disabled 'USB Composite Device' Here's a cygwin command which disables the shortboard devcon disable `devcon find 'USB*' | fgrep 'FBV Shortboard Mk II' | sed 's/\(USB\\\[^&]*&[^&]*\).*/\1/'` And a command which reenables it devcon enable `devcon findall 'USB*' | fgrep 'FBV Shortboard Mk II' | sed 's/\(USB\\\[^&]*&[^&]*\).*/\1/'` If you put them on a script around your DAW launch, you can have your shortboard enabled during and only during your DAW session

It's not a bug of Windows: with the 'KORG MIDI Device' the device manager shows no error when reenabling the Shortboard but no midi messages are received further. So it's a bug of the Shortboard firmware :(

Seems a bug on the Win7 usbaudio.sys driver because forcing the shortboard to use the generic "KORG MIDI Device" driver from KORG fixes it. I haven't found any hotfix from microsoft to address the problem, but with the KORG driver it works as it should.

I have the latest firmware on the shortboard and I'm using Win7 x64 with the hotfix KB2919139 installed (USB MIDI update). Now if I disconnect and connect the shortboard to the USB port, the device keeps working as it should. However, if I disable and enable it on the device manager (control panel), windows says the device cannot start (code 10). Could you test if it happens to you, so I can know if it's a problem of my system or on the shortboard itself? Thanks in advance! I'm programming a script which disables and enables the devices I need when I launch the DAW software and I would like to disable and enable the shortboard without disconnecting it.