To much OSC data over wifi to the Lemur causes omissions(?)

Hmm, didn't like Lemur files, lets try a zip...

Useful Lemur setup! thanks!
jd

This conversation reminds me of MobMuPlat LANdini.

http://music.columbia.edu/~daniglesia/mobmuplat/doc/index.htm

""LANdini" : A custom networking protocol for many-to-many communication, with guaranteed delivery and ordering. See the "LANdini" example for more info on LANdini. All devices must be LANdini enabled to be aware of other devices and receive messages from them. Each client pings out its name and other information, and every client keeps a record of the other clients' states.

All messages are prefixed by 1) sending protocol ("/send", "/sendGD", or "/sendOGD"), 2) a destination ("all", "allButMe", or a user's name), 3) the rest of the user message. The messages then show up at the destination (without the first two elements).

Example PureData messages:
Send a guaranteed-to-be-delivered message to all clients except the sender:
[list /sendGD allButMe /myParameter myValue ("

Also, to anyone doing this wirelessly, one may ask, is your network SSID name being broadcast? If so then people's devices may be trying to connect to it. Perhaps if people, so to speak, are trying to connect their phones to your wireless router during your performance then perhaps that could detract from it's performance? In that case, it would be the router and it's settings which would be at fault.

p.s. see also "Ping & Connect" in the MobMuPlat OSC bullet point above LANdini on the same page.

I have switched to using midi Sysex and, while it isn't just a straight forward to program as OSC, I figured out how to make everything work as I want it to and so far, have not witnessed any data loss at all. Let's see, what happens, when the template gets larger ... Although I think it won't matter much, as I have seen data loss with OSC even with small amounts being sent and haven't observed any of that with midi ...

You have me wondering how feasible it would be to implement a simple ACK system so that when Max sends an OSC packet to Lemur, it must receive an ACK within a short time otherwise it will just send it again (TCP for dummies!)

That sounds like a great idea, but for now, I will keep midi! Maybe another time, when I will start over from scratch. ;-)
Seriously: For my purposes, Sysex is ok. It is a bit more complicated to set up right to label textfields etc, it is also limited in size per junk, but apart from that, it does everything I want for now.

If you have an example of the Lemur side of things to handle sysex data, I'd love to see it. I've never been quite able to figure out how to make scripts work in Lemur, documentation is unclear and the lemur editor is not conducive to helping one figure things out.

Yes, the lemur forum is nowhere as helpful as this one, nor is the documentation ...
But with a lot of cursing, you can figure it all out! ;-)
When you send Sysex to Lemur, in max you have too send your text (message or textedit or whatever) as a list to an 'attoi' object, which converts it to ASCII, the 'prepend 240' and 'append 247'. That goes directly out to the demon Lemur midi in. That is really all there is to it in Max, as long as you just want to send one sysex bulk to be converted to one label (Text, Monitor or labeling of other objects).
On the lemur, you set up a script, execution on_midi, ‘System Exclusive‘ (the other parameters don't matter for Sysex).

 
setattribute(Text1,'content',{arraytostring(subarray(MIDI_ARGS,0,sizeof(MIDI_ARGS)))});

This means, you set the attribute "content" (meaning the actual text), for the text object "Text1" to a vector (array) of the received midi arguments, which gets converted to a string (from ACII back totext). Actually, in this case you could probably just leave out the subarray, as the whole MIDI_ARGS would do it as well:

 
setattribute(Text1,'content',{arraytostring(MIDI_ARGS)});

But with the 'subarray()' call you can select a certain portion of the text, if you want to split the Sysex data to different operations. With one or two numbers at the start of the Sysex dump (in Max prepend before the 240, which defines Sysex start) you can kind of create an ID, which Sysex should trigger what, which has to be filtered in the Lemur script by one or two 'if' conditions accordingly.
So, e.g., if you would want the sysex from before only executed on this text-object, you would send from max: 240 0 {your text in ASCII} 247. The Lemur script would look like:

 
if(MIDI_ARGS[0]==0)
{
     setattribute(Text1,'content',{arraytostring(subarray(MIDI_ARGS,1,sizeof(MIDI_ARGS)-1))});
}

The first line lets only Sysex starting with zero be executed by this script. Because you don't want the zero be part of the text, you have to define the length of the array excluding the 240 and 247 = 'sizeof(MIDI_ARGS)', start your text with 'MIDI_ARGS[1]' (which is actually the second position of the array). The last argument of the subarray is the length of the subarray, which is that of the whole array minus one, as you start on the second position.
I hope that helps and will get you started!

Thanks for the detailed instructions. As it happens, the only part that I've never quite been able to figure out on Lemur is the "setup" bit

-------------------
On the lemur, you set up a script, execution on_midi, ‘System Exclusive‘