Cannot discover stream on the network

[Yuutsuna]

When I do
gst-launch-1.0 videotestsrc ! ndisink
I'm able to send a video with NDI.

I have a mixing desk that is able to discover devices that streams over NDI. But when I have my pipeline running the mixing desk does not detect it. Is it normal?

[sdroege]

Does it show up with gst-device-monitor-1.0 -f?

[Yuutsuna]

No my stream does not appear

[sdroege]

Can you get a debug log with GST_DEBUG=ndi*:9 of both the gst-launch-1.0 and the gst-device-monitor-1.0?

[Yuutsuna]

gml.log
ndipipeline.log

[sdroege]

Looks all correct but for some reason the NDI SDK indeed doesn't find the source. Not sure what the problem there is. Does it work with the send samples from the NDI SDK on the same machine?

[Yuutsuna]

I just tried one more time to be sure and I'm able to receive the stream on the local machine and another machine on the network by specifying the url-address.
When I put only a ndi-name and I'm not able to get the stream (pretty much expected)

I made a program to listen the multicast traffic on 224.0.0.251:5353 and I don't see anything coming from my computer when I start or stop the NDI stream. To be sure, does the ndisink send multicast packets for device discovery or should I do it myself?

[sdroege]

ndisink doesn't do that but the NDI SDK is doing that automatically. I think your problem is then either in the SDK or in your network configuration.

[Yuutsuna]

Ok so I was able to get it partially working.
I'm on Arch Linux and I installed the avahi package. And now my program is receiving multicast packet containing the ndi-name I specified so the device discovery seems to work.
Using the NDI Tools from another computer I'm able to detect and see the stream from my computer.
The only problem is that my mixing desk does not detect anything.

So it was a problem with my configuration.

I'll still post updates about the mixing desk if I get it to work

[mindriot88]

I found that I can reproduce similar results on a system if ipv6 is disabled, it maybe unrelated to your issue but its worth checking if this applies to your system/network configuration.

[Chron-O-John]

for anyone reading this in the future:
I don't know what it was exactly that helped, but after installing all the dependencies and pre-requisits from the following url it worked:
https://github.com/lplassman/FFMPEG-NDI

(this is only for the NDI part, you can ignore all FFMPEG stuff)