[LAD] midi2tcp and tcp2midi, working prototype

[Jonathan E. Brickman]

It is working as here:

https://github.com/ponderworthy/midi2tcp

and quite well.  Haven't come up with a single reason to make it more
complicated, beyond much more careful timeout handling.  It will need
to be able to destroy its own socket and recreate et cetera, to be
durable with marginal wifi.  And performance is not very good, midi2tcp
takes 3-5% of one core and tcp2midi takes 6-8% of another on this i3-
3110 at 2.4GHz.  

Am not sure what best to do about the performance.  Will probably try
converting Python to binary, but have read over and over again that
that doesn't do so very much.

I also had to rename it back to TCP after re-reading the Mido library
docs yet again, it is using rtpmidi backend but it says it's TCP, not
UDP, and it is using a connected socket which means TCP I do
believe.  I had thought RTP-MIDI was UDP?   I wonder if judicious use
of UDP would improve performance by a substantial amount?


-- 
Jonathan E. Brickman   jeb at ponderworthy.com    (785)233-9977
Hear us at ponderworthy.com -- CDs and MP3 available!
Music of compassion; fire, and life!!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.linuxaudio.org/archives/linux-audio-dev/attachments/20180906/e4a9175a/attachment.html>