Hi lad-folk,
The latest rev of the MWPP spec is out:
http://www.ietf.org/internet-drafts/draft-ietf-avt-mwpp-midi-rtp-01.txt
A quick synopsis of the changes:
o The MIDI command section now encodes all legal MIDI
commands, including all MIDI Systems commands.
o The MIDI command section header has new features to
support the efficient streaming of pre-generated MIDI
performances.
o A new SDP parameter (pwe) indicates that a stream
is suitable for use in pseudo-wire emulation.
o Changes in response to Dominique Fober's AVT postings.
Basically, at this point, for applications where the recovery
journal isn't needed (TCP transport) MWPP is done --
if you see any MIDI functionality which is unencodable in
the MIDI Command Section of MWPP, its a bug we need to fix.
Major remaining work items include:
o A redesign of Chapter C of the recovery journal, to
handle the semantics of all 128 controllers of the
MIDI Control Change command. Will probably include
the creation of a new recovery journal chapter for
Registered/Non-Registered Parameter Numbers, since
the Chapter C format is unsuitable for resiliency
for this feature.
o Resiliency guidelines for MIDI Systems. A significant
subset is amenable to recovery journal techniques,
the rest requires the hooks for an "other means"
resiliency, which for unicast could be as simple as
a separate TCP MWPP link dedicated to the bulk transport
aspects of MIDI Systems which are unsuitable for UDP
streaming.
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------
