sysex and lemur, is there a known problem?

[dbk]

Hello,

receiving sysex over Wifi (ad hoc or router) seems to be kind of buggy. The sysex data from my machinedrum geht scrambled on like 6 out 10 tries, if it doesn´t work i get an empty arrray.

it mostly works with an interface attached to the ipad but i still wonder if there´s something fishy with sending sysex over wifi and if Liine i aware of this?

besides, i heared the lemur cuts Sysex above 128 bytes, is this true?

this would at least make clear why i have troubles, a kit dump from the machinedrum has round 400 bytes.

looking forward to a reply from lline or any other one who has insights on this tpic.


cheers,
martin

[whatisvalis]

Are you on windows? If so what virtual midi driver are you using? I only ask because I thought Loopbe supported sysex, but I noticed the Mackie control doesn't send track names to the surfacelcd.

[dbk]

nope. sorry, i´m on a mac.

[Macciza]

Hi
Found this on the web for a current version of some other iOS software - may be relevant here - could not find more details with a quick search . . .

System exclusive messages larger than 1010 bytes can't be sent over the CoreMIDI network interface. This seems to be a problem with the iOS driver from Apple. Note, this does not affect external interfaces.
System exclusive messages larger than 255 bytes can't be received via the CoreMIDI network interface. This seems to be a problem with the iOS driver from Apple. Note, this does not affect external interfaces.

I have have had some issues with sysex as well that I am not sure about . . .
Cheer
MM

[dbk]

thanks for the info.

this is really odd, a sysex dump from the MD gives always strange values to my monitor.
sometimes the array is filed with 4 values, then it´s 16 and then again it´s 20 and everything in between.

i really whish this would be more easy to handle, becuase right now i don´t know what´s the problem, the iOS, the lemur´s sysex handling or my code or all of it

cheers