1 Topic by kope (edited by kope 2025-04-21 05:11:54)

  • kope
  • ADAT user
  • Offline
  • Registered: 2018-03-07
  • Posts: 16

Topic: RME connector app no longer discovers 12MIC over ethernet

Hi there - Currently, RME connector app is working fine using MIDI over UFX+ port 3 (connected by MADI to 12MIC). It used to work well over ethernet as well until I updated to macos sequoia 15.4.1

12MIC remote is working just fine in the web browser (http://12mic.local/) so I still have all remote functionality I need. It's just the Connector App that stopped working by IP and no longer finds my 12MIC device.

I was wondering if anyone else is having the same problem on macOS?

Cheers, thanks!

(running macOS 15.4.1, apple silicon M4 max. HTTP remote is on, MODE set to DHCP on 12MIC)

2 Reply by waedi (edited by waedi 2025-04-21 06:36:06)

  • waedi
  • DAW Mastermind
  • Offline
  • From: Swiss Zürich
  • Registered: 2020-12-08
  • Posts: 7,815

Re: RME connector app no longer discovers 12MIC over ethernet

kope wrote:

It's just the Connector App that stopped working by IP and no longer finds my 12MIC device.

MODE set to DHCP on 12MIC)

If you set the 12Mic to IP ?

M1-GoldenGate, Madiface Pro, Digiface USB, Babyface silver and blue

3 Reply by kope (edited by kope 2025-04-21 07:24:21)

  • kope
  • ADAT user
  • Offline
  • Registered: 2018-03-07
  • Posts: 16

Re: RME connector app no longer discovers 12MIC over ethernet

you mean static IP?

these are the settings in 12MIc as of now

  • HTTP remote is ON

  • IP settings primary is set with MODE=DHCP (allocated IP: 192.168.100.172)

  • none set for IP secondary

edit:
12MIC is reachable by browser (12mic.local). Only the RME Connector app doesn't find it

4 Reply by maggie33 (edited by maggie33 2025-04-21 23:47:44)

  • From: Germany, Tuvalu, Poland, Chile
  • Registered: 2021-07-27
  • Posts: 1,120

Re: RME connector app no longer discovers 12MIC over ethernet

IP settings primary is set with MODE=DHCP (allocated IP: 192.168.100.172)

192.168.100.x is usually reserved for DOCSIS Networks (thus also valid in private networks).
Anyhow, this looks odd (the unit is probably in another network segment than your Mac (and the Connector App))?

- Both, Mac and unit, should be in the same network.
- Ensure the unit gets its IP from the same DHCP Server as your Mac gets it (or set a static IP for the unit in the same network segment).
- Check if you can ping the IP of unit from Mac's terminal.
- Also check firewall settings.

“Do It For Her”
My Gear: Bontempi Magic light Keyboard
  • Max
  • Max
  • Moderator
  • Offline
  • Registered: 2007-05-09
  • Posts: 361

Re: RME connector app no longer discovers 12MIC over ethernet

It seems that one of the latest Sequoia updates indeed broke the discovery mechanism. Even though one allows the access to local network devices, they do not get discovered. We will take a look into this.
Max

  • Max
  • Max
  • Moderator
  • Offline
  • Registered: 2007-05-09
  • Posts: 361

Re: RME connector app no longer discovers 12MIC over ethernet

Please try 2.0.1 beta 7. Settings > Check for beta updates.

  • kope
  • ADAT user
  • Offline
  • Registered: 2018-03-07
  • Posts: 16

Re: RME connector app no longer discovers 12MIC over ethernet

Max wrote:

Please try 2.0.1 beta 7. Settings > Check for beta updates.

Hi Max - thanks for the feedback. I've updated to 2.0.1 Beta 7 but the problem persists.

I tried to delete and re-instantiate an IP connection in the Connector App but my 12mic is still not discovered.

However, the device is found quickly in Safari Browser by web address (12mic.local) or IP: 192.168.100.172

  • kope
  • ADAT user
  • Offline
  • Registered: 2018-03-07
  • Posts: 16

