Mac OS X "Ad Hoc" Networking Errors?

Question

As a precedent for this post, I am using the most recent beta of Mac OS X 10.9 (13A558). It is pretty much done and to be released in Early September. I know that can always be the issue at hand, but just wanted to rule out anything that may be happening that isn't beta-related.

 

I've downloaded the Pro version yesterday, and everything works fine over the regular Wifi Network, except with a lot inconsistent latency issues, controlling Reason 6.5.

As recommended, I've established several "ad hoc" or computer-to-computer networks with different variations on the same theme. (changing settings such as Channel, trying differing IP addressing schemes, Static IPs, DHCP mode ect. all with the same result.

Every time I connect MIDI Designer to my new network, it will seem to sync fine on the iPod Touch and then it disconnects after about 5-10 seconds. I haven't had it connect for any longer than that.

On the Mac, in Audio MIDI Setup, when double clicking the Network Icon to bring up the options, before allowing me to continue my setup, I do get this error message. With 0.0.0.0 for the IP address for some reason:

 

 

Then, I can setup everything as recommended. My iPod Touch shows up in the Directory section like normal. Then I can "supposedly" connect my device - in the Audio MIDI Network dialog window only. I cannot get the device to connect by selecting the network in MIDI Designer. Even when I select the network in MIDI Designer, it doesn't show that it has been connected in Audio MIDI Setup. And with in 5-10 seconds, MIDI Designer "disconnects" from the network. But, I'm not sure if it is really ever actually establishing a connection at all, or just attempting to and timing out.

Below is my Network setup dialog. I clicked connect in this dialog to get my device to show up on the right under Participants, otherwise, it will not. It will NOT show up if I attempt to connect from MIDI Designer. (As shown in the tutorial video).

 

