Logitech Brio 300 A/V Sync & Latency Test

Logitech Brio 300 A/V Sync Test: Measure Audio Offset in Chrome

Measure the Brio 300 on your own USB path before relying on a generic sync value. Brio 300 is Logitech's USB-C webcam for 1080p video calls. It delivers 1080p/30fps over USB-C, and Windows can use its system UVC driver without a Logitech driver.¹ Logitech lists RightLight 2 auto light correction and a noise-reducing mic, while the support specs list fixed focus and an integrated privacy shutter.

Chrome receives the camera and microphone tracks after you grant getUserMedia permission, then this tool compares the luminance and audio transients from those local tracks.² Because Logitech does not publish an HDR or auto-framing pipeline for the Brio 300, treat it as a simple fixed-focus UVC camera rather than a camera with active processing. Measure on your machine, because host controller, browser state, and USB topology affect the actual offset.

Specifications³

Connection and browser setup

Plug the Brio 300 into a USB-C port before navigating to this page. Windows can use the system UVC driver for compliant USB video devices, so the camera can enumerate without a Logitech driver installation.⁴ Click "Enable Camera & Mic", approve the browser permission prompt, and the test starts after Chrome receives both media tracks through getUserMedia. Fixed focus means there is no autofocus hunt during the test; sit at your normal monitor-top distance for the sharpest clap detection image.

No Logi Tune configuration is needed or recommended before testing. The Brio 300 has no software-adjustable processing settings that would affect the A/V offset. This simplicity is actually an advantage for sync measurement because there are fewer variables that could shift between sessions, making the Brio 300 one of the more consistent cameras for repeated five-clap tests across different days and system states.

Fixed focus and stable working distance

The Brio 300's USB-C connector works without any Logi Tune configuration before the test. Because the camera has no auto-framing, HDR pipeline, or adjustable processing settings, there is nothing to disable before measuring. Staying at your normal working distance ensures the fixed-focus lens delivers a sharp image, which sharpens the luminance transient the clap creates and gives the detector the best possible frame-to-frame contrast for an accurate timestamp.

Common A/V sync issues with this model

Automatic exposure adjustment is the main processing step to watch with the Brio 300. In a bright room with consistent light, auto-exposure stabilizes quickly and produces clean clap detection. In a room where light changes frequently, the exposure algorithm adjusts frame-by-frame and can smooth out the luminance transient the clap creates. Clap near the camera in such conditions to maximize the luminance change detected.

Fixed focus also means the camera delivers a blurry image when you sit closer than its target distance. Blurry images reduce the sharpness of the luminance change at the clap boundary, which can cause missed detection or shift the detected transient by one frame. Sit at your normal working distance rather than leaning in, and verify that your hands are clearly visible in the video preview before starting the test so you know the detector has a sharp image to analyze.

Stable lighting for repeatable claps

Maintaining consistent room lighting throughout the test run reduces auto-exposure adjustments that change the frame brightness between claps. A window with direct sunlight shifting behind clouds during the test causes the sensor to open and close the exposure within the test window, creating inconsistent frame brightness at the clap boundary. Running the test in a room with stable artificial lighting, or with the window blinds drawn, produces five readings with tighter spread and a more reliable average.

What the test covers

Five luminance and audio transient pairs produce an averaged offset value with a direction label. The Brio 300's simplified pipeline means the five readings cluster tightly, giving you high confidence in the average even before seeing all five individually. Because the camera lacks HDR, auto-framing, and other active processing stages, the video path latency stays consistent from clap to clap, which is why the spread across five readings is typically narrower than on more feature-rich cameras.

After the test, copy the displayed OBS Audio Offset value and paste it into your streaming app's audio sync or delay control. In OBS Studio, open Advanced Audio Properties for the microphone source and use the Sync Offset field in milliseconds.⁵ In Streamlabs Desktop, open Advanced Audio Properties from the Audio Mixer when you need source-level audio controls, then verify the result with a short recording.⁶

Verifying the correction

Record a short clip after applying the offset, then play it back and confirm the clap sound arrives at the frame of visible hand impact. If the image still leads the audio, increase the audio delay; if the sound leads the image, reduce the delay and test again. Watching the clip frame by frame in a video editor gives you the most precise way to confirm alignment, since stepping through individual frames at 30fps lets you see whether the sound and motion share the same 33 ms window.

Logitech's own Brio 300 specification lists RightLight 2 automatic light correction with no HDR or auto-framing entry³, confirming there is no active per-frame processing stage to add latency beyond the basic USB video path. That puts the Brio 300 on the same minimal-processing footing as the C920x, so expect an offset close to that tight baseline rather than the wider range HDR- or AI-processing cameras in this series show.

Before you stream, record the clip under the conditions you actually use and keep the same working distance the fixed-focus lens needs. The Brio 300's narrow five-reading spread means a single corrected clip should match the average closely, but only if the same USB port, microphone source, and browser stay in place. OBS Studio and Streamlabs Desktop both expose the Sync Offset field in milliseconds, so enter the captured value in whichever app applies the correction. If the clip shows the sound and motion sharing that 33 ms window, the correction is holding. Start your session with confidence.