NDI|HX2 Sources Showing Up Black
- Thread starter imryh
- Start date
Update - this isn't a Mac issue. I have a Windows PC that also won't show those source. Maybe it's a subnet issue. When I'm at home, using a VPN, I can see almost all our NDI sources, but not these cameras with NDI|HX2. But when I'm in the office, on the same subset as the cameras, everything is fine. Ideas?
kanep
Administrator
Are these devices on separate subnets from each other? Discovery and Transmission are different protocols, it possible that discovery packets are being forwarded between subnets, but the transmission packets are not. Which is why you can see the source name, but then get no signal once you select it.
You might want to look into NDI Bridge as the solution to connect NDI traffic between separate networks.
You might want to look into NDI Bridge as the solution to connect NDI traffic between separate networks.
So, yes. My computer and the cameras are on different subnets, connected through a VPN. BUT - everything worked fine yesterday. Our 100+ NDI and NDI|HX signals worked perfectly. Then, I updated these JVC PTZ 200 cameras to their newest firmware, which now uses NDI 5 instead of NDI 4. And suddenly, these cameras don't show an image. After a lot of trial and error, I was able to get the signal to work this morning by changing the NDI Receive Mode to TCP-Single. Now everything works. Any idea why that's the case?
kanep
Administrator
All of that is sounds like transmission modes. Starting with NDI 5, the preferred transmission mode is Reliable UDP. This is a UDP based protocol, from the Multi-TCP (TCP based) that would have been used with NDI 4.
Forcing NDI to Single-TCP is also using a TCP based protocol. Perhaps the VPN is only forwards TCP traffic and not UDP (or withing certain port ranges?)
Forcing NDI to Single-TCP is also using a TCP based protocol. Perhaps the VPN is only forwards TCP traffic and not UDP (or withing certain port ranges?)
Last edited:
OK. Just had a meeting with our IT group. UDP is not a factor here. They're not seeing any UDP traffic.
What they are seeing is that NDI Monitor initiates a connection with the camera, and then the camera in return tries to initiate a new connection back to NDI Monitor. That's prevented in our VPN. The connection must only originate within the VPN and point out. Then, traffic can flow in both directions.
Any idea why that's the case starting with NDI 5? And not a problem anyway when we switch to TCP-Single?
What they are seeing is that NDI Monitor initiates a connection with the camera, and then the camera in return tries to initiate a new connection back to NDI Monitor. That's prevented in our VPN. The connection must only originate within the VPN and point out. Then, traffic can flow in both directions.
Any idea why that's the case starting with NDI 5? And not a problem anyway when we switch to TCP-Single?
kanep
Administrator
I'm guessing. TCP connections are bi-directional and two-way (once the connection is created, both sides can communicate with either other), while UDP connections are connectionless and one-way (each side needs to send a UDP transmission to the other to communicate back and forth).
It sounds like, that to make it work thru the VPN you are going to have to use a TCP based transmission for NDI (Single-TCP or Multi-TCP) or look into using NDI Bridge.
It sounds like, that to make it work thru the VPN you are going to have to use a TCP based transmission for NDI (Single-TCP or Multi-TCP) or look into using NDI Bridge.
Last edited: