Industrial gigabit camera's (like SVS-Vistek) are using jumbo frames (9015Kb) to send high resolution video real-time over gigabit network.

NDI is IP based, but is not using IP addresses if I am correct.
Does it work like a Sony or Axis setup tool that can find all IP camera's even in different network ranges?

Is NDI using jumbo frames too for transferring big data blocks trough the network?

It would be very interesting if gigabit IP camera's could be seen as NDI sources by using a SDK.

More specifically, NDI uses mDNS (Multicast_DNS) to broadcast it's resources and find other NDI resources.
mDNS is also the mechanism used other services and systems - Apple Bonjour is just an example.
https://en.wikipedia.org/wiki/Multicast_DNS

NDI is not using Jumboframes.
Instead, it uses small IP frames - but there are a lot of them.

If you want to route your NDI packages across network segments or use WiFi, you will need enterprise grade accesspoints or high-end gaming routers that has the extra processing power to handle the high package rate.

/Jon

RTSP was created with no specific intention regarding latency. It's a delivery format, not a production format. A such, it leverages H.264/5 Long-GOP compression, which inherently adds delay in traditional implementations.

Long-GOP achieves high-compression by evaluating a group-of-frames and encoding redundancy withing the frames in the group. A such, the entire group is processed before it can be shipped down the wire. That can be several seconds of video, even before buffering.

In crafting NDI Newtek has establish a consistent way of using RTSP that addresses issues of latency. NDI 2.0 does not use long-GOP. It compresses each frame individually, not unlike MJPEG. That limits the compression rate that can be delivered, but ensures latency of < 1 frame.

NDI|HX uses a proprietary, modified form of long-GOP that achieves better compression, but send the frame data incrementally, not processing the entire GOP before sending down the wire. It's an attempt to have the next of bother worlds; high compression rate (low data rate) and modest latency.

"Proprietary" means that it was created by Newtek without engaging any of the traditional standards bodies, like SMPTE, AES, EBU, etc. While they publish the protocol, it remains theirs. It's not an internationally agreed upon standard. Standards processes are slow and costly, so it's easy to understand why Newtek would skip that process.