Q Light Controller+

Hello all QLC+ friends, hello Massimo.
I need your help to better identify a strange situation that I noticed a few days ago. I'm a little sad because I don't know how to identify the problem.

As the title says, the e131 plugin doesn't work anymore. I'm using the latest version of MacOS (freshly installed) on an Intel Mac Mini and the latest QLC+ 4 version. The node is a Showtec NET-2/3 Pocket connected directly via the onboard ethernet to the Mac Mini, both have static addresses. For some debugging:
1. tried ArtNet and works perfectly.
2. on an Intel MacBook Pro (penultimate version of MacOS, latest of QLC+) everything works flawlessly.
3. tried unicast and multicast, none working.
4. tried different nodes and Ethernet cables.
5. over Wifi same behavior!
6. tried a different NIC (usb-c to eth adapter) same behavior.

I’m at a loss; I don’t know what else to try. Attached detailed specifications and some images.
Thanks friends for all that you’re doing.
With love, from Italy,
Marco

Latest macOS requires you to allow each app that access network. Check if QLC+ and/or e131 plugin is allowed. I can't tell you details, try to search the internet, there is a lot of people having network issues with Sequoia.

Jano

marcopiro wrote: ↑Thu Nov 14, 2024 12:19 am
5. it works over WiFi (if I connect the node to an access point/router and then the Mac Mini to WiFi).

This is strange ...
If you connect your sACN device directly to your Mac's NIC, did you use a cross-network cable? (This is an old habit; technology should have evolved.)
Can you ping the device directly when it is connected? If not, a $20 network switch will solve your problems...

GGGss wrote: ↑Thu Nov 14, 2024 8:29 am

marcopiro wrote: ↑Thu Nov 14, 2024 12:19 am
5. it works over WiFi (if I connect the node to an access point/router and then the Mac Mini to WiFi).

This is strange ...
If you connect your sACN device directly to your Mac's NIC, did you use a cross-network cable? (This is an old habit; technology should have evolved.)
Can you ping the device directly when it is connected? If not, a $20 network switch will solve your problems...

My bad, over WiFi I get the same results.
Nope, I'm using a straight cable. This system worked until a few months ago.
Everything was initially connected to my studio's network (this setup was also tested and working) but to simplify debugging I connected Mac and Node directly, putting everything in static mode.

janosvitok wrote: ↑Thu Nov 14, 2024 5:57 am Latest macOS requires you to allow each app that access network. Check if QLC+ and/or e131 plugin is allowed. I can't tell you details, try to search the internet, there is a lot of people having network issues with Sequoia.

Jano

Your answer pointed me on an interesting and promising direction.
In fact, QLC+ is not listed in SysPref, Privacy & Security -> Local network. As you can see there are other apps that use the network.
I noticed that the other apps, unlike QLC+, opened the first time after installation, asked me for permission to access the local network.
My lovely QLC+ unfortunately not.
And I have no idea how to make it pop out either!
Still digging...
Many thanks.
Marco

Try this: https://developer.apple.com/forums/thread/663839
This may be interesting as well: https://developer.apple.com/forums/thread/663858

Jano

janosvitok wrote: ↑Thu Nov 14, 2024 5:18 pm Try this: https://developer.apple.com/forums/thread/663839
This may be interesting as well: https://developer.apple.com/forums/thread/663858

Jano

Thanks for your kind reply.
I solved it by launching QLC+ from terminal, for now.
In fact, Apple says in the FAQ that, if launched from the terminal, the apps have full permissions to connect to the local network.
From what I understand there must be an update of the apps to ask MacOS to talk to LAN devices but this is beyond my knowledge!

Thanks for your help, I hope this report can be useful to others too.
See you soon, QLC+ friends.
Marco