NDI Bridge, therefore, handles all the complexity of remote sources on a truly potentially global scale, while still working with alpha channel, KVM, PTZs, tally, metadata, and all the rest of the bells and the whistles it brings to the table. Called, pragmatically enough, NDI Bridge, it enables users to securely share NDI sources between remote sites wherever they may be using what the company promises is a simple and secure network setup. What NDI has done with NDI 5 is build its own bridge.

It’s not worth going into them in too much detail here as we don’t know quite how NDI has solved them, but there have been workarounds for this for a while.Įffectively you use a third party bridge between separate NDI networks, ingesting it in one location, compressing it, and squirting it using a low-latency protocol such as RIST or Zixi to another, where it is uncompressed and broadcast on the local LAN once more as NDI. NDI was designed initially to provide plug-and-play capabilities via a combination of TCP socket connections and Bonjour service announcements over a LAN, and there are a couple of factors that limit their use when scaling up from a Local Area Network to a Wide Area Network. And it’s honestly not hyperbole to say that this is a bit of a game-changer when it comes to IP production as this lifts the uses of the NDI protocol away from the LAN and up to a point where NDI networks can talk to each other no matter where they are. A new version of NDI opens up the possibility of establishing plug-and-play broadcast and production networks pretty much anywhere you want them.īy now, no doubt you will likely have seen the news that there is a new flavour of NDI on the way NDI version 5 is going to be made available at some point in June.

Ndi remote for mac