bitfocus / companion-module-newtek-ndistudiomonitor

MIT License
3 stars 0 forks source link

Companion NDI Studio Monitor Source Select Options #2

Closed petertapmedia closed 4 months ago

petertapmedia commented 3 years ago

Hey there,

with the NewTek NDI StudioMonitor Feature in Companion i have a few ideas/question. Maybe some of it is already possible.

E.g. when i have MS Teams connected to studio, meaning every participant sepreately and i want to choose the source depending who is currently speaking/needed (not meaning the active speaker view). Teams users show up in NDI only when they are dialed into the call. So my idea is if there is the chance of going through all the sources by pressing a button which always selects the next one with the button style alway showing the input name simultaniously.

Of course the "source" would have to stay on the teams input device.

If somebody has any other ideas that would be helpful.

My problem is mostly, that in a live streaming enviroments when participants are coming in to the call just in time, i have no chance of reprogramming any buttons and the only way of selecting them in that case is going to the studio monitor and manually scrolling through the list.

Thanks for help....

albertorighetto commented 3 years ago

This issue should be in https://github.com/bitfocus/companion-module-newtek-ndistudiomonitor/issues

I think it would be a solution only for a specific user case. Beside that, NDI Studio Monitor does not have a built-in "next" command so it would require a custom logic for that.

Have you considered using an external program to do this? Personally I'm doing almost the same thing using Node-RED combined with Zoom-OSC and Generic OSC module. You could pull JSON data from http://127.0.0.1/v1/sources and http://127.0.0.1/v1/configuration and build your own logic to manage the switch.

albertorighetto commented 4 months ago

I'm closing this issue. While totally understanding the need for this feature, I could not implement it because there's still not a API in Studio Monitor to cycle through sources. This is more of a custom implementation that needs a customized logic that doesn't exist in the original software. The logic will most likely not adapt to all use cases as it would require to make assumptions on what the user wants (alphabetical order? Order by ID? Cycle only current host? etc.).