From the original SynthMaker forum (2004–2014), with its members’ names and dates.
lesobrod ·
Now I try to do some terrible things using SM as MIDI source (pseudo-random music etc.).. 😈 So many events comes to poor "Midi Event" primitive and, when using as VST on DAW, sometimes Midi Panic happen - one note over-looping, DAW hunging etc. Is it possible to do a kind of "Restrict Poly" inside SM project? I mean: to cut off all overlaping notes, except "N", where N should be changeable, from 1 to 4-5.
trogluddite ·
I have been making some MIDI looping plugins, and there is one thing I found that may be related to your problem...
Some VSTi's don't handle multiple instances of the same note being played, e.g if you send; note-on C3, note-on C3, note-off C3, note-off C3 (all on same MIDI channel) With some synths, this confuses the voice manager because it can't tell which note-on matches up with which note off, and you get either hanging notes, or notes cut short. Always best to turn off the first instance before playing the same note again.
It's also worth being very careful how you have MIDI generators rigged up - it's very easy to get the trigger order for the data wrong, so that sometimes you are not sending valid messages. Make sure that the trigger input of the MIDI Event will be triggered after all the data inputs have the right values. Also, it can be better to use several MIDI Event primitives and then merge their MIDI outputs, rather than trying to 'multiplex' lots of green data into a single MIDI Event primitive.
If those tips don't help, then you will need to build some form of voice management into the plugin - to handle polyphony and multiple instances of the same note (maybe send them to different channels?). I had some success with this kind of thing making a green voice manager, so that I could have different behaviour to the normal MIDItoPoly - so in principle it can be done.
Would be useful to see a schematic - can then get a better idea of what kind of buffering etc. you might need.
lesobrod ·
trogluddite wrote: Make sure that the trigger input of the MIDI Event will be triggered after all the data inputs have the right values.
Well, the main problem was with this. Thanx for always factful posts!
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker