Skip to main content

Tech Forum

Black content when sending from MacOS device to Windows machines

Black content when sending from MacOS device to Windows machines

by Juan P Gimenez - Number of replies: 2

Hello, 

Sorry if this sounds like very basic issue but I have been trying to solve it with people from network AV guys and could not solve it easily, only with what sounds too complicated for me.

Summing up, I have a setup with Mac computer, Windows and GrandMA3 lighting console. From all the machines, we can see all the sources (discovery seem to work fine) but when the Mac is sending, we are only getting black image across the windows devices (we tried few) and lighting console.

Instead, if the Windows is sending, the image is displayed correctly (mostly).

We managed to see the Mac source in one of the windows machines by setting up a discovery server (SDK) in one of the machines and point the Mac video traffic to the IP of that windows machine but seems like too complicated solution for a “simple” issue.

Needless to say that this solution does not work for the lighting console (as the NDI configuration is very limited).

We tried several combinations disabling network protections, using different IP ranges, etc… From the Mac we tried outputting with test patterns, webcam, screen capture or with direct NDI output from QLab.


Any advices or solutions to test? Many thanks in advance.


Juan

In reply to Juan P Gimenez

Re: Black content when sending from MacOS device to Windows machines

by Kane Peterson -
Sounds like a network firewall issue to me.

If these systems are using the built-in firewall. On the PC, make sure the network type is too 'Private' (this will make the Windows Defender firewall allow local traffic). And verify the macOS firewall isn't configured to block and traffic. If are you using a third-party firewall software on the Mac to PC, try disabling to see if that helps.
In reply to Juan P Gimenez

Re: Black content when sending from MacOS device to Windows machines

by Zoe Williams -
You might try specifying the IP address in the remote sources tab of access manager