Also on occasion after attempting a setup, when closing the Network dialog in Audio MIDI Settings, I will get this version of the same warning as I showed at the top, but WITH the IP address I put in this time. (the screenshot below was from a different session than the screenshot of the Network dialog above. That's why those two IP's don't match.)

 

I have been at it for a while now and narrowed it down to these issues. Like I said, It does work when wirelessly networked over my normal Wifi connection I use for internet access and local networking. I've turned File Sharing on and off. And no other sharing services are enabled. I can't even get to the point to see if MIDI Monitor will show anything. Which it does when networked over the regular Wifi. I do realize that networking can be a complicated issue, so I've tried everything I could think of and research. 

I would try to use BlueMIDI, but unfortunately my iMac's built-in Bluetooth adapter isn't new enough and unsupported.

I have followed the steps outlined in the tutorial video step by step. And then tried lots of troubleshooting options from there.

I love this app. It's definitely one of my favorite tools to be able to set-up a rig for pretty much anything. I'd just like it to be feasible for use- without much latency. Any changes or suggestions to get it working within an "Ad Hoc" network?

Thanks, Jason.

Computer and iOS device used:

iMac 27-inch, Mid 2011, iPod Touch 5th generation.

Comments

Hi! That's very unfortunate, that it doesn't work straight away! I'm on Windows myself so can't help you with this, but I just wanted to let you know that the main guy behind Midi Designer will be back in a couple of days, he'll most probably be able to give some additional advice. Stay tuned!

---

Thanks for the info. I am using the most recent beta of Mac OS X 10.9 (13A558). It is pretty much done and to be released in Early September. I know that can always be the issue at hand, but just wanted to rule out anything that may be happening that isn't beta-related. 

---

Hi. Thanks Rainer! I'm back (mostly)...

We won't be testing Mavericks until it actually becomes available, however... Let's try some random stuff. Add security to the ad-hoc connection and change the name to something simple. Also get on the Apple Developer Forums and see if there are any problems with Bonjour and Mavericks. This problem sounds limited to Bonjour (the location service) and Mavericks, which doesn't help much but does help us look for the problem better.

Then ping back here and we can continue the conversation.

---

Hey thanks for your reply,

Wanted to let you know first that I have been using MD over the last week though the regular WIFI connection with little to no noticeable latency problems. There is latency, and always will be, but it wasn’t as noticeable as when I first tried it. Perhaps the wireless LAN has less web traffic or devices making requests when I am using it (mostly at night when other people are asleep in the house). There are are other computers, iPhones and a Blu-Ray player on the network. But at night, it’s mostly just me with my Mac & iPod.

Well, I tried your suggestion immediately after reading it. And it worked, for a while. I tested Reason with it and everything seemed fine. I thought I’d better replicate it to make sure before responding. So I switched back to my internet router and then started the process over and created a new network again.

After that however, nothing worked again. The same errors as before were happening, and I could not after 10 tries or so of different settings, (no password, with password, channel change, DHCP, Static IP) get the Ad Hoc Network option to sync again. The exact same behavior was happening as before this time around. So, I guess it was a fluke that it did work that first time.

Also, Mavericks Developer Preview 7 [ OS X 10.9 (13A569) ] came out today, so I upgraded to that after trying it several times. And after the update, no change to the behavior of this anomaly.

As far as researching the Apple dev forums, my partner will have to do that, as I myself don’t have access to them. I have notified him, and awaiting response from him on that. My partner is the one who does all the interaction with Apple on that stuff. I’m just running it on my machine along with him and it’s been fairly stable overall with this one exception.

Anyways, I’ll continue to use it over my normal wireless network for now, as it’s not a crucial time where things have to be 100%. But like I said, since my last post, latency hasn’t made your app unusable at all. It’s not even really noticeable during use with Reason, and seems responsive enough for what I’m doing currently. The latency runs from around 0 to100 ms in the Audio MIDI Setup Network window’s dialog. And after a few seconds of using the controller, it will go down to around 0, then return again once a MIDI signal is received again. But, I do want to resolve this eventually, as I want the best performance possible.

Also wanted you to know, I think your app is Amazing! I have created a couple of layouts for use with custom templates I’ve made in Reason and having a blast coming up with ways to interact with it. I also use Digital Performer but haven’t begun to interface with it yet. Being able to design and customize your own MIDI controller is just so great! I’m glad you designed this and made it public, and keep supporting/developing it strongly. I’m getting the new iPad whenever they release the next version, so I cannot wait to have more screen real-estate to use MIDI Designer on! Two big thumbs up!

Thanks again,
Jason

---

Hi, just getting to this now. We're having some issues with this notifications on this Q&A site that we're working out. Thanks for your patience.

---

Okay, I've read this over. First off, THANK YOU for the kind words about MIDI Designer. If you wanted to get them into a review for the App on the App Store, that would be highly appreciated.

Secondly: regarding Mavericks... so where are we on this issue? A simple Google search does reveal some anomalies regarding Wi-Fi and Mavericks: http://forums.macrumors.com/showthread.php?t=1596390... so we're hoping that Apple resolved any issues without any action on our part.

Thanks!
Dan

Answer 1

works fine for me, but i'm doing this on 10.7.5

---

i had a problem using sysex or nrpn one time, i forget which it was. it was only via this setup, direct connection worked fine.

midi designer recommened this and it worked (he also built this tool): http://confusionists.com/software.mjdj.aspx

Comments

I think the problem is that we were seeing some filtering using "live routing" via the Network connections on OSX. Glad to see that MJDJ worked for you!

---

Admin, did you ever find out more info about that filtering you saw in "live routing" via Network MIDI on OS X? I'm seeing the same thing and can't figure it out (came here from a Google search). It seems that the first two messages to specify a controller number via NRPN always get filtered in the Live Routing. Seems like some kind of bug in OS X?

Answer 2

works fine for me, but i'm doing this on 10.7.5

---

i had a problem using sysex or nrpn one time, i forget which it was. it was only via this setup, direct connection worked fine.

midi designer recommened this and it worked (he also built this tool): http://confusionists.com/software.mjdj.aspx