On 7/23/06, lazzaro <[EMAIL PROTECTED]> wrote:
> Dave Robillard <[EMAIL PROTECTED]> wrote: > > OSC can go over TCP to avoid the packet loss issue (and messed up > ordering which can be extremely annoying as well). liblo's TCP > support > needs some work though. This comment illustrates an advantage for using RTP MIDI to send MIDI over lossy networks. The recovery journal in RTP MIDI supports graceful recovery from the loss of an arbitrary number of packets upon the receipt of the first packet after the loss (also works for reordering). Journalling is a feed-forward process, no retransmission is used -- thus, no head-of-line-blocking latency issues as one has when running media over TCP. See: http://www.cs.berkeley.edu/~lazzaro/rtpmidi/index.html The IESG approved RTP MIDI in February, so the protocol is frozen. Hopefully the copy-edit phase will be done by autumn and then we'll have RFC numbers for RTP MIDI. --- John Lazzaro http://www.cs.berkeley.edu/~lazzaro lazzaro [at] cs [dot] berkeley [dot] edu ---
Yay! i want my whole app to communicate between engine and gui via midi! That's going to really be interesting... So what CC would i use for add a new node named "node"? Sysex i guess? .... Loki
