lemur app ios 6

[crabs]

just installed iOS 6 on my iPad 2.
the lemur app still works, but when i switch between apps and come back to lemur it restarts.
can you fix this please!
grt randy

[nick_liine]

Thanks for the report. Looking into this.

EDIT: Confirmed. Fix should be included in next update.

[Phil999]

I cannot connect my iPad to my local network anymore. My local network is not connected to the internet. I read that with iOS 6 every wifi connection must contact the Apple server. Does that mean that offline wifi connections are no more possible?

[ggc]

EDIT: whoops, was using rtp, not loop... loool... nyway, seems fine... weeee=)
(seems i also need to manually set the ports in the daemon now.. but it works=)))
hi=)

yeah, also here..

iphone ios5 = connects fine

ipad ios6 = rtpmidi sees the ipad but i cannot connect the session... (latency ????)

the ipad was fine under ios5...

(windows+ipad)

Does it work for you under windows and ios6?

thx=)

[Phil999]

no. The iPads are visible, and networks are visible, you can even connect, but without any effect. The network symbol on the iPad is off.

Connecting to a router with internet access is no problem. But connecting to an ad-hoc network is not working, even with enabled internet sharing. I hope there will be a solution, but so far I haven't seen one.

[sgnhh]

I'm having the same issue.

Lemur also doesn't send MIDI data on any channel except for Omni/ 0. Tried this with both Magellan and Animoog, neither work with any other channel but 0. Anyone else experience this?

[halfcut]

no. The iPads are visible, and networks are visible, you can even connect, but without any effect. The network symbol on the iPad is off.

Connecting to a router with internet access is no problem. But connecting to an ad-hoc network is not working, even with enabled internet sharing. I hope there will be a solution, but so far I haven't seen one.

Yes having the exact same issue. Have emailed Liine support already - however, i did manage to get it working.

You need to setup the network as you did before, and although the little signal fan is not working, have faith that it is actually connecting, may take several attempts of doing the same thing...

Then, open the lemur app, then normally when you can choose the midi ports from the drop down menu you'll realise the MIDI targets are no longer an option, it'll only say the name of your ipad and session 1 below it.

So, you have to keep the lemur App open and go to Lemur Daemon, You'll then notice that nothing appears automatically like before, so you have to select 'Add' then expand the Daeom Midi In and Out menu's and double click on the midi Input and then your iPad should appear 'eventually' as a recognised destination for port complete with the IP address in brackets, and then you have to expand that. And do the same for both Midi in and Out- then back on the lemur app itself the drop down menu's we're used to will appear again...

This happened to me 5 mins before a DJ set last week and i thought i was screwed, and i repeated the above about 3 or 4 times, then suddenly the iPad appeared but only when adding manually...and as you mentioned, works perfectly on the home wireless network, but this strange occorance is only when creating an ad hoc personal network - but the above steps shold get it working again - for now!

Hope this works!

[Phil999]

Glad you found a workaround. I will try those steps again, maybe it works this time. I just have two questions, to rule out some questions: do you have WEP or WPA as security option in your ad-hoc network? Or do you use a router?

[halfcut]

The Ad-hoc network is literally a 'computer to computer' network created from the drop down options when you click on the signal fan on the mac and go to 'create Network...' - and i never use a security option. so no this one wouldn't go through the router.

It seems if you use the home network through the router e.g., BT lets say, this error doesn't seem to be an issue, it will connect like before.

[Phil999]

It seems if you use the home network through the router e.g., BT lets say, this error doesn't seem to be an issue, it will connect like before.

that's what I think, too. I believe it has to do with the wireless card, ad-hoc type, or something we don't know yet.