Page 1 of 1

Serious problems with Lemur+Mu running over Adhoc

Posted: 08 Feb 2013 01:05
by benlikesound
Hey guys,
I'm having a really frustrating problem that sounds similar to a lot of the others discussed here, but not quite the same, and I've been as yet unable to find a solution for it.
As much as I don't like the idea, I'm starting to think I'm going to have to ditch Lemur and go back to an APC.

I'll start at the beginning... I was originally running iOS 5, Live 8.2.6 and OSX 10.6.8, and all was well. I'd just create an adhoc network with DHCP and off I went. Countless gigs went down without a problem.

Then came the iOS 6 update. Bad idea. Eventually figured out that Apple removed support for adhoc networks using DHCP, so, with an hour to spare before a set, I set up a new network location with a manual IP (computer as 192.168.0.1, subnet mask 255.255.255.0), created an adhoc network, connected the iPad, set up with ip 192.168.0.2, same subnet mask, and all was good. Gig went well, no problems.

2 Weeks later I did a clean install on my Macbook Pro. OSX 10.7.5, Live 8.3, iOS 6.0.1 and now nothing works.
Same network setup, and the ipad connects, but the Mu device can't see the ipad. Tried entering the IP manually using port 8000, same issue. Tried setting the network up with the computer as 10.0.1.1 and iPad as 10.0.1.2, same issue. Under both setups, the Lemur Daemon is unable to see the iPad.

The weird thing is that when I enter the IP into the Mu device manually and hit Reload Template, the layout on the Lemur flashes once, very quickly, as if it is receiving a template and is about to populate the grid with clips, but nothing happens after that. Also weird, is that with the same setup, using either IP range, Lemur Editor can communicate with Lemur with no problems. This led me to believe that port 8000 was being blocked, so I turned off my firewall, but no change. I'm not running any other apps on the ipad or the Macbook Pro, and I don't have Little Snitch or any other port blocker installed.

If anybody has any ideas, I could really use some help. I've been working on this for days and I'm out of ideas. I have a gig in a week, so need to have it fixed by then.


EDIT: I just did another quick test. Tried connecting my Macbook pro and iPad to my home wireless router using the router as DHCP server. The ipad has an active internet connection, and so does the computer, so they're both talking to the router, but still, no ipad found in either Lemur Daemon or the Mu device. Fucking annoying.

Re: Serious problems with Lemur+Mu running over Adhoc

Posted: 06 Mar 2013 22:57
by azfx
Check if Max application is running on your mac. I had the same issue, and shutting down the application seem to have solved the issue.

Re: Serious problems with Lemur+Mu running over Adhoc

Posted: 07 Mar 2013 22:49
by Joe Soap
Yeah, this is about udpsend and udpreceive binding to ports and the way M4L and Live handle the transition from running under Live as a device versus being edited under Max as a maxpatch.

If you search the forum (this section) I recently posted a link to a C74 forum discussing this, wherein lies a patch to work around the issue via some gating logic and loadbangs or whatnot.