+1
From what I've researched thus far, OSC as a protocol is not inherently wireless, it just uses an address path format that is comparable to HTML. My understanding of the current state of the spec is that most of the time, a wired (or at least a closed-system, software-to-software within one computer) implementation of it still requires wrapping TCP/IP like string packets around an existing control signal (Serial, MIDI, what have you) - but I am not technical enough to comment on this, I just have knowledge of other wired OSC projects - Arduinome/Chronome (which requires Nomestate to translate Arduino serial into OSC) and OSCuino (which still doesn't really work, and uses SLIPSerial as its means of translation/message construction and transmission).
Still, some sort of precedent has already been set. I found this thread because I'm doing some testing work in-office and the company wireless is choking, so my interface controls are jumping around - ugh. It should not be that I can be plugged into an Alesis iO Dock and send USB MIDI just fine, but that I cannot do something similar with OSC - maybe not through the iO Dock, since it's that thing's job to mount to an iPad dock to translate relevant in-app MIDI messages to class-compliant MIDI messages over USB, so it would be on Alesis to make it send ANY kind of message over USB - but in principle the same level of connectivity should be allowable for either kind of message you'd like to send out of Lemur.
Being able to use ports other than 8000 only for sending would be cool too
