assurance-tunnel
assurance-tunnel
assurance-tunnel
assurance-tunnel

[ANSWERED] Handling NDI Watcher as Connections Appear and Disappear



  • [EDIT: I've take the liberty of modifying the title of your thread to help other users understand what you're asking. -- Mark]

    Hi,

    Having quite a lot of fun piping in numerous NDI sources into different environments.

    Stress testing this revealed a bit of a problem in terms in a busy use case with lots of connections coming in and dropping off.

    It'd be good to be able to assign the list of current connected NDI sources to a lookup table which is then hardwired to indivdual NDI watchers.

    Is there a <listofNDIsources> variable globally accessible?

    Cheers as ever,

    Rob



  • @robhblack said:

    Is there a  variable globally accessible?

    No, that's not available. We'd have to create an actor to "ask" NDI about its sources.... probably we could output them from the NDI Watcher actor itself. I will need to look into this to see how difficult it would be to accomplish.

    Best Wishes,
    Mark



  • Thanks, it's a brilliant tool.

    Been trying to feed it with various variables to select sources, a source index variable would be plenty, given it knows the total that could be fed back in as (total - watcher number) = index.

    Couple of videos, excuse the Dad dancing! https://twitter.com/BeckStewart_/status/1264238016647835648 and https://twitter.com/petewoodbridge/status/1268793854377037824

    Best, Rob



  • @robhblack said:

    It'd be good to be able to assign the list of current connected NDI sources to a lookup table which is then hardwired to indivdual NDI watchers.

     I am not sure I understand what you want, but could it be a solution:

    ,

    best, Jean-François


  • Hi JF, yes that is a pretty effective workaround, except the issue is the sources aren't default assigned in the individual watchers. This solution would def help improve speed of live switching though since we can put logic in. So thanks, that's a great help.



  • +1 for getting access to an input list similar to the Screen Capture actor. sometimes the NDI source has a pretty complicated name and having to type it all in accurately has more potential for error.



  • @robhblack said:

    the sources aren't default assigned in the individual watchers.

     

    use the initialize option or this:


    best, Jean-François 



  • @dbini

    there is already one:

    best, Jean-François 



  • Hi,

    Thanks for the additional advice, I'll give it a shot. Cheers, Rob



  • Hi, I've packaged up the Selector solution with User Actors with a completely horrible little Javascript rolodex. But when set up for the first time it is one click to shunt sources around.

    Cheers,

    Rob

    useractorndi.izz