Re: [LAU] MIDI over wifi on Linux, revisited

On Mon, 4 Jan 2016, Christopher Arndt wrote: I think (from what I have read of the OP setup) that this case has two things that call for reliablility. 1) The MIDI stream is heavy. It includes the whole backing orchestration. The use of a panic button would be very noticable. (maybe more so than the hung note it was correcting) 2) The person controlling the playback is playing a sax over top of it and therefore needs his hands to play that. That is he has no way of monitoring and manually correcting things. I can not see how adding OSC as yet another layer with no error checking or correction could be any better than ipmidi. rtpmidi with journaling looks to be the best bet on this because there is no resend needed. The journaling info is sent if needed or not so there is much less latency required for error correction. Journaling does not cover all possibilities BTW, but it is very picky about note off events. In the case of controllers the last value is journaled rather than the whole string of values. I think any of these protocols are event based so that the likelyhood of partial events showing up is minimized. I am not sure how sysex events longer than packet size are handled, but it would be simple enough to add sequence numbering and not start forwarding a sysex till the whole thing reaches the receiving end. So really it is only performance data where one event completes another that is at issue. -- Len Ovens www.ovenwerks.net