Logitech Brio 500 A/V Sync & Latency Test

Logitech Brio 500 A/V Sync Test: Measure Audio Offset for OBS and Zoom

For a Brio 500, the important sync number is the one measured on your desk, not the marketing latency figure. Brio 500 is a Full HD 1080p USB-C webcam with RightLight 4 HDR, RightSight auto-framing, and Show Mode.¹ Connect it to a USB-C port, grant camera and microphone access in Chrome, and the clap test starts after the browser receives both media tracks through getUserMedia.²

Logi Tune can customize Brio 500 settings, including AI-optimized framing, so disable RightSight before testing if you want a fixed framing state across all five clap readings.³ Measure on your specific machine because Windows audio buffers and driver settings can change capture timing; driver versions and USB topology affect the actual offset more than a published camera figure.

The measured offset still depends on the host controller, operating system, and browser state, so use your five-clap result rather than a generic published figure. When the result says Audio Delay, enter the positive value in OBS Studio's microphone Sync Offset field to delay the audio until it matches the video frame.

Specifications¹

Connection and browser setup

Connect the Brio 500 via USB-C before opening this page. If your machine lacks a USB-C port, the included USB-C to USB-A adapter can still provide basic plug-and-play camera access, but moving the camera to a different USB topology can change available bandwidth and timing.⁴ Chrome recognizes the camera after you grant the getUserMedia permission; no Logitech software installation is needed for basic camera access.

Disabling RightSight auto-framing before testing produces more consistent results. Open Logi Tune, navigate to the Brio 500 camera settings, and toggle RightSight off. With auto-framing disabled, the camera delivers a fixed framing state instead of changing the crop while it detects and tracks your face. Leaving RightSight active during the test can cause the camera to reframe between claps, which changes the luminance distribution in each frame and makes the detector work harder to find a clean transient.

Stabilizing Logi Tune and framing settings

Set the Brio 500 to the same framing state before every test. If you use Show Mode, HDR, or a custom Logi Tune preset, keep that preset active during all five claps. Switching presets after the test can change processing time and make the saved OBS value less reliable for the setup you actually used. Keeping a written note of the active preset alongside the measured offset helps you reproduce the same conditions when you re-enter the value in OBS after a session break.

Verifying camera permissions in Windows 11

If the Brio 500 does not appear in the video input dropdown after clicking Enable Camera and Mic, check both browser permissions and OS-level permissions. Windows 11's Privacy and Security settings include separate camera permission toggles for apps and for browsers; if the browser-level toggle is off, Chrome cannot enumerate any webcam regardless of its internal permission status.⁵ Open Settings > Privacy and Security > Camera on Windows 11 and confirm that browser-level camera access is on before reloading the page and trying again.

Common A/V sync issues with this model

Windows audio latency depends on the driver and buffer configuration, so a Windows or webcam driver update can change the audio side of your Brio 500 measurement.⁶ If you measured the Brio 500 before a major OS or driver update and entered that value in OBS, re-measure now. A changed audio buffer path can shift the apparent offset even when the camera hardware has not changed.

RightSight active is the second common issue. When enabled, RightSight changes the active framing state while it detects and tracks your face. This can make individual clap readings spread further apart across five tests because the camera crop shifts between claps, altering the luminance baseline the detector uses for each measurement. Disable it in Logi Tune and retest if your five measurements show more than 25 ms spread, and wait three seconds after disabling before starting the test so the camera fully settles into its fixed framing state.

Run the five-clap test after any major Windows update to confirm the offset has not shifted. Keep the same USB port, same microphone, same Logi Tune settings, and same browser between measurements so the result reflects the setup you are about to use for recording or streaming. Treat the measured offset as a snapshot of your current configuration rather than a permanent property of the camera alone, and rerun the test after any system change that might touch the audio or video path.

Logitech's own webcam comparison chart lists RightSight auto-framing and HDR as standard on the Brio 500, features the simpler Brio 300 in the same lineup does not carry.⁷ That extra per-frame processing is consistent with the Brio 500 typically reading higher than a minimal-processing camera like the C920x.

What the test covers

Inside the browser, the tool samples the video frame canvas for a luminance spike and the Web Audio AnalyserNode for a transient above the calibrated noise floor. Both use the same performance.now() clock, which is a high-resolution monotonic timer that is not subject to system clock adjustments. Five paired timestamps produce an averaged offset with direction, and the five-reading design helps cancel out any single-frame timing anomaly caused by a momentary CPU spike or USB scheduling delay.

For the Brio 500, the offset direction is almost always positive (Audio Delay), because video processing runs longer than audio. Building on this, the result panel displays an OBS-ready value labeled "OBS Audio Offset". Enter that number in OBS Studio under Edit > Advanced Audio Properties > Sync Offset (ms) for your microphone source. Logi Tune and the Windows Camera app do not expose a sync offset control, so OBS or Streamlabs is where the correction must be applied. The Brio 500's RightLight 4 HDR pipeline adds more in-camera processing than the older C920x, which is why the measured offset tends to be slightly higher on the same USB port and microphone combination.

Confirming the offset in a test clip

After entering the OBS Audio Offset value, record a 10-second test clip and clap once clearly in front of the camera. The clap sound should align with the frame where your hands visibly contact. Brio 500 recordings corrected with the measured offset typically show alignment within one or two frames at 30fps, which is 33–67 ms of residual error and below the perceptible threshold for passive viewers. If the sound arrives noticeably before or after the visible clap in the test clip, adjust the OBS Sync Offset by 10 ms in either direction and record again.

During the test clip, match the conditions to your real session and account for the Brio 500's HDR processing lag. Keep the same USB port, microphone, and Logi Tune preset you used for the measurement, because the Brio 500's extra in-camera HDR processing makes the offset sensitive to those choices. A positive result means Audio Delay, so the value you entered pushes audio later until it meets the frame. If viewers still notice a gap after the first correction, nudge the Sync Offset another 10 ms and re-record until the clap lines up.