&effects
to the guest invite URL. https://obs.ninja/?effects=3
(bokeh blur)https://obs.ninja/?effects=4
(greenscreen)https://obs.ninja/?effects=5
(image; guest can select an image on joining; a sunset image is used by default)chrome://flags/
if you'd like to see a large reduction in CPU load when using this feature.&effects
to pick on startup.&activespeaker
(or &sas
or &speakerview
)&broadcast&webp
URL parameter to the guest links.
ie:) https://vdo.ninja/?room=xxx123&broadcast&webp
(The director just needs to go live with their camera after that.)&webpquality
(&webpq
or &wq
) can adjust the quality, where you can pass a value from 0 to 5. You add this parameter to the director (or designated broadcaster) and it then sets the the quality target for the &webp
mode. 5 (default) = 270p @ ~15fps ; 4 = ~30fps, 3 = ~50fps, 2 = 360p, 1 = 720p, 0 = 1080p.
/list
/msg 25e HellllOOo
&broadcast
mode.&showlist=1
will force show it and &showlist=0
will force hide it.&videobitrate=
command of course forces Chrome to test much higher. I suppose you could use this value to get an estimate on what the total bandwidth of a connection is, and then you'd be best served keep the &videobitrate
target to be no more than 80% of that.&minipreview
option by default, with the slight twist; the guest will see themselves full screen if the broadcast hasn't started yet. &nopreview
can disable it and &minipreview
can force always-pip for the preview. &broadcast
option.&outboundaudiobitrate
or &oab
, along with &outboundvideobitrate
or &ovb
.&stereo=1
or &ab=200
), it will override the publisher's &oab
parameter.&ovb
is similar, except if set it sets the viewer's bitrate and overrides the &videobitrate
parameter. It won't override the room's total bitrate parameter, as that's a dynamically set bitrate, so to get higher bitrate in group rooms you still need to use &trb
.&broadcast
situation, where guest to guest you might want to have a different audio bitrate versus the director's audio bitrate output.&css
parameter. You can stylize VDO.Ninja without needing to host anything more than a CSS file.https://vdo.ninja/?css=https%3A%2F%2Fs10.fun%2Fmain.css
&scenetype
(aka, &type
). This is replacing &scene=2
with &scenetype=2
. &scenetype=2
just shows the last guest that was added in the scene; it does a basic mute of the last guest also. &scenetype=1
does the same thing, but doesn't mute. It's not super sophisticated logic, but it should work in a pinch.&scene=5
, etc). You must manually create scene links for OBS to use these extended scene options, as links for &scene=0
and &scene=1
are the only ones provided by default still. You can use these added scene links to create dedicated "slots" for guests in an OBS layout. &scene=2
or greater, for performance reasons, videos won't load immediately in the background when the scene becomes active; only once the video has been added to the scene will the video stream be loaded. Videos will still preload however if using &scene=1
, (up to 500kbps anyways). This is a required performance optimization, imo, and it shouldn't impact existing use cases of VDO.Ninja.&pcm
or w/e) the inbound audio bitrate will be at 256-kbps (regardless of video bitrate).&transparent
will make the Director's room even more transparent now, for better or worse.&vd=xxx
/ &ad=yyy
.&showdirector
as a director, you will now appear as a performer kind of like other performers. Add/remove from scene, highlight, record, order, and the solo-link is easy to access.&beep
will now go off for the director each time a guest joins the room (with audio/video tracks added).&scene=1
+ highlight state synced).CTRL
(plus state is correct after director reloads)&outputdevice
value for URL-based audio output device selection.&optimize=0
will disable video tracks (video bitrate=0) when the video track is not in an active OBS Scene&nvb
or &novideobutton
hides the video button for guests (unable to mute their video); &nmb
and &nomicbutton
also added.&noremb
command, which deletes the flag for Google' bandwidth estimation tool. Doesn't seem to do much though.&micdelay={milliseconds}
parameter, which is guest-side, and delays the microphone by specified time in milliseconds. alias &delay
and &md
. I already had a &audiolatency=
parameter, but that used a buffer-node and not a delay node. I am finding the buffer node to cause clicking, and the delay node does not. This is also not the same as the &sync
or &buffer
commands, as those are viewer-side delays.&nonacks
, &codec=red
, &codec=fec
, and &nopli
have been added as a viewer-side parameters. They don't seem to do much it seems, but for advanced webRTC testing, they can maybe help override default webRTC behaviors, like potentially some bitrate throttling.&pip
on the view side will force the system-based PIP to trigger on the first video that loads. This was a user request.&maxframerate
(&mfps
or &mfr
) , which is like &framerate
, except it will allow for lower frame rates if the specific frame rate requested failed. Happy to add more options here, or to make the &framerate=XX
option not fail (but go up or down), but i think the feedback that a frame rate isn't supported is helpful. You will still get an error if the only supported frame rate is higher than the specified frame rate; with either URL.&ptz
, which can be added to a push link, which enables the pan/tilt control of the camera, if compatible. This will trigger a new permission popup though (Chrome only).&cleanish
and &record
, you'll get the Record button showing, but nothing else.&tcp
as a flag will force TCP mode if connected to a TURN server, versus the default, which may be UDP or TCP. &mini
or &minipreview
will enable it. Auto-forces the preview on.&remote=privateKey
allows for sharing of stats with remote connections; privateKey value is optional.monitor.html
page.&sid=xxx
or &view=xxx
, as view might be more familiar, but you're not really viewing a video -- hence sid. (stream ID)&room=ROOMNAME
; same with the password.
https://vdo.ninja/speedtest?sid=xxxxxxx
https://vdo.ninja/monitor?sid=xxxxxxx
or for a direct link:
https://vdo.ninja/?push=xxxxxxx&remote=privateKey
https://vdo.ninja/monitor?sid=xxxxxxx&remote=privateKey