I’ve been testing NDI Bridge lately, to deal with NDI outside your local network. I think that means that there is an extra step in the address (Group + computer_name + source_name), it should be just an extra slash, right? I cannot seem to find the way to make it work, and I wonder if it’s a server limitation.
#200 NDI LIST OK
1 "MOUNTAIN (Remote Connection 1)" ndi-app:MOUNTAIN%20(Remote%20Connection%201)
2 "TEST (LAPTOP-KDN2J54S (Remote Connection 1))" 192.168.0.183:5963
3 "TEST (LAPTOP-KDN2J54S (Rotulos))" 192.168.0.183:5964
play 1-10 ndi://TEST/LAPTOP-KDN2J54S/Rotulos"
[2022-04-07 18:41:10.990] [info] Received message from Console: play 1-10 ndi://TEST/LAPTOP-KDN2J54S/Rotulos"\r\n
#202 PLAY OK
[2022-04-07 18:41:10.990] [info] ndi[1|TEST (LAPTOP-KDN2J54S)] Source currently not available.
play 1-10 ndi://LAPTOP-KDN2J54S/Rotulos/"
[2022-04-07 18:41:35.847] [info] Received message from Console: play 1-10 ndi://LAPTOP-KDN2J54S/Rotulos/"\r\n
#202 PLAY OK
[2022-04-07 18:41:35.849] [info] ndi[2|LAPTOP-KDN2J54S (Rotulos)] Source currently not available.
“TEST” is the name I gave to the NDI Bridge group to receive it. When I open NDI Monitor I can go to TEST / LAPTOP…/ Rotulos and see the source with no problem.
but with Caspar 2.3.3 I keep getting “Source currently not available”.
If anyone gets different results let us know!
Thanks