[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-audio-dev
Subject: Re: [LAD] =?utf-8?q?MIDI-2-TCP=2C_TCP-2-MIDI?=
From: christoph.kuhr () web ! de
Date: 2018-08-30 5:11:30
Message-ID: 1535605889.340923915 () f2 ! my ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
Hey Len,
thanks for the insight.
I never used OSC this way so far.
I also did not know that there are existing RFCs for MIDI over RTP, which is very nice!
So, yeah, lets do that.
I will take a closer look at the code repos you posted. I definitly want to give this a try!
But I am rather busy at the moment, so don't expect too fast progress in this matter ;-)
BR,
Ck Mittwoch, 29 August 2018, 09:00nachm. +01:00 von Len Ovens len@ovenwerks.net :
>On Wed, 29 Aug 2018, christoph.kuhr@web.de wrote:
>
> I would always prefer a UDP based solutions, because TCP can really mess up the
> timing. UDP packetloss usually is below 1%. The bigger problem in this case are
> WIFI connections, scrambled packet orders and jitter.
>
> Are there any objections to using Open Sound Control based solutions?
> To me it makes more sence, because it is an IP-based protocol (32 bit) in
> contrast to MIDI, which is designed for 8 bit serial interfaces.
>
>OSC being lossless has not been my experience. The problem I have had is
>the OSC messages are generally one message per packet which means that a
>large group of messages can overwhelm udp quite easily. OSC does allow for
>using bundles of messages to be performed at the same time, however MIDI
>to OSC cannot really determine a group of events that happen at the same
>time because of it's (slow) serial nature.
>
>Do note that the osc message "stormes" I have had trouble with are bigger
>than what MIDI was designed to handle in realtime (10 events from 10
>fingers). I am talking about refreshing a control surface with at least 8
>strips with each strip having 20 or so events. So well over 100 events.
>When I tried to use bundles, I found that no control surfaces created or
>understood bundled messages. I ended up adding a small delay in the sends
>to fix this... not very "real time" :) Not noticable while moving one
>control like a fader but noticable if performing music.
>
>
>--
>Len Ovens
>www.ovenwerks.net
>_______________________________________________
>Linux-audio-dev mailing list
>Linux-audio-dev@lists.linuxaudio.org
>https://lists.linuxaudio.org/listinfo/linux-audio-dev
[Attachment #5 (text/html)]
<HTML><BODY><p style='margin-top: 0px;' dir="ltr">Hey Len,</p>
<p dir="ltr">thanks for the insight.<br>
I never used OSC this way so far.</p>
<p dir="ltr">I also did not know that there are existing RFCs for MIDI over RTP, which is very nice!</p>
<p dir="ltr">So, yeah, lets do that.<br>
I will take a closer look at the code repos you posted. I definitly want to give this a try!<br>
But I am rather busy at the moment, so don't expect too fast progress in this matter ;-)</p>
<p dir="ltr">BR,<br>
Ck</p>
Mittwoch, 29 August 2018, 09:00nachm. +01:00 von Len Ovens <a \
href="mailto:len@ovenwerks.net">len@ovenwerks.net</a>:<br><br><blockquote id="mail-app-auto-quote" \
cite="15355728320000011926" style="border-left:1px solid #FC2C38; margin:0px 0px 0px 10px; padding:0px \
0px 0px 10px;">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div >
<base target="_self" href="https://e-aj.my.com/" />
<div id="style_15355728320000011926_BODY">On Wed, 29 Aug 2018, <a \
href="mailto:christoph.kuhr@web.de">christoph.kuhr@web.de</a> wrote:<br> <br>
> I would always prefer a UDP based solutions, because TCP can really mess up the<br>
> timing. UDP packetloss usually is below 1%. The bigger problem in this case are<br>
> WIFI connections, scrambled packet orders and jitter.<br>
> <br>
> Are there any objections to using Open Sound Control based solutions?<br>
> To me it makes more sence, because it is an IP-based protocol (32 bit) in<br>
> contrast to MIDI, which is designed for 8 bit serial interfaces.<br>
<br>
OSC being lossless has not been my experience. The problem I have had is <br>
the OSC messages are generally one message per packet which means that a <br>
large group of messages can overwhelm udp quite easily. OSC does allow for <br>
using bundles of messages to be performed at the same time, however MIDI <br>
to OSC cannot really determine a group of events that happen at the same <br>
time because of it's (slow) serial nature.<br>
<br>
Do note that the osc message "stormes" I have had trouble with are bigger <br>
than what MIDI was designed to handle in realtime (10 events from 10 <br>
fingers). I am talking about refreshing a control surface with at least 8 <br>
strips with each strip having 20 or so events. So well over 100 events. <br>
When I tried to use bundles, I found that no control surfaces created or <br>
understood bundled messages. I ended up adding a small delay in the sends <br>
to fix this... not very "real time" :) Not noticable while moving one <br>
control like a fader but noticable if performing music.<br>
<br>
<br>
--<br>
Len Ovens<br>
<a href="http://www.ovenwerks.net" target="_blank" >www.ovenwerks.net</a><br>
</div>
<div>_______________________________________________<br>
Linux-audio-dev mailing list<br>
<a href="mailto:Linux-audio-dev@lists.linuxaudio.org">Linux-audio-dev@lists.linuxaudio.org</a><br>
<a href="https://lists.linuxaudio.org/listinfo/linux-audio-dev" target="_blank" \
>https://lists.linuxaudio.org/listinfo/linux-audio-dev</a><br> </div>
<base target="_self" href="https://e-aj.my.com/" />
</div>
</div>
</blockquote></BODY></HTML>
[Attachment #6 (text/plain)]
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic