It’s generally considered best practice to sign on to existing requests with a +1, and, if you have more to add by way of use or reason, additional information.
That’s how interest is generally monitored.
2 of which are mine, which you can find here:
https://forums.vmix.com/...-as-a-Data-Source-optionhttps://forums.vmix.com/...nt-attributes-to-API-XMLIt’s also, to my understanding, considered best practice to use a separate thread for each request to allow for easier finding and monitoring.
I’d originally requested, as you did, adding the full list of participants to the API.
After thinking about it, I deleted it and replaced it with the 2 above requests, which make more sense logicially and productively.
If it’s a data source option, you can easily convert it to the API without needing to bog down the API with large meetings.
As for “index”, while it would certainly make it easier for scripting, from what’s been said before, the system is set up to use names exclusively. That’s why the unique name requirement is in place.
I’ve been asking for it since within a couple of hours of the beta’s first release, in various forms. It was suggested to me at that time by another user that name selection would very possibly be the compromise used.
So while that would be nice, I wouldn’t hold my breath. It can, however, by easily simulated with the Data Source suggestion.
Number 5 has been explicitly ruled not possible, again, from the very outset of the beta. Your best option is to set it to set it to a separate output and run a mix on that output using the output input.
If you don’t have additional outputs, I highly recommend upgrading, but, absent that, you can sacrifice your main out and use the Fullscreen in conjunction with something like OBS to simulate additional outputs.
