Input Browser Webcam

How it fits

Typical backends

Caveats

• CompatibilityBrowsers only grant camera and microphone access over HTTPS in production (localhost is exempt for development); without TLS the browser silently refuses permission and no frames arrive.
• Hard constraintwith_video and with_audio gate the two outputs independently, and any enabled output that is left unconsumed back-pressures the component, so wire every output whose gate is on.
• Accuracyfps and frame_size are negotiation hints the browser may silently downgrade to what the device supports, and permission denial yields no frames without an error.
• Parameter interactionaudio_frame_ms at the sentinel forwards each underlying WebRTC audio callback as its own frame, while a positive value accumulates audio into fixed-size chunks; drop_frames discards frames under back-pressure instead of blocking, which matters under network jitter.
• Compatibilitywebrtc_port_range pins the local UDP ports used for connection setup; leaving it unset lets the system choose, which can fail behind restrictive firewalls.
• State lifetimeOnly drop_frames takes effect at runtime; the other knobs apply on the next browser session.