4 Jan
2016
4 Jan
'16
10:16 a.m.
On Sun, 3 Jan 2016 18:04:25 -0800 (PST), Len Ovens wrote:
Even for a controller, it is quite important, maybe
required. The only
place midi can be less than 100% is a string of changing values for
one controller where the next value is known to be coming or this is
the last event in a string and the change in value is very small.
I suspect that even this could lead to wrong results, if the byte/bites
that follows the missing byte/bites should make sense for the string.
Theoretical MIDI doesn't need to be 100% reliable for sysex data that
requires a checksum, but not all sysex data requires a checksum and
sometimes even a checksum doesn't correctly verify the data. I noticed
it, when I wrote an editor to manage DX7 sound banks in the 80s or 90s,
that even checksums sometimes could be "flexible".
In a performance situation, audio and high fidelity are
not so
important. QOS still must be very high, but a missing sample is not
like a missing note off (or missing mute on a controller) where the
effect can last till manually corrected, possibly needing a panic
reset.
For live usage active sensing and a panic button are very important ;),
especially if MIDI is used by a sequencer but one MIDI IO only. If
possible each MIDI channel should have it's individual IO ;). I'm not
talking about a thru box, I mean real IOs.