<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 01/03/2016 05:30 PM, Len Ovens
wrote:<br>
</div>
<blockquote
cite="mid:alpine.DEB.2.10.1601031504010.2588@scott.cbbs.org"
type="cite">On Sat, 2 Jan 2016, Jonathan E. Brickman wrote:
<br>
<br>
<blockquote type="cite">For midi over a network have a look at
<br>
<br>
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/RTP_MIDI">https://en.wikipedia.org/wiki/RTP_MIDI</a>
<br>
<a class="moz-txt-link-freetext" href="https://code.google.com/p/midikit/">https://code.google.com/p/midikit/</a>
<br>
</blockquote>
<br>
RTP_midi is supposed to be standard and does (if fully
implemented) have error checking. The other standard is ipmidi
(see qmidinet) ipMIDI does not make sure of 100%... it would have
to be tunneled through tcp to get that. UDP tunneled through tcp
on a local LAN may be acceptable timing wise for your purposes, I
don't know.
<br>
<br>
MIDI, unlike audio, must have 100% reliablility to be useful. That
reliablilty is first that all events must reach the other side and
second timing needs to be preserved. A small miss in timing while
anoying, is tolerable. A missing byte is not. One missing byte =
either a missing event or a malformed event that can change the
meaning of that event. (even from a note off to a note on)
<br>
<br>
Both RTP_midi and ipmidi sit on top of other IP protocols and are
therefore wifi compatible.
<br>
<br>
I am guessing ssh or telnet over wifi (if set to binary) may work
just as well too. I don't know if you need ssh or not. If you are
willing to do a bit of programming, making a jack client connected
to a tcp server/client should be easy enough though. I have not
played with netjack and do not know how reliable that is for MIDI.
I have not had trouble with Xruns though which would be the same
thing.
<br>
</blockquote>
Len, thanks for the rundown. I put a lot of effort into
ipmidi/qmidinet, and there was definite occasional loss which I
could not eliminate. Also tried both varieties of netjack; similar
result. I did not find any usable error correction therein. (Error
detection is irrelevant for this; error correction is priceless!)
Latencies were very nicely low, but indeed for instrument control
any MIDI loss, even one byte per minute, is unacceptable.<br>
<br>
I am not certain that MIDI must have 100% reliability to be useful
in something like a tablet controller, as long as status feedback
exists so the operator knows that a signal has failed. But MIDI
does have to have 100% reliability to be useful to drive a synth
from a keyboard. And I will think that for very high fidelity
situations, audio transmission does have to either have 100%
reliability -- with retransmission or a good enough setup that there
simply is no audible loss -- or has to have seriously good
interpolative resampling capability to hide the losses. <br>
<br>
According to at least one reference I found, the Ubuntu inclusions
"scenic" and "midistream" are said to be RTP-MIDI complete with
journaling, and it does sound to me like this is likely to be the
best-of-breed for remote instrument control over IP right now. I'll
be trying these next unless another option arises.<br>
<br>
J.E.B.<br>
<br>
<div class="moz-signature">-- <br>
<div style="color: #993300; font-size: 0.8em; font-style: italic;">
Jonathan E. Brickman <a class="moz-txt-link-abbreviated" href="mailto:jeb@ponderworthy.com">jeb@ponderworthy.com</a> (785)233-9977<br>
Hear us at <a href="http://ponderworthy.com">http://ponderworthy.com</a>
-- CDs and MP3 <a
href="http://ponderworthy.com/ad-astra/ad-astra.html">now
available!</a><br>
Music of compassion; fire, and life!!!
</div>
</div>
</body>
</html>