Re: RME connector app no longer discovers 12MIC over ethernet

maggie33 wrote:

IP settings primary is set with MODE=DHCP (allocated IP: 192.168.100.172)

192.168.100.x is usually reserved for DOCSIS Networks (thus also valid in private networks).
Anyhow, this looks odd (the unit is probably in another network segment than your Mac (and the Connector App))?

- Both, Mac and unit, should be in the same network.
- Ensure the unit gets its IP from the same DHCP Server as your Mac gets it (or set a static IP for the unit in the same network segment).
- Check if you can ping the IP of unit from Mac's terminal.
- Also check firewall settings.

I've setup my network with 4 VLANS:

  • Management (switches, router, hot spots, etc): VLAN ID: 1 (192.168.99.[...])

  • IoT (all my smart appliances): VLAN ID: 98

  • internal LAN (where my Mac and 12MIC are assigned to) VLAN ID: 100 (192.168.100.[...])

  • and Guest LAN (for clients and guests) VLAN ID: 101 (192.168.101. [...])

12MIC is reachable by browser using this IP: 192.168.100.172

  • From: Germany, Tuvalu, Poland, Chile
  • Registered: 2021-07-27
  • Posts: 1,120

Re: RME connector app no longer discovers 12MIC over ethernet

So it looks like your Network should be ok.

Just one Idea I have, maybe worth to try:

Set your VLAN 100 interface on top (via set order option in Mac Network Settings Pane).

PS: I myself have no RME Network equipped unit here, so cannot verify your situation.

“Do It For Her”
My Gear: Bontempi Magic light Keyboard

10 Reply by Max

  • Max
  • Max
  • Moderator
  • Offline
  • Registered: 2007-05-09
  • Posts: 361

Re: RME connector app no longer discovers 12MIC over ethernet

The fact that the problem came with the macOS update (and not with a new network configuration) indicates an issue with macOS permissions. In particular, System Settings > Privacy and Security > Local Network should show an Entry "RME Connector" that is automatically created when the user allows the application to access the local network on first start after update. However it seems that the newest Sequoia version does not trigger the request to allow access to the network - we will check this.
Max

11 Reply by Max (edited by Max 2025-04-23 05:56:15)

  • Max
  • Max
  • Moderator
  • Offline
  • Registered: 2007-05-09
  • Posts: 361

Re: RME connector app no longer discovers 12MIC over ethernet

Managing the access control entries in macOS is tedious, even though there are some great reads (like this one) and tips on how to remove specific entries:

sudo tccutil reset All com.rme-audio.connector

I ended up going into recovery to wipe the entire thing. Also I deleted Connector and rebooted. After downloading Connector Beta 7 (Apple Silicon) once again, installing it lead to the correct prompt:

Allow

After I pressed Allow, Connector could NOT see the devices on the network... until I quit and restarted Connector. Then, it works without problem. I agree with most people out there that Apple should make tcc management a bit more transparent and understandable.

Let me know if this helps to solve your issue; it might not even be necessary to use the beta version (although it certainly won't cause problems, either).

-Max

Edit: the reason why I intentionally wanted any "RME Connector" entries REMOVED from the Local Network access list in system settings is: when I right-clicked the entry to "show in Finder", it lead me nowhere (not to a specific installed program) and the manual removal described above with the sudo command showed "not found". If your tcc-database is healthy, it may be sufficient to just ensure 'allow' is active on the corresponding entry. However it seems that there is a bug in macOS 15.4.1 that scans the system for similar applications and re-uses their access permission (even if the bundle id is different), so I wanted the entire database cleaned up.

  • kope
  • ADAT user
  • Offline
  • Registered: 2018-03-07
  • Posts: 16

Re: RME connector app no longer discovers 12MIC over ethernet

Hi Max - thanks for looking into it and walking us through this fix. I'm off for the next couple of weeks and not near my RME rig. Will test when be back. thank you!