I have exactly the same problem since the Mira update.
Until now I was able to connect the iPad through both my home internet wifi or a local network started from my laptop. Everything was fine, except the slowness with my internet connection of course. None of these solutions is working anymore...
I'm using Max 6.1.4 on OS 10.7.5 (MacBook Pro).
The error doesn't affect Max itself (like it was mentioned on another topic), it only forbids me to connect from the iPad.
Cool. I have some sense of what's going on here--it looks like the iPad 2 and the desktop Mira are opening up connections on the wrong interfaces. This might be an easy fix, but it will have to wait for testing. I'll let you know as soon as I have some more insight. Thanks again for your patience, and for sending me such thorough debugging info to work with.
Okay, one more thing to try. Is everyone using the latest Mira package? You actually have to download the package again and update the mira.frame object from 1.0.7 to 1.1.4. Apologies if this wasn't clear. Hopefully this fixes the problem!
Same for me. Just in case I re-installed it like 2 times, first erasing the previous one, then copying again...
The help file of mira.frame mentions the umenu, so it should be the good one.
I'll try it again tonight, I don't have my iPad with me right now.
Thanks Wells. Which Network Preferences do you mean? Mac or iPad?
Edit : So I tried to change the Prefs on the Mac, created a new config, even reinstalled Mira on the iPad, nothing changed.
Maybe a clue : when I did my new network config, I created a local network with another name, just for trying (let's say AdHawk instead of Jv-Macbook).
Strangely, when I tried to connect from Mira, the name displayed for the local network was the previous one, Jv-Macbook. I mean in Mira, not in iPad settings, where AdHawk is shown properly. Is this normal?
FWIW, MBP 2x2,4 10.8.4 iOS 5 max 6.14 mira package 1.1.4 and latest iApp, no crash, but live.grid is unresponsive (may have read somewhere that I should upgrade to iOS 7 for it to work, but then Mira would crash... My choice is made for now...).
I tried Max 6.1.4 with the new package and the Mira update on 10.8.5 with iOS6 on an iPad 3. It worked as it used to (a bit clunky) and the umenu showed on the iPad, but would not populate or let me change its drop-down.
Reading this, it looked like Sam was very keen on iOS7, so I updated to that having resisted for ages. Now Mira will not launch at all. I am not getting an error number, just 'submit report', and iOS7 is looking pretty ugly to me...
Something new. I changed location with not the same provider and less people connected around me. Now Mira look fine. I connect it at the same ad-Hoc network as before. All is the same execpt location.
Have not been able to connect with my MIRA app since purchase. I tried adhoc network from OSX 10.7.5 and 10.9 on two different machines. I am running Max 6.1.5 and Mira tools 1.1.4. Is there something basic that I am missing? Getting this error every time:
POSIX error 70007
Any guidance would be helpful - the application is completely useless to me currently.
Unfortunately, I am still getting the same error (as seen in the attached image). Mira 1.1.6, Max 6.1.5, iOS 7 (on an iPad 2), OSX 10.7.5. The machines see each other, but just will not connect. I have restarted each machine, reset network settings and reinstalled both the app and the corresponding max software. I have tried both a non-firewalled local network and an Ad-Hoc network.
Are there any tricks to try to get this to work? Is it solely an iPad 2 problem? Any help would be appreciated.
Has anyone made changes to either their primary machines or on the iPad that have been helpful in a similar situation?
@dolce Great to hear.
@jmcjedi Huh. I'm really sorry you're still having trouble. Of the top of my head, all I can think of is that the network error you're experiencing is exactly what I get when my MacBook firewall blocks the Mira connection. Are you sure that you don't have some kind of network configuration blocking incoming connections?
That was what I was thinking, but I tried a separate machine and got the same thing. I will do some more exploration. I was able to get Mira to work well with my Windows machine, so a solution has been found that will tide me over. I will check back in with an update after further exploration.
What would be a super useful thing for us would be to collect lists of running processes from people who are experiencing the error. You can get this from Activity Monitor. I've like to compare these running process lists ad see if we can't find something in common with them all.
If you are stuck with the 70007 error please feel free to get in touch with support, and we can try and get to the bottom of it.
Apologies if this has been solved for most folks, but I've just downloaded Mira today and am having problems. Basically it worked once, but hasn't worked properly since my first attempt. Here goes:
Mira App v1.1.6
Max package v1.1.6
1. Connected once on my home wi-fi network, all fine and dandy, lovely.
2. 'closed' Mira by pressing home button, back to home screen on iPad, patch still open in Max.
3. Reentered Mira, patch no longer displayed, but now showing Mira connection page (i.e. the one with 'Current WiFi' and 'Ad Hoc setup'). Since then, it doesn't work: reopening the patch in Max, creating new mira.frame, or anything, does not reconnect Mira.
4. I tried: quit Mira completely; uninstalled/reinstalled App; uninstalled/reinstalled Max package; restarted iPad and computer.
5. Created a new ad hoc network. App appears to reconnect with the mac: under 'Max Servers' the app reports the name of the mac, but after a few seconds gives a yellow warning triangle and a 'Disconnect' button. If I press Disconnect, it becomes a 'Connect' button, and if I then press that, the App finally connects and THEN I can see my patch in the App and it seems to work ok. Now, I can 'quit' the app, reenter it, and it still works so long as I have my ad hoc network running. If I swipe-close the App, restarting it now gives 'Mira unexpectedly quit, would you like to send an anonymous report' etc. But I can then press the 'Connect' button and it reconnects to my ad hoc network and it works ok.
6. But it no longer will connect over my home wi-fi network at all, even though it did one time. Wi-fi network otherwise fine.
Anyone shed any light here? Sorry if I missed something obvious.
I've having approximately the same problem than Incky :
• When using a non ad-hoc network (i.e. a network created on my Mac Mini for sharing an ethernet-fed internet connection):
- It works the first time I open Mira on my iPad: automagically connects and all...
- if I ever close the app or move to another app, then I have the Current Wifi / Max servers window, and no visible server - sometimes that also happens when putting the iPad in sleep mode, and reopening it (directly on Mira)
- sometimes also, without going away, the Mira interface just unexpectly disappears, and I'm back to the good ol' desperately empty Max servers window
- from then on, the only way to get Mira back to work (it must be French: always on strike !) is to restart the iPad
• I have tried to create an ad-hoc network, but then:
- either I get a POSIX error (I have forgotten the number, maybe 5000-ish) when trying to connect
- either it works for some time, and does soemthing very near to the previous situation
Mira 1.1.6 package and app
Mac Mini i7 2.3GHz
Ok having been away for the weekend I decided to try again!
This is weird:
On opening the Mira app over my home wi-fi network again, the app connects to the wi-fi network fine and it shows my iMac as a server.
In Max, as soon as I create a mira.frame object, the app gives me a popup:
"could not connect to server: [my servername]
Error 70007, the operation couldn't be completed. (POSIX error 70007 - unknown error: 70007)"
This popup I can simply 'okay' and it goes away, and then my iMac is listed under Max Servers in the app, with a Connect button. I hit Connect, and after that everything seems ok - I can destroy mira.frames and create them at will, and the app behaves fine.
I can also quit the app, and quit Max, independently, and restart both and they seem to be ok - except that the app says it quit unexpectedly, and do I want to send an error report. But it actually behaves ok now.
So somehow it seems to be working at the moment, despite the POSIX error.
But it would be nice to know it will be a bit more robust on other networks (I have to try it next week on another network and am hoping to use this for a performance next year…)
I posted it elsewhere but it seems to belong on this thread....
I have been using Mira for about a week now with great results but ran into something this morning. I was using it on my in-house wireless network via an Apple Airport that leads out to the internet. I will eventually be performing in a space where I don’t want to use their public WiFi. I created a network on my laptop. My iPad sees it when I identify it in Systems Preferences and connects but Mira doesn’t see it. First questio is, can it be done this way? Second, what might I be missing? Third, is there a tutorial document about this?
iPad Air, ios 7.
Reading INCKY above I pressed OK and was able to connect from IPad to my computer-to-computer network.
Another wonderment...if Mira sees two computers each running max with mira frames it brings both up on the iPad. Not sure how i could use that but perhaps switch frames in some context would be useful.
I encoutered the same 70007 error today while building a new Windows 8 system. This system is WIRED to the network. No wifi for now.
The problem vanished when I gave sufficient access permissions in the firewall to MAX and Bonjour. Sufficient, in this case, means: wide-open for private and public nets :-)
When creating ad-hoc servers, and for some reason, the servers do not connect, they seem to never be forgotten by Max, even after restarting max, mac and ipad.
So when connected to a new wifi server, Max still tries to connect with mira on the old destroyed server.
Mira says it is connected to the good server until max is launched. Then it only sees the wrong one (which should be not here anymore)
I have tried to reinstall max, but no progress
I encountered 70007 error today and I solved after hours of struggling. It has something to do with Mac firewall (pf) configuration. I am using
I have Icefloor to configure pf. Although the firewall was off, it was blocking Mira. So, I started pf firewall with Icefloor, I chose no_filtering_and_no_logging preset. This solved connection error using a router or modem. To solve the same error on ad-hoc, I used following network configurations;
Manually configuring the Ad hoc network connection by manually setting the TCP/IP address, subnet, and router in the Network Preferences for the Wi-Fi settings
192.168.2.0 on my MacBook Air
255.255.0.0 as the subnet
192.168.2.0 as the Router
192.168.2.1 on my iPad
255.255.0.0 as the subnet on iPad
192.168.2.0 as the DNS and Gateway
years later, and weird enough that it appears only now, but sometimes now i have this POSIX error code 70007. It's not always there, i mean it's there if :
* Max is not yet open
* i right click the Max icon in the dock
* the list of recent patchers pops up from there
* i open the Mira containing patch from there.
But if i wait for Max to initialize and then i open my patch, it doesn't do the bug. Ipad is iOS10.3.3 air2, osx 10.10.5.
there is now firewall that i know of here