obs-ninja-trampoline VS obs-scripts

In the docs, you can check the headings for the individual query string parameters - &bitrate for example is under "Viewer's Settings", so I'd try and use it in the browser source link. But didn't try myself, so just experiment with it - and maybe use https://rse.github.io/obs-ninja-trampoline/ to generate links and check the params there.

Try Vingester creator's OBSninja URL generator. There is a drop down for Greesnscreen/blur effects in the push options for attendees. https://rse.github.io/obs-ninja-trampoline/

When using OBS.Ninja, my personal recommendation is to use my companion tool OBS.Nina Trampoline: for each participant, create an URL with session mode "sender" and give it to the participant and use the same config but with session mode "receiver" and use the resulting URL in Vingester. The "receiver" mode automatically configures OBS.Ninja to have the participants video alone and no composite variants of all the participants. Just repeat this sender/receiver URL generation for each participant, but with a different "Peer Id" each time.

First, OBS.Ninja has tons of cool parameters. That's great for configuring OBS.Ninja in various scenarios, but it's nasty if you just want to create intuitive, short and stable URLs for the participating parties. My first tool, OBS.Ninja Trampoline, allows you to fill out a simple form and generates a more intuitive and stable URL which can redirect to the underlying complex technical URL of OBS.Ninja. It especially allows you to control OBS.Ninja parameters at a central place while being able to use clean, intuitive and stable URLs for both the presenters and the consuming OBS Studio in video production. The tool itself is just a simple file and can be either used via the central Github Pages URL or self-hosted in order to change the parameter mapping. If you don't self-host it, you at least have to accept my opinionated set of OBS.Ninja parameters in the tool.

The third point for me in using NDI is that NDI is usually part of a production environment anyway and allows great flexibility there. For instance, I've today even crafted an OBS Studio script (see https://github.com/rse/obs-scripts/blob/master/production-information.lua) which creates scene meta information inside a hidden OBS Studio scene which is then also broadcasted via NDI and as a result it can be included in my OBS.Ninja participant view (which for me is actually just a screensharing of the NDI multiviewer Livemind Recorder, showing the OBS Studio Preview and Program plus this meta information plus all the ingested NDI streams).