iOS Lemur MIDI Weirdness...

[vfxjokir]

Hello all.

I've installed the iOS Lemur app on both my iPhone and iPad - both devices are running the latest iOS version. Both devices are connected to the same WiFi network, and my MacPro is "hardwired" to an Ethernet router.

All three devices share IP "space" - the iPad is 192.168.1.5, the iPhone is 192.168.1.4 and the Mac Pro is 192.168.1.2. No firewalls are running internally.

On my MacPro, in the Audio/Midi Utility, I create a Session in the MIDI Network Device's pane. When Lemur is running on both my iPhone and iPad, those two devices appear in the list of external sessions to connect to. When I select the iPhone in the list, and choose "Connect", it connects nearly instantly, and appears in the right side of the pane as a Participant.

When I try to do the exact same thing with the iPad- there is a pause, and a window pops up- "192.168.1.5:5004 refused the connection request."

Connections between the iPhone Lemur instance and MIDI apps on my Mac Pro work perfectly- Lemur running on the iPhone controls things perfectly. I just can't get a similarly configured iPad to work at all!!??

Screenshots below...
Any ideas?

thanks in advance!
j.

Screen Shot 2011-12-08 at 9.13.35 AM.png (13.62 KiB) Viewed 2121 times

Screen Shot 2011-12-08 at 9.13.20 AM.png (45.15 KiB) Viewed 2121 times

[nick_liine]

Hi Josh,

Thanks for posting. The explanation is quite simple. We use CoreMIDI only for the USB MIDI connection (either through the Camera Connection Kit or with a native interface like iConnect MIDI). To send MIDI messages over Wi-Fi use the Lemur Daemon.

Check out this simple tutorial video:
http://www.youtube.com/watch?v=g69iVWxJZuQ

Thanks,
Nick

[pdelges]

That's strange because using a "MIDI network session" on my Mac (OSX.6.8) does work with Lemur on my iPad (latest iOS).

Maybe you had a port conflict?

This CoreMIDI over WiFi feature is undocumented, but I wonder why the Lemur Deamon should still be used...

[axel_liine]

This CoreMIDI over WiFi feature is undocumented, but I wonder why the Lemur Deamon should still be used...

Quite simply, the Lemur Daemon offers us more flexibility than networked CoreMIDI in terms of number separate connections. You can only have on MIDI session for a given app on the iPad, but we need more than that so each MIDI target can be routed to a different destination, possibly on separate machines.