MIDI Command sent by Cubase "on Stop"

  • Thread starter Thread starter midifreak
  • Start date Start date
M

midifreak

New member
Hi,
New to the site and I like what I've read so far.

Here's my question....

I have designed and built a simple MIDI I/O interface that uses the MIDI Note On/Off messages to operate 16 digital outputs (Velocity sensitive outputs in Mark 2 version) for operating lighting synchronously with sound. Also sends MIDI Note On/Off messages when one of 8 switches are operated for triggering samplers etc. for sound effects (I'm a member of a drama group and it's something useful to use in plays etc..)

Basically, I use Cubase VST/32 and when I press "Stop" for the second time (Return to start), it crashes my interface. I noticed on the MIDI output activity indicator on the transport bar that "something" is sent to MIDI OUT.

Anyone know which command this is? Mode? Reset?

I have a MIDI Monitor program but can't use it as I only have the one computer and you can't share MIDI ports. (Conflict - bummer!)

Regards

Chris

P.S. Other than that my MIDI IO interface works like a charm!
 
It could be sending a note off on all channels. That's what happens when you press the 'panic button' in software to stop any stuck notes.

Maybe I am misunderstanding but why do you have your interface also hooked up to the Midi Out? Isn't all the communication one way from the controller to the computer?
 
Stop commands

Hi Tex,
It's not a panic button, it's just a normal transport control. '0' (Ins) key on the numeric keypad is stop/restart. Press it once while playing and the sequencer stops, press play "Enter" on the numeric keypad and playing resumes from where you stopped. If you press stop again (a second time in succession) the song pointer returns to the start of the song. This is when my problem occurs.

It could be an all notes off command (Mode command) I suppose, but there's more than one version of that mode command.

The communication is two-way I have push buttons that send note on/off messages for triggering samples etc.. (Read the 1st paragraph, second sentence).

Thanks I'll have another look at my source code.

Regards

Midifreak
 
Midi message on Stop

Hi Tex,
I've checked my source code and added a trap for all the Control Change and mode commands ($B0, cc, vv). I don't bother with the last two bytes, as soon as I decode the status byte as $B0 I reset the processor.

This has had no effect.

It's not a start or stop command because I trap all status bytes starting with $F ($Fn, where 'n' = I don't care).

I wonder if it could be the song position pointer ($F2, ll, hh)...
Even though it starts with $F, I don't handle the next two bytes associated with it. Hmmm, I wonder?....

Back to the source code again.

Does anyone know exactly what the code is to save us/me guessing?....

Regards

Midifreak
 
Midi message on Stop

Hi guys,
I've found the reason. It was a bank/program change command. I thought I had cleared all of them, but I found one on a part I must have missed. Turned it off and it's now fine.

I think I will modify my source code to "swallow" those commands.

Many thanks

Midifreak
 
You must log in or register to reply here.
Back
Top