Page 1 of 1

Another person who cannot connect Lemur Ipad to Mac (AD-HOC)

Posted: 28 Dec 2012 20:15
by djjoshuacarl
greetings.
new user, but still pretty tech saavy.

after a few hours of reading the forum here I see that I am one of those people who cant seem to create an adhoc network, and gain a midi target on the Ipad settings.

Ive gone and watched the videos, and did some reading... ended at the Static IP method of getting the Ipad to actually sync with my mac.
which in fact DOES work, but i am only limited to the sync in the lemur editor application... I cannot get the MIDI TARGETS on the on the Ipad to show any clickable solution
(in turn the Daemon doe NOT see the Ipad)
and obviously i am lost without any midi functionality.

Ive tried this is a few environments with no luck (trying to rule out interference)
(I also tried the manual adding in the Daemon)

I am using the latest and greatest from Liine (I just bought the software on the 26th)
my MPB is running snow leapard (17" i7)
and the Ipad is a mini, which is 6.0.2
Though the wifi it works excellent (obviously its a problem when im in a venue with no wifi)

My work-a-round for the moment (which might be for some expensive)
I turn on the "Personal hotspot" on my Iphone
the sign both the Computer, and the Ipad onto the Iphones network.
and sure enough in the ipad settings I get midi targets... but of course both of these suck the life out of the phone, and the ipad.
but it DOES work.

is there a fix in the works? please advise!!!
thanks

Re: Another person who cannot connect Lemur Ipad to Mac (AD-

Posted: 28 Dec 2012 23:14
by tylerm
This is a widespread problem that does not seem to be getting acknowledged/remedied with any high level or priority by the staff at Liine.

I too am having the same problem, I can only get the Ipad and Lemur editor to be recognized over Ad-hoc (Whether it's using regular settings or Static IP) at a ratio of nearly 1 in 50 tries, and when it does connect, it drops out after about 15 minutes.

Things worked fine on my 2010 Macbook Pro, but as soon as I upgraded to the 2012 MBP retina and purchased a new iPad, that's where the problems began.

I am honestly considering re-purchasing a cheap legacy Lemur off ebay for the time being until this gets ironed out.

Again, these problems have been brought up on the forums for months and it doesn't seem like anyone is interested in fixing it or has a definitive solution... It is such a shame that the worlds FINEST customizable controller is being given such limited support.. :x

Re: Another person who cannot connect Lemur Ipad to Mac (AD-

Posted: 28 Dec 2012 23:57
by djjoshuacarl
this looks like it might def be an Ios6 (even 6.0.2) WIDE SPREAD issue.

https://discussions.apple.com/thread/43 ... 5&tstart=0

this thread ^^ is over 80 pages long.... some are having ad-hoc, some are having 2.4 vs 2.5 hz router issues, its pretty crazy.

one reason why they should WITHOUT QUESTION look into an alternative way to have a wired failsafe option (that doesent require MORE HARDWARE!)
I Have friends who use jailbroken ipads with touch OSC hardwired into their MBP who are laughing right now (lol)

Tylerm, noticed your also in Boston.

Twitter: DJJoshuaCarl

Re: Another person who cannot connect Lemur Ipad to Mac (AD-

Posted: 29 Dec 2012 01:43
by djjoshuacarl
I think i just figured this out.

while on my last leg (one hour til gig time)

there was talk of 255.255.255.0 Vs 255.255.00
and with both those I was able to get airport indications on my ipad.... but never midi.

usually when i looked at ip/gateway settings on my mac, (even on manual) it never said what the gateway actually was when using a private network
this time, it did.
255.0.0.0
(YES, A 3RD OPTION!)

so, with 10.0.1.1 and 255.0.0.0 IT WORKED!
i didnt mess with it for long, maybe 10 minutes... no issues
was this a fluke? only time will tell....

Re: Another person who cannot connect Lemur Ipad to Mac (AD-

Posted: 29 Dec 2012 04:10
by Macciza
Hi All
We are aware of the problems some people are having with various setups and in various situations and are constantly working to improve performance in all areas.
Changes in iOS 6 caused various issues for many users and likewise for developers. Networks are inherently instable and there are often many factors and settings that can complicate the situation.

Those 255.255.255.0 numbers are the 'subnet mask' not a gateway - it serves to delineate networks and wrong settings can cause problems

Heres a few examples from my setup on an iMac; i7 10.6.8 -10.8.2- iPad2 iOS6.0.1 Lemur 4.0.1

Often I run through a router that does my internet connection as well when doing dev and needing to be on the net.
The router is 10.0.1.1 and runs DHCP so both my computer and the iPad get various addresss that change occasionally
Currrently computer is 10.0.1.22 and iPad is 10.0.1.23 with subnet mask 255.255.255.0 - network numbers the same only the end varies

I can then create a standard adhoc network using DHCP and end up with say 169.254.251.181(comp), 169.254.19.87(iPad) so now my subnet is 255.255.0.0
This is because the devices are on the different subnets basically - if I setup static ips the subnet mask would be set similarly depending on addresses chosen.

Due to using computer name in the MIDI Targets set from iPad, and computer network name being the name in both instances, imac.local : Daemon Output 0 etc
Because the targets are the same I can pretty much swap between router and adhoc setup and the daemon setup rediscovers itself.

Sometimes it is a problem for me to work out problems that others are having when I can't reproduce the problem myself, and there are many variables.
Sometimes during beta testing of various versions deleting the preferences files for the daemon or editor has proved to be helpful.
Sometimes for whatever reason the ports have not been closed properly and reconnection has required restarts.
Sometimes an other application has been responsible - Max, OSCulator basically other OSC apps can sometimes cause issues
Sometimes when my local network(router) is running badly and a project is having difficulty loading I will switch to the adhoc and it will fly over.

I'll try to do up another setup document or something with some more tips and troubleshooting advice . . .
It is equally frustrating for me knowing that people are having issues when I have so few

Anyway the New Year will bring early updates and the next development cycle . . .

Happy New Year
MM

Re: Another person who cannot connect Lemur Ipad to Mac (AD-

Posted: 29 Dec 2012 07:31
by djjoshuacarl
Hey !!!!
Thank you very much for the lengthy, in that response. I think I learned more from that Post then I have all year!

I am happy to report, that over a Wi-Fi I have had flawless performance from Lemar, and I look forward to learning more and more of the intricacies of the software. Thanks again!!

Jc

Re: Another person who cannot connect Lemur Ipad to Mac (AD-

Posted: 30 Dec 2012 17:54
by djjoshuacarl
I just wanted to give a brief update, so perhaps the developers might take note on there next update. Last night was the first night that I had to use this method to connect my iPad to my MacBook Pro. It was a four hour gig. (Video DJing , using lemur to control Mix Emergency & a few aspects of SeRato)

The first hour and a half was flawless. Connectivity was instant, latency was zero, I was very happy. But then around the two hour mark the daemon Started to get finicky. Fortunately I figured out the quickfix was to force a shutdown of the Daemon, And then restart it, and then refresh the midi targets on the iPad. Problem is that almost every time it took two or three times for the daemon To launch and stay open. Obviously mid gig I cannot restart my computer. So I was constantly force quitting that, until it would start and run. And then make the adjustments in the iPad settings to see the new midi target.

Over the last two hours I probably had to go through that routine about eight times for no rhyme or reason.
I don't know if it was a brief lapse and connectivity on the private network that makes the daemon Do that, or it's just the program itself being a bit flaky. There are no crash reports or anything, because the program never actually crashed it just would lose its connectivity, and then the Daemon became unresponsive.

Thanks :-)