We frequently use an NDI Input for sources from presentation laptops and applications. Typically we name this Input "Laptop" and manually select which NDI source to use by right-clicking the Input.

Selecting the NDI source instead via the shortcut NDISelectSourceByName currently requires that we manually enter the source's name after finding it out by looking at the available NDI sources. For example from the list shown when right-clicking the Input, our by an external application like NDI Studio monitor.

But we would like to automate this with scripting and Companion. Hence it would be perfect if vMix's API contained a XML element with all available NDI sources. In addition it would be useful if the <Input> element also included the currently selected NDI source as an attribute. For example as ndisource="PC1 (Display 2)". This would also allow use to change the name of the Input to also include the NDI source (e.g. "Laptop - PC1 (Display 2)".

I believe this feature would also come in handy for other types of NDI Input uses, like NDI feeds from Teams. In effect offering us a way to build an NDI router with vMix that only uses the bandwidth required for the currently selected NDI source.

Side notes (v27 and v28):
1. When opening a Preset, vMix's NDI Inputs does NOT include a checkmark that shows the currently selected NDI source.
2. The shortcut NDISelectSourceByName does not change the Input's original name (manual selection of NDI source do change the original name).
3. We still have the problem that we cannot disconnect all NDI sources from an NDI Input (compare this FR)

+1

To begin with, Data sources feed Title Inputs, one source row at a time. This is not the way I want it for a smart integration with scripts and Companion. Also, the Data source scan interval is determined by a setting in the Data source manager, not "constantly".

Furthermore, I do not know how the NDI SDK keep track of available NDI sources or how much impact vMix would have on system resources when getting that info into the API. I think that's a question that the vMix developers can answer in order to assess the feasibility of this FR.

One way for vMix to limit the resource impact would perhaps be a new Settings/Option "Update NDI source data every xxxx milliseconds". Where 0 would mean "never", for those who does not need this information.