anyway this works for me , so it turned out ok
ASM , steve
thank you for your time trying to help , i appreciate that a lot!!
anyway this works for me , so it turned out ok
ASM , steve
thank you for your time trying to help , i appreciate that a lot!!
In the world of MIDI it is quite common to interpret NoteOn velocity 0 as a NoteOff message. While Cubase itself generates NoteOff messages to end notes it should actually send NoteOn message with velocity = 0.
While the internal midi monitor of Cubase displays such data as NoteOn…
…using an external midi monitor shows the real data:
The example with Zebra should also work with Cubase. However, if you use a different instrument it could be interpreting the vellocity 0 message as a NoteOff.
I need to correct myself a bit. Unlike for midi ports it seems Cubase does not send VST NoteOn events to a VSTi when the velocity = 0. So you’ll have to use always velocity 1 or bigger.
For those interested where the 0 for not off comes from….
In the days that midi was only send through cables at a pretty low speed, they invented something to speed things up a litle. Normally a midi note has 3 messages, this is a note, which note and the velocity. so 3 bytes. Then they invented running mode, so for the period you only send notes and no CC or sysex, you only have to send the note and the velocity, but then a note off command would break running mode because that is a different byte. So the made the note plus velocity 0, note off without breaking running mode. Same with sending CC, in running mode only which CC and value. This made midi 1/3 faster.
This is written by me from my memory, no Ai.
Cheers
Velocity 0 for Note-off: A fossil from the MIDI Stone Age ![]()
MIDI is a fossil from the MIDI Stone Age. Should have been succeeded by something better ages ago, but here we are…
It’s been over 20 years now since I first read about the MIDI Association working on updating the MIDI standard. About f’n time, I thought to myself. And here we are, still waiting.
Slow and steady wins the race!
We should be at Midi 3.0 by now.
This is my thought too! If I were in the association I would troll by announcing the 3.0, or even something more exotic like “MIDI X” upon the release of Windows MIDI Services upcoming package.