sysex_f0 v. sysex_f7 ?

[Peter Billam]

The normal sysex is a sysex_f0 event, which starts with F0 and
ends with F7.

Could someone re-explain to me the role of the sysex_f7 event,
which starts with F7 ? I think I remember it had something to
so with continuing very long sysex-data over several messages,
but I can't see how it would work, and there's no mention of it
that I can see in either:
http://www.blitter.com/~russtopia/MIDI/~jglatt/
or
http://www.midi.org/techspecs/midimessages.php

Thanks, Regards, Peter

[Peter Billam]

Post by Peter Billam
The normal sysex is a sysex_f0 event, which starts with F0 and
ends with F7.
Could someone re-explain to me the role of the sysex_f7 event,
which starts with F7 ? I think I remember it had something to
so with continuing very long sysex-data over several messages,

Sorry, it's me again; I found the original thread, which was
voluminous, and was back in early March 2011. The consequence
for me now is that people using MIDI.lua or MIDI.py
http://www.pjb.com.au/comp/lua/MIDI.html
http://www.pjb.com.au/midi/MIDI.html
who use {'sysex_f0', dtime, raw} do need to put an explicit F7
at the end of their raw data, but not an F0 at the start because
that gets added automatically (eg by score2midi or opus2midi).
This needs to be documented better :-( ...

It's the same with the original CPAN module
http://search.cpan.org/perldoc?MIDI
...

Regards, Peter