Been putting recently purchased mioXL through it's paces, and mostly everything is good, however there are a couple of niggles on the rtpMIDI side:-
1) Setting rtpMIDI to be "Initiator" does not seem to be working for me (Windows 10) - the mio connection shows as participant on the DAW/Windows side (rtpMidi app), but the connection never updates in the mioXL (IPAddress / Port). So even though it looks like a connection has been made in Windows, it is not working and no MIDI is sent.
2) Even sessions with the mioXL set up as Responder have a few issues - e.g. my FaderFox PC4 editor cannot "Send to PC4" using it's editor over rtpMIDI - it gets a checksum error (strangely the editor can receive from the PC4 ok over rtpMIDI). When I connect using USB DAW and use the FaderFox editor directly (HST1) i can send / receive perfectly.
Connecting via ethernet was one of the big draws of the mioXL, reduced cabling and USB ports on DAW, but obviously it needs to work! I know from other MIDI dev work i've done that some devices don't like MIDI data to be transmitted too fats (BOMEs send SX has a throttling ability), i'm wondering if rtpMIDI is possibly too fast?
Any insight / ideas would be appreciated! I will keep reading up / digging more into rtpMIDI and see if there is anything that can be tweaked.