&vred
Asks WebRTC negotiation to prefer video RED right after the chosen video codec
Viewer-Side Option! (&view, &scene, &room)
Options
Example: &codec=vp8&vred
(no value)
Prefer video RED during negotiation
There is no default; without &vred, codec order is left alone.
Details
&vred reorders the video codec list in the session description so the requested codec comes first and video/red comes right after it, when the browser offers RED.
On a viewer link, it only takes effect together with &codec, because VDO.Ninja reorders codecs only when a codec is requested. On a publisher using &meshcast or &whipout, it also applies to the outgoing WHIP offer.
Start with VP8. Chromium can disable the RED/ULPFEC combination in some cases, such as H.264 with NACK enabled.
https://vdo.ninja/?view=STREAMID&codec=vp8&vred&buffer=500What it does not do
It does not force a FEC percentage or parity rate, and does not guarantee repair packets are sent.
VDO.Ninja has no URL parameter that forces browser video FEC on normal WebRTC video.
It does not configure the Ninja OBS Plugin publisher, which does not offer video RED, ULPFEC or FlexFEC. That plugin's Packet Duplication setting is separate and is not turned on by
&vredor&pvred.
If you need VDO.Ninja-controlled parity, use the chunked (WebCodecs) path instead. It adds buffering:
&chunkfec=4 sends one parity payload per four data chunks.
Bandwidth
&vred adds no fixed overhead. If the browser sends repair data, it comes out of the same uplink budget as the video. On a tight link, that can make congestion worse. Pair RED tests with a lower bitrate and some headroom, for example &videobitrate=2500&maxbandwidth=60 on the viewer, or &outboundvideobitrate=2500&maxvideobitrate=2500&maxbandwidth=60 on the publisher.
When to use it
Try &codec=vp8&vred when the stream has short, random packet loss, round-trip time is not extreme, and there is bitrate headroom. Always compare against the same link without &vred.
For other problems, use other controls:
Jitter or reordering
Smeared video that lingers after a dropout
&keyframe=3000; avoid very frequent keyframes
Motion breaking up under bandwidth pressure
°rade=maintain-framerate
Screen sharing or text
°rade=maintain-resolution
Burst loss, cellular handoffs or multi-second outages
&chunked, SRT, RTMP, or WHIP/WHEP with an SFU
Audio dropouts
&audiocodec=red
Do not add &nonack, &nopli or &noremb for reliability. They remove the feedback WebRTC uses to recover and adapt.
How to test
Compare the same stream with and without
&vred, keeping codec and bitrate fixed.Open
chrome://webrtc-internals(Chrome) orabout:webrtc(Firefox).Check the negotiated video codec and payloads.
Compare bitrate, packet loss, NACK count, freezes, keyframes and picture stability.
Browser support for RED varies. Check the target browser, including older OBS Browser Source versions, before relying on it.
Related
&pvred
Publisher
Prefer video RED in the publisher's own codec ordering
&prefervideocodec=vp8
Publisher
Preferred video codec for viewers
&redaudio, &fecaudio, &predaudio, &pfecaudio
Viewer / publisher
Experimental audio RED/FEC ordering
&chunkfec, &chunknack
Chunked publisher / viewer
VDO.Ninja-controlled parity and retransmission
Last updated
Was this helpful?