I'm trying to setup an old iPad2 as a WiFi MIDI controller on my 2018 Mac Mini.

iOS 9.3.5, OSX Catalina...

When I create a Session in the Mac MIDI setup, my new iPad (iOS 14+) connects fine. My old iPad doesn't show up as a Device for some reason. I've also tried manually adding the old iPad (using it's IP as a host name, not sure if that's correct).

I'm assuming something is incompatible but I can't find any specific thing that would prevent this connection. I can ping the iPad from the Mac so I'd assume they can connect.

I'm using Knob Lab on the iPad, which is supported on 9.3.5 but it shows no WiFI connection.

Also, I can't get Bluetooth to connect either.

Any ideas or info would be appreciated.

bump

maybe this is some related information.

https://discussions.apple.com/thread/250790806

Thanks for that link.

I'm assuming it is just a compatibility issue but can't figure out with what exactly.

Since this connection should just be using WiFi and MIDI, I can't think of anything 'operating system specific' that would prevent this from working.

They are on the same network and can see each other. MIDI info wouldn't change from OS to OS. I'd be just as satisfied to figure out 'Why Not' as I would with 'How'.

From some reading it sounds like the connection point for WiFi MIDI on the iPad is attached to the app. I downloaded another app (MIDI Controller Free) and my iPad appeared in the Device list in Audio MIDI Setup!

BUT... I still can't connect. After it tries for about 5 seconds it returns with:

"(host/port) didn’t respond to the connection request. Check the address and port, and any firewall or router settings."

Since my newer iPad connects I should be able to rule out firewall and router settings.

The host part of the message looks kind of like a Mac address but with more characters, not sure where that name comes from exactly.

maybe it's something related to incompatible bit depths.
the Catalina OS I believe was a full 64bit system.
e.g. it may not work with a system which was still 32bit.

High Sierra could handle a mix of 32bit and 64bit drivers for example.
but it was unable to run 32bit and 64bit midi drivers, if both types were in the midi driver folder, together.

but in Catalina, the 32bit driver (I'd assume) would not even be accepted in that folder as it would likely be totally incompatible.

so maybe a similar case exists, with a similar bit depth incompatibility, in your case. related to different parts of the OS system, and not simply just the midi drivers.

so maybe 32bit communications using the protocols you are needing to communicate, are suffering similarly.

Thanks for your comments. Good thinking, that very well could be it! I'll keep trying and reading and will report back with anything I find.

The number of bit of the cpu/applications shouldn't have any relevance when it comes to network protocols (and data in general)

Maybe you're seeing a IPV6 address (instead of an usual IPV4 address)?

I wouldn't rule out a firewall/router settings issue.


Unfortunately I have almost no experience with network midi (even if I have various Apple devices) and the info on the thread are not sufficient for me to get an idea of what's going on, I'm sorry.

Here's the full message:

"fex0::cx6:2e7x:86bb:23xc:5004 didn’t respond to the connection request. Check the address and port, and any firewall or router settings. (13:50:30)"

I know that 5004 is the port its connecting through. ipv6 would be 8 sets of characters, right?