Discussion:
MIDEX3 MIDI Outs blink/transmit every 2.1 seconds! Help, please!
(too old to reply)
novice
2005-12-17 07:45:52 UTC
Permalink
I'm using Cubase SX 3.0.1 on a Dell Dimension 8400 WinXP system, with
an SB Audigy 2 ZS sound card and a Steinberg MIDEX3 USB MIDI
interface. I've downloaded and installed MIDEX3 firmware and driver
1.93.

Am in the very early stages of setting everything up, using a Yamaha
KX88 controller keyboard. Cubase is correctly receiving the MIDI
signal through MIDEX3; it records and plays back through the Audigy
card just fine.

However, for some odd reason, my computer seems to be sending some
sort of MIDI signal approximately every 2.1 seconds - the MIDEX Out
lights (all three) come on for about 2.5 seconds, then they go out and
it works normally for about 2.1 seconds, and then this repeats
constantly.

This of course screws up the playback of any external synth module
connected through the MIDex3 - the module works fine for a couple of
seconds, then receives that bad MIDI signal for a couple of seconds,
over and over.

BTW, an annoying clicking sound accompanies this
lighting-up/transmitting of the 3 MIDI Outs until Cubase SX is
actually booted. Once Cubase begins running, the clicking sound goes
away, although the blinking/transmitting continues. (Perhaps this
might be a clue as to what's going on.)

What is causing this MIDI Out problem and what is the solution? I'd
greatly appreciate all suggestions.
s***@gmail.com
2005-12-17 14:56:54 UTC
Permalink
What, if anything, is connected to your MIDI IN ports? Does
disconnecting it help the problem? If so, you may have stray timecode
running through your MIDI system.

Another possibility is that your interface is reacting to active sense
(or the lack thereof) and sending extended panic messages.

Does your interface driver software allow you to specify routing and/or
filtering for specific kinds of messages? If you can, check for loops
and make sure that MTC and SMPTE are disabled ( unless, of course,
you're using them).

Failing that, can you enable a record track and capture the data in
Cubase to see what it is?
novice
2005-12-17 19:08:27 UTC
Permalink
Post by s***@gmail.com
What, if anything, is connected to your MIDI IN ports?
MIDEX3 is 1 In, 3 Out. A Yamaha KX88 is connected to the single In
port on the MIDEX3.
Post by s***@gmail.com
Doesdisconnecting it help the problem?
No. Disconnecting the MIDI cable to the MIDEX3 MIDI In has no effect
on the problerm.
Post by s***@gmail.com
Another possibility is that your interface is reacting to active sense
(or the lack thereof) and sending extended panic messages.
Does your interface driver software allow you to specify routing and/or
filtering for specific kinds of messages?
No.
Post by s***@gmail.com
If you can, check for loops
and make sure that MTC and SMPTE are disabled ( unless, of course,
you're using them).
Am using nothing at this point.
Post by s***@gmail.com
Failing that, can you enable a record track and capture the data in
Cubase to see what it is?
No. Cubase SX records without any problem whatever I play on the KX88
controller keyboard. Cubase doesn't seem to "see" whatever is being
sent out every couple of seconds thru the MIDEX3 Out ports.

The problem continues.
SpringDiver
2005-12-17 20:52:03 UTC
Permalink
If all the obvious has been ruled out, load up MIDI-OX and MIDI-YOKE
and some sniffing.

Wayne
Post by novice
Post by s***@gmail.com
What, if anything, is connected to your MIDI IN ports?
MIDEX3 is 1 In, 3 Out. A Yamaha KX88 is connected to the single In
port on the MIDEX3.
Post by s***@gmail.com
Doesdisconnecting it help the problem?
No. Disconnecting the MIDI cable to the MIDEX3 MIDI In has no effect
on the problerm.
Post by s***@gmail.com
Another possibility is that your interface is reacting to active sense
(or the lack thereof) and sending extended panic messages.
Does your interface driver software allow you to specify routing and/or
filtering for specific kinds of messages?
No.
Post by s***@gmail.com
If you can, check for loops
and make sure that MTC and SMPTE are disabled ( unless, of course,
you're using them).
Am using nothing at this point.
Post by s***@gmail.com
Failing that, can you enable a record track and capture the data in
Cubase to see what it is?
No. Cubase SX records without any problem whatever I play on the KX88
controller keyboard. Cubase doesn't seem to "see" whatever is being
sent out every couple of seconds thru the MIDEX3 Out ports.
The problem continues.
SpringDiver
2005-12-17 20:55:25 UTC
Permalink
Do some sniffing that is. You can get the software with user
information at:

http://www.midiox.com/

Wayne
Post by SpringDiver
If all the obvious has been ruled out, load up MIDI-OX and MIDI-YOKE
and some sniffing.
Wayne
Post by novice
Post by s***@gmail.com
What, if anything, is connected to your MIDI IN ports?
MIDEX3 is 1 In, 3 Out. A Yamaha KX88 is connected to the single In
port on the MIDEX3.
Post by s***@gmail.com
Doesdisconnecting it help the problem?
No. Disconnecting the MIDI cable to the MIDEX3 MIDI In has no effect
on the problerm.
Post by s***@gmail.com
Another possibility is that your interface is reacting to active sense
(or the lack thereof) and sending extended panic messages.
Does your interface driver software allow you to specify routing and/or
filtering for specific kinds of messages?
No.
Post by s***@gmail.com
If you can, check for loops
and make sure that MTC and SMPTE are disabled ( unless, of course,
you're using them).
Am using nothing at this point.
Post by s***@gmail.com
Failing that, can you enable a record track and capture the data in
Cubase to see what it is?
No. Cubase SX records without any problem whatever I play on the KX88
controller keyboard. Cubase doesn't seem to "see" whatever is being
sent out every couple of seconds thru the MIDEX3 Out ports.
The problem continues.
novice
2005-12-18 10:34:13 UTC
Permalink
MIDI-OX shows system (RT) activity constantly, as long as the KX-88
controller keyboard is attached to the MIDEX3 input port. This
activity is constant and uninterrupted in the Input port and and all
the Output ports, even when the MIDEX3 MIDI Out lights are on for that
2.5 second period.

When I play the KX88 controller keyboard, system (RT) activity stops
and activity is shown on channel 1 in the Input and all the Output
ports, as it should be.

When I connect a synth module (Roland D-550) to one of the MIDEX3
outputs and play it using the KX88 controller keyboard, the D-550
plays fine for a couple of seconds, then is frozen for about 2.5
seconds, during which it will not respond to the KX88 at all, but if a
note has been played and still held at the moment of that 2.5 sec
freeze, the D-550 will not release the note, even though it's been
released on the KX88.

And keep in mind that MIDI-OX is not showing anything at all unusual
during that 2.5 seconds when the MIDEX3 freezes with the MIDI Out
lights on, even though the signal that gets to the slaved (D-550)
synth does indeed reflect a problem during that 2.5 sec period..

All this leads me to believe that somehow the MIDEX3 is getting jammed
up every 2.1 seconds, and it takes 2.5 seconds to clear itself, only
to repeat that cycle over and over.

*If* this is what's happening - or whatever *is* happening - does
anyone have a suggested solution?
Post by SpringDiver
Do some sniffing that is. You can get the software with user
http://www.midiox.com/
Wayne
Post by SpringDiver
If all the obvious has been ruled out, load up MIDI-OX and MIDI-YOKE
and some sniffing.
Wayne
Post by novice
Post by s***@gmail.com
What, if anything, is connected to your MIDI IN ports?
MIDEX3 is 1 In, 3 Out. A Yamaha KX88 is connected to the single In
port on the MIDEX3.
Post by s***@gmail.com
Doesdisconnecting it help the problem?
No. Disconnecting the MIDI cable to the MIDEX3 MIDI In has no effect
on the problerm.
Post by s***@gmail.com
Another possibility is that your interface is reacting to active sense
(or the lack thereof) and sending extended panic messages.
Does your interface driver software allow you to specify routing and/or
filtering for specific kinds of messages?
No.
Post by s***@gmail.com
If you can, check for loops
and make sure that MTC and SMPTE are disabled ( unless, of course,
you're using them).
Am using nothing at this point.
Post by s***@gmail.com
Failing that, can you enable a record track and capture the data in
Cubase to see what it is?
No. Cubase SX records without any problem whatever I play on the KX88
controller keyboard. Cubase doesn't seem to "see" whatever is being
sent out every couple of seconds thru the MIDEX3 Out ports.
The problem continues.
s***@gmail.com
2005-12-18 16:24:05 UTC
Permalink
The RT data coming from your KX is probably active sense data. Its
purpose is to keep the connection alive so that the receiving module
knows the cable didn't get kicked out. Active sense stops on some
boards when the connection is being used.

There is a common issue in windows with most MIDI interfaces regarding
"high-speed" or "advanced" mode. I believe it has something to do with
interrupts (not the IRQ like on an old ISA machine, but the method used
to precisely timestamp MIDI events), but the problem manifests itself
in a particular way that sounds familiar now. Incoming data trails
along perfectly for a while, stops inexplicably, then comes pouring out
in one big clump. Then everything is fine for a while and it starts
over. I used to get this on my MTAV and cured it by messing with the
drivers, but it was so long ago that I can't remember what I did
specifically to remedy it.

If a note gets stuck in the 550 as you described, does it release after
the 2.5 second hangup? if you play several notes independently during
the hangup, do the come out as a chord when it frees itself? If so, I'd
investigate the driver/os settings. You might want to call Steinberg
too, because I think this is happens pretty frequently.
bronx
2005-12-18 21:52:12 UTC
Permalink
I dont know if this will help--
I had a similar sort of problem---as someone suggested I was able to
see it recorded as midi data--
So if you know WHAT it is, and have an Input filter, you can just
filter it out--

thats what I did...

Hope your problem gets solved!

Peace, Bronx
Post by s***@gmail.com
The RT data coming from your KX is probably active sense data. Its
purpose is to keep the connection alive so that the receiving module
knows the cable didn't get kicked out. Active sense stops on some
boards when the connection is being used.
There is a common issue in windows with most MIDI interfaces regarding
"high-speed" or "advanced" mode. I believe it has something to do with
interrupts (not the IRQ like on an old ISA machine, but the method used
to precisely timestamp MIDI events), but the problem manifests itself
in a particular way that sounds familiar now. Incoming data trails
along perfectly for a while, stops inexplicably, then comes pouring out
in one big clump. Then everything is fine for a while and it starts
over. I used to get this on my MTAV and cured it by messing with the
drivers, but it was so long ago that I can't remember what I did
specifically to remedy it.
If a note gets stuck in the 550 as you described, does it release after
the 2.5 second hangup? if you play several notes independently during
the hangup, do the come out as a chord when it frees itself? If so, I'd
investigate the driver/os settings. You might want to call Steinberg
too, because I think this is happens pretty frequently.
s***@gmail.com
2005-12-20 00:43:46 UTC
Permalink
Please let us know how this works out, btw.
novice
2005-12-20 07:54:20 UTC
Permalink
Post by s***@gmail.com
If a note gets stuck in the 550 as you described, does it release after
the 2.5 second hangup?
Yes.
Post by s***@gmail.com
if you play several notes independently during
the hangup, do the come out as a chord when it frees itself?
No, they're simply ignored and not played at all.
Post by s***@gmail.com
If so, I'd investigate the driver/os settings.
I've already upgraded to the latest MIDEX3 driver, which is V1.93.
Post by s***@gmail.com
You might want to call Steinberg
too, because I think this is happens pretty frequently.
I called Steinberg today, and they asked me to return it to them.
Post by s***@gmail.com
Please let us know how this works out, btw.
Steinberg tech support will have the unit Wednesday. When I receive
their analysis, I'll share it here.
novice
2005-12-28 11:16:22 UTC
Permalink
Post by novice
Post by s***@gmail.com
If a note gets stuck in the 550 as you described, does it release after
the 2.5 second hangup?
Yes.
Post by s***@gmail.com
if you play several notes independently during
the hangup, do the come out as a chord when it frees itself?
No, they're simply ignored and not played at all.
Post by s***@gmail.com
If so, I'd investigate the driver/os settings.
I've already upgraded to the latest MIDEX3 driver, which is V1.93.
Post by s***@gmail.com
You might want to call Steinberg
too, because I think this is happens pretty frequently.
I called Steinberg today, and they asked me to return it to them.
Post by s***@gmail.com
Please let us know how this works out, btw.
Steinberg tech support will have the unit Wednesday. When I receive
their analysis, I'll share it here.
Steinberg tech support received my MIDEX3, tested it, said that it was
bad, and shipped me a new one. I've just finished testing it, and it
seems to work fine.

Thanks very much to those who offered suggestions.

Loading...