Oct 11, 2006 at 11:31am
Whenever i put a pair of note-number velocity values into midiformat it churns out a note on message, even if the velocity is zero. I.e. i churns out 144 64 0 say, rather than 128 64 0. Why? (even the help on midiformat does that – so it can’t be me). I was under the impression that the midi code for note-off was 128-143 (one per channel) and for note-on it was 144-159.
also if i pack up the messages midiformat dishes out and prepend “midievent” to them, when i pass the message onto vst~ i get no response. but if i pass the message through a messagebox to reformat it, it works. Why is that? What’s wrong with the format?
Oct 11, 2006 at 12:11pm
> Whenever i put a pair of note-number velocity values into
noteoffs are usually treated as simple noteons with a velocity of 0.
> also if i pack up the messages midiformat dishes out and prepend
i think you have to be more specific, if you want help on that one.
Oct 11, 2006 at 12:38pm
What i mean by ‘reformat’ is that if a message saying “midievent 144 64 72″ goes straight to vst~ from midiformat as in diagram A, vst~ does nothing.
(sorry that diagram’s a bit bad….)
Oct 11, 2006 at 1:51pm
> What i mean by ‘reformat’ is that if a message saying “midievent
why don’t you simply send a patch?
i wonder in what way vst~ reacts to your messagebox approach. do you
but you can easily build the correct message yourself.
#P window setfont “Sans Serif” 9.;
Oct 11, 2006 at 2:13pm
as far as posting a patch – when i open the .pat files they look nothing like the things you guys post on this forum! And i can’t load your patch, max opens it as a text file… ??? am rather new to this forum, sorry.
anyway, vst~ plays notes when using my messagebox approach, although the timing is a bit off, and it just strikes me that this is the *wrong* way to be doing it. I have tried packing the note number and velocity together and prepending “midievent 144″ (or 128), as i think your patch does, but vst~ then doesn’t react. it makes no noise.
have attached both versions as a patch to this post.
Thanks for your help btw!
Oct 11, 2006 at 3:09pm
On 11 Oct 2006, at 16:13, Tom Giles wrote:
> as far as posting a patch – when i open the .pat files they look
you select the text and copy. then go to max and do “new from
> anyway, vst~ plays notes when using my messagebox approach,
both your versions work for me (and are different from what you
sometimes vst~ is a little picky about midievent messages, when it
but still your programming is not optimal…
Oct 11, 2006 at 3:42pm
thanks for that. tried earlier on in the day with midiformat but replaced it with the prepend 144 etc whilst discussing this. either way didn’t work for me, and, as you say, both are equivalent.
Oct 11, 2006 at 8:24pm
ok, i’ve found the solution to this problem – the other part of my patch was sending note-offs far too quickly and too often. inserting a speedlim just before the vst~ demonstrated that. so this is all solved.
Oct 11, 2006 at 10:57pm
As to ‘why?’ 144 60 0 for a note off: read the MIDI standard. Pay particular attention to the section labeled “running status.”
If a VST is not grokking note-on-with-velocity-zero as synonymous with note-off, then the VST is broken. Period. I see in this case it turned out that your patch was broken. Auch schlecht.-
The only compelling reason for having MIDI messages 0×80-0x8f is so that you can program your synth/sampler/whatever to respond differently to different note-off velocities (for instance, change the Release parameter of an ADSR envelope or something). Very few MIDI devices seem to take advantage of this capability (or maybe it’s the device users).
Oct 13, 2006 at 7:29pm
Tom Giles wrote:
Yes its much easier to just copy the non working part and paste it into
Then everybody can immediatly try it and help out with your problem…
Oct 13, 2006 at 9:31pm
Peter Castine wrote:
Yes, I know only the Prophet T8 and the Oberheim Matrix 12 had release
Maybe thats it…
You must be logged in to reply to this topic.