vvvv / vl.io.ndi

Nodes to receive and send NDI streams within vvvv

VL.IO.NDI

Provides support for the NDI® in VL.

Try it with vvvv, the visual live-programming environment for .NET
Download: http://visualprogramming.net

Using the library

In order to use this library you'll have to install the nuget that is available via nuget.org. For information on how to use nugets with VL, see Managing Nugets in the documentation. As described there you go to the commandline and then type:

nuget install VL.IO.NDI -pre

Once the VL.IO.NDI nuget is installed and referenced in your VL document you'll see the category "IO.NDI" in the nodebrowser. Press F1 to open the Help Browser and search for the term "ndi" to see relevant how-to patches.

Recommended

Download the NDI® Tools. They contain several applications (like Test Patterns and Screen Capture) to create NDI Sources on your computer.

Credits

Initial development by @mhusinsky and @sebllll

License

By using this you agree to the NDI® EULA which can be found in licenses/NDI License Agreement.pdf . NDI® is a registered trademark of Vizrt Group. See NDI.tv for details.

Sponsoring

Development of this library was partially sponsored by

• Refik Anadol Studio

For custom development requests, please get in touch.

vl.io.ndi's Issues

SourceSelector matches only 'SourceName', cannot select duplicate sources on different machines

There are three different name types for an NDI source, with some confusing overlap.

'ComputerName' = Name of the computer eg "WindowsRender5"
'SourceName' = Name of the source eg "Logitech Webcam C920"
'Name' = ComputerName + SourceName together eg "WindowsRender5 (Logitech Webcam C920)"

Currently SourceSelector node only matches for SourceName.
This means that if two machines have a source with the same name then mismatches can occur.

This can easily happen as the NDI Capture utility takes 'SourceName' automatically from hardware device names.
In my case I have multiple machines with a 'Logitech Webcam C920'

NodeContext for a Videoframe

Hi Everyone, I'm trying to create a nodeContext to pass to a Viseoframe from a texture2d. Could some one giovedì me some infos about it?

Crash when adding the VL.IO.NDI dependency

After installing VL.IO.NDI v0.2.1-alpha, gamma crash with the following messages when trying to add the NDI dependency to a blank patch:

error logs:
VL.IO.NDI-error-2020.2.2.log
VL.IO.NDI-error-2020.3.3-0056.log

When opening the examples in the help browser, the little dot, that turns into a cross next to the link to the example patch, turns into a rotating ring that never stops rotating.

also posted on the vvvv.org forum

HowTo Receive Stride Texures... opens with AV

sometimes recovers after press of F5, sometimes not

Changing connection source on receiver machine crashes ndi source program

Hi @mhusinsky . Having this issue with Gamma 2021.4.3 where the send and receive demos work perfectly across a local network, but if I change the the source image the receiver gets (e.g. from 'VL.Source Async' to 'Desktop Capture' for example, or adding an extra receiving PC) the The Gamma sending patch crashes

For a craic I tried replacing the runtime with the newest (5.0.10.1) but it didn't improve this issue, so its something to do with the connection stage.

To reproduce this, run both the NDI screen capture and the Gamma Sending howTo patch. On a separate machine in the network, run the receiving patch. It should show both the sources. Change source getslice. The Sending Gamma will close down without an error.

Audio output works in HowTo Receive Stride... but not in ...Skia.. help

Open issues for "redesign" branch

• Opening the "Send Skia images" or "Send Stride textures" helpers and closing it, fails with the following error:
  
• In "Send Stride textures", changing the size of the Neurons texture closes vvvv

Audio buffer output

extend receiver with methods to receive an audio buffer which could then further be processed in VAudio or other audio engines within VVVV

Metadata todos

• Receivers have a global metadata output but the sender no global metadata input
• The individual video/audio frame input nodes have metadata inputs, but their respective output nodes have no metadata output

Native dependency is not being copied during the Export

When exporting a patch with a dependency to VL.IO.NDI the exported app crashes because of the dependency error.
It can't find the native NDI dll.
Tested with 2021.3.3 (the test fails when the app is starting as a non-admin user, so that the system can't find the dll. The dll is not being copied into the app's folder)

At the moment the folder structure of the nuget is:

The new nuget format is specified here:
https://docs.microsoft.com/en-us/nuget/create-packages/supporting-multiple-target-frameworks#architecture-specific-folders

So would be cool if it's possible to move that native dll into the: runtimes/win-x64/native.
Devvvvs are finishing the support for the new nuget format. But the new folder structure is already working since end of may.

Thank you!
Anton