Class Compliant MIDI devices crash in Win7 64bit

[Cartman1227]

Hello Rob,
on my Win7 64bit desktop machine I have 2 Alesis TiggerIO + 1 MIDI Expression (newest firmware and MIDI Expression Control software) as Class Compliant MIDI Devices.
So I'm running Cubase for e-drumming and MIDI Expression is generating CC04 values from the hihat controller. Especially when being idle (not playing) these MIDI Devices randomly crash. One time MIDI Expression fails together with one of the Alesis, another time all three fail, a third time both of the Alesis fail and ME is still there...
When running only both Alesis (or together with another Class Compliant midi-keyboard, or together with native Roland TD-11 MIDI drivers) nothing fails or crashes. Only when the MIDI Expression device is connected the crashes appear.
All midi devices are controlled by the motherboards USB3 host controller that is switched to legacy support. I did not have problems with any other (Class Compliant) USB-MIDI devices or applications on this machine in the past.
The USB cable for the MIDI-Expession is a 2 meter "Lindy"-cable http://www.thomann.de/gb/lindy_usb_20_k ... _amini.htm.

Any ideas or experiences like this?

[Rob]

No, I haven't heard of any issues like this. What does 'legacy' support mean. I'm not sure if that should be necessary.

[Cartman1227]

That's the default BIOS-Setting for USB3 controllers. It means that they also work with old USB protocol (USB2, USB1)

[Rob]

Can you give me some complete specs on you system, motherboards, cpu, memory, video, etc?

[Cartman1227]

MSI B85M-E45 , Intel Core i5 4670 , Intel HD Graphics 4600 , 4GB Corsair XMS3 Classic DDR3-1600 DIMM CL9 Dual Kit , Win7 Ultimate 64bit SP1

[Rob]

Thanks for the info. I'll do some searching and see if I can't find anything. You say it occurs after a long period of inactivity? Could this be related to some kind of USB power saving option? All the devices are connected direction to USB ports (not a hub)? And can you clear up what you mean when you say 'crash'? And what do you need to do in order to get things working again?

[Cartman1227]

You say it occurs after a long period of inactivity?

Inactivity - yes , but long period - no : can be half a minute. it did not fail while I was playing (until now... )

Could this be related to some kind of USB power saving option?

No, because my Windows settings don't allow USB power saving.

All the devices are connected direction to USB ports (not a hub)?

They are connected to the USB3 Root Hub that is running under the motherboard's USB3 host controller. All the physical USB ports (the blue USB3 ones and also the black USB2 ones) of that machine run under the USB3 Root Hub.

And can you clear up what you mean when you say 'crash'?

Cubase does not crash and the devices are still listed at the device manager in Windows - but there is no more midi activity. I hit on the edrum-pads (that are connected to the Alesis and play the hihat pedal (that is connected to MIDI Expression) and in case this particular device "crashed" there are no Midi notes and values anymore that are sent.

And what do you need to do in order to get things working again?

Close the DAW, then pull out the USB cable of the device with the failure and re-connect it to the computer.

[Rob]

Last question. The next time the midi expression stops sending midi data, can you check if the control app still works.

[Cartman1227]

ok, good idea. I will report back asap

[Rob]

I know why the MIDI Expression stops sending MIDI data, but I can't explain why the Trigger I/O's are not happy yet. The problem arises when using MIDI Expression in conjunction with DSPT 1.5.0.6. This will not be an issue using DSPT 1.6. I can make a firmware update for the MIDI Expression to stop this from happening.

Regards,
Rob