beats me wrote:I'll stop posting my user problem diatribes in here and start going direct for support or to their forum. I think my rants were mostly in spiteful response to the "It connected and worked perfect in 5 minutes" bastards.
In all fairness in comparing this to LiveControl, LiveControl has been around a lot longer than this and has gone through a long history of similar connection problems. I pretty much gave up and I'm sure it's probably a lot more stable now, months later, but they too had to go through this painful period.
More of a general question about adhoc networks here. When I went to connect back to my wireless router I thought it fucked everything up because it wouldn't connect or get a signal but it had to do with the adhoc network using a set static address and when using the router it needs to let the hamster in my laptop detect and set the address. As a Mac user this is way more than I ever wanted to know or do. Is there any way to setup an adhoc network that will just let me flip between that and the router by selecting either and not having to manually do anything in top of that?
Part 2: Is this "just use an adhoc network" going to be the status quo or can anything be done on the programming end so that going through a router will be just as reliable?
beats, beats, beats.
It pains me to see you having so much trouble.
One thing that I've found works well is to NOT have Live running when you begin the start sequence steps. Their website is confusing. It says to start Live on the 3rd of 4th set of instructions, then do some other stuff, then it says to start Live (again? after I shut it down from the first start up? after the zombie apocalypse? wtf) Ugg.
Starting Live should be done AFTER you set your MIDI prefs on the iPad touchAble app and BEFORE you start touchAble on the iPad.
While I could get everything going with Live open
after I created my ad hoc network, it was the exception rather than the rule.