Muff's Modules & More

[HeWhoWantsJeans]

Hey kids,

I've received 0 responses on Cubase.net about this, and while I think it's frowned upon to admit the use of a DAW, I'm hoping that anyone in here might have any idea what-the-fuck-is-going-on.

I've found a bug that I can replicate where my MidiSport 8/8s will get dropped from Cubase (though the system still recognizes it, as my CME MotorMix still interfaces with LUI Plus even after Cubase drops it).

-Send Midi-clock to a device
-Also send performance information (either pitch bend information or a slew of notes, but the problem is more practically illustrated with the pitch bend scenario) to the same device.

Cubase will, without fail, drop all midi-output. Midi-input still functions, as the lights on the MidiSport 8/8s still activate to show reception of information, but the output lights are dead (note: Cubase only, as LUI Plus activity will be reflected on the LEDs just fine). Is there any kind of 'protection' in Cubase that will drop an interface if an excess of information is being sent?

My system setup is as follows:

AMD Phenom 9950
Gigabyte MA790X motherboard
2.49gb RAM (limitation from 32bit OS)
Windows XP, Service Pack 3
Cubase 5.1.1
M-Audio MidiSport 8/8s (with more recent drivers)

Gracias, 'Wigglers.
Erik

[dkcg]

Do you have another computer you could test the midisport out on? At least rule it out at the problem. I got one of the later grey M-Audio Midisport 8x8s, No problems here, but I vaguely remember it needing to go straight into my machine on an older machine (i.e. no usb port).