Sierra has broken Midi Network Studio

Question

Level 1

9 points

Sierra has broken Midi Network Studio

So, I just figured out that Sierra broke midi networking. I've been using a midi network for quite awhile and I did a clean install on an older Imac, and now midi network setup errors when I try to connect to another mac(ElCapitan) on my network. Here's the error msg:

mycomputer:5006 didn’t respond to the connection request. Check the address and port, and any firewall or router settings. (13:25:47)

I've tried every conceivable combination in network settings to fix, but no good. I also tried connecting to another computer(Yosemite) on the network, and it gives the exact same error. I am upgrading my laptop to Sierra now to see if it will talk to the Imac Sierra box.

Until then, my midi network is hosed.

iMac, macOS Sierra (10.12), null

Posted on Oct 4, 2016 11:56 AM

Reply

Answer 1

arebee70

Level 1

8 points

Mar 17, 2017 6:13 AM in response to cuttime110

does disabling IPv6 affect my web browser? i need to go online AND network midi over ethernet.

im just asking because i had this problem, with a normally strong connection for years until Sierra broke it!

i use fixed IPs for midi network devices in network prefs with specified device IP in midi network settings.

now some days its ok briefly, then 'randomly' disconnected, then it seemed it was due to me going online, browsing would cut off the midi network roughly the same time. alternatively if i was browsing then initiated a midi network connection, my browser would inform me that i was disconnected from the internet, while my midi network worked.

i got a fix but only after this... * i rearranged the 'set service order' in network prefs: my services were in this order previousy;

1 ethernet/thunderbolt bridge

2 WIFI

it now works every time - as soon as i rearranged it to;

1 WIFI

2 ethernet/TB bridge

hope this helps without disabling IPv6

* i only rearranged the service order because in a blind panic i deleted all my ports in network settings and tried to rebuild the list with new thunderbolt & ethernet ports (no proof that it helped in any way other than the order changing)

cheers

Reply

Answer 2

Feb 1, 2017 11:38 AM in response to RHMedia

Disabling IPv6 has fixed the issue for me. http://osxdaily.com/2014/04/18/disable-ipv6-mac-os-x/

Reply

Answer 3

RHMedia Author

Level 1

9 points

Oct 4, 2016 1:20 PM in response to RHMedia

So, after installing Sierra on my laptop, I am getting the same error message when I attempt to connect to my Midi network. So, I think it's safe to say there is a bug here.

Since I am not a developer, can someone verify and send a bug report?

Reply

Answer 4

Oct 21, 2016 2:14 AM in response to RHMedia

We were having massive issues with network MIDI in 10.12 as well...

I just filed a bug report with the number: 28887117

We can only hope Apple gets back to this soon...

Reply

Answer 5

Nov 10, 2016 1:40 PM in response to guitarflow

Still no word. I can't upgrade or it will break my current workflow. I use QLAB for a lot of things and this bug will render it almost useless.

Reply

Answer 6

Nov 13, 2016 2:19 PM in response to RHMedia

I am having this exact same problem. I waited a good while before upgrading to Sierra, and I thought the coast was clear. I use WiFi MIDI networks, and I found that if I use an ad-hoc connection the network works. Everyone should know by now that ad-hoc connections are not secure, and I really don't want to work that way. I am coming to the conclusion that WPA Security may be part of the problem. Apple need to fix this ASAP.

Reply

Answer 7

Nov 14, 2016 8:24 AM in response to cuttime110

FYI, I did hear from Apple Development regarding this issue, and they are aware of it. No further info was given. If there is anything I can publicly disclose, I will do so here.

Reply

Answer 8

Dec 13, 2016 11:03 AM in response to cuttime110

Good News! I just received word that this issue has been addressed in the new update (macOS Sierra 10.12.2) that just released. I'm going to test it out, but I wanted to let you all know.

Reply

Answer 9

Dec 13, 2016 3:32 PM in response to VolksWatson

Thanks so much for keeping us informed. My fingers are crossed.

Reply

Answer 10

Dec 15, 2016 5:36 PM in response to VolksWatson

I'm sorry to say that I did the update and I still can't connect, but I get a new error, if anyone has any tips I would greatly appreciate it:

Reply

Answer 11

Dec 15, 2016 5:46 PM in response to cuttime110

i noticed that it worked, but only from a sierra macbook to an sierra imac... any older ios macs gave an error. AND, it only connected when initiated from the imac, not the macbook. weirdness.

Reply