obs-ninja-trampoline VS vingester

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.

Another consideration is, if you are usually capturing the exact same web page (like perhaps a stream elements overlay or similar) is to use Vingster.app (free and open source) which says it also works for Mac.

I use: https://vingester.app/ (free)

there is Vingester if that's something you do often but I find that I'm doing a lot of that work with a browser source inside OBS now

also don't do anything else on your computer while recording, and I'd recommend using something like (free) Vingester to make it easier to capture the window.

You could use an app like https://vingester.app/ to create an NDI stream of each page and convert those to SDI using the many Birddog/magewell/Kiloview options.

I work overlays in streaming with SPX-GC (https://github.com/TuomoKu/SPX-GC) which feeds HTML via a virtual server and read those with Vingester (https://vingester.app/), a headless browser, to NDI. There are other tools that do this for framesharing like SPOUT (https://ultralig.ht/) and pretty sure something for an apple variant (Syphon has been suspended, right?)

I found the soluction which works really, i mean - REALLY - good. On mixer side I use Vingerster https://vingester.app/ to get the video (it can emulate OBS, which i required to get data from Ninja). Vingester outputs the video to NDI and that I can get the stream to OBS on main mixing comupter. The video is flawless, no jagging.

You can also just capture the desktop-audio or use https://vingester.app/ (vingester) to capture audio/video from VDO.Ninja. Apps like Vmix and probably Manycam support VDO.Ninja, and would also I'd imagine bypass the problem, rather than using OBS directly for browser capture.

So, I've been using VDO.Ninja and Vingester to pull WebRTC live video from anyone using the Chrome Browser and into a wireframed OBS Studio environment for my live production, and it works beautifully. The issue though is I have a client that wants something more "user friendly" for guests - and they are willing to pay for it. I've been doing some research, and I see Cicso Webex a lot.

Since I first started to put together this workflow, I've been revising it to make it leaner and more robust. I wanted to share the latest iteration of this guide - one that uses the Vingester + OBS Window Capture method for my sources, as well as some great plugins I've come across.