Skip to main content

Tech Forum

Using Access Manager to manually connect to sources

Using Access Manager to manually connect to sources

by Bill Gillock - Number of replies: 3

If I want to manually connect to an NDI source on my network, do I run Access Manager on the source machine, or the receiver machine? Do I add this IP as an External Source? If so, why can't I enter a Local Device NDI name and channel? 


Thanks for your help in advance!

In reply to Bill Gillock

Re: Using Access Manager to manually connect to sources

by Kane Peterson -
You configure this on the receive systems.

NDI sources don't let you set a local name because this information comes from the source device. In the case of older NDI-HX1 devices (the other type you can choose), those let you set a local name.
In reply to Kane Peterson

Re: Using Access Manager to manually connect to sources

by Bill Gillock -
Thanks for the clarification! I was successful in setting this up manually on the receiver.
In reply to Kane Peterson

Re: Using Access Manager to manually connect to sources

by Bill Gillock -
As I said, this works well. Not only do I get the external source using the find API in the SDK, I can also receive the signal when using that p_ndi_name.
To make it easier for my users to connect manually, I want to use the NDI SDK to achieve the same thing. If I use the p_extra_ips field in the NDIlib_find_create_t API and provide the IP address I used as an external source in the Access Manager, I get the external source with the p_ndi_name in the list returned. However, when I try to create a receiver with that p_ndi_name, it does not receive a stream. The creation of the receiver seems to work, just no signal.

FYI: To force manual mode, I am blocking the mDNS port UDP 5353 inbound on both machines so I can emulate situations where a user will need to connect manually with an IP.

Is there something else I need to do in order to receive the stream from the manually specified external source using the SDK?