If OBS audio distorts or clicks each time a video repeats, first find out whether the sound is clipping from excessive level or is a brief click at the loop seam. Those are different problems: lower and control the mixed audio level for clipping, but inspect the media file’s beginning and end for a seam click.
A loop setting only repeats playback; it does not manage audio peaks or guarantee a seamless transition. Before changing Sync Offset, establish whether audio and picture are already out of time in OBS’s local output, or whether the apparent mismatch is only in the YouTube Live playback chain.
Identify where the problem occurs
Start by describing the symptom rather than changing settings. Clipping usually sounds like harsh distortion on loud material. A seam click is more often a short tick, pop, or abrupt change at exactly the same point each time the clip restarts. A sync problem means speech or another identifiable sound no longer lines up with the corresponding picture. These can happen together, but one does not prove the others.
Check whether the problem occurs on every repeat and whether it is tied to a particular loud moment or to the exact end of the file. If distortion appears during a loud chorus as well as at other points, investigate level. If there is a click only at the boundary while the rest of the programme sounds clean, investigate the file’s transition. If a mouth movement and spoken word drift apart throughout the clip, investigate timing separately.
The first useful comparison is between OBS’s local output and the viewer’s YouTube playback. Make a short recording or local output test from the intended OBS scene and listen while watching it. If the same mismatch is present there, the problem is already in the source, scene, or OBS processing path. If the local recording is aligned but the YouTube player seems different, do not assume an OBS source timing fault: YouTube’s ingest and playback introduce a separate delivery path.
A local recording is a diagnostic check, not proof that every viewer will hear or see the same result. Use the same scene, source order, filters, and audio routing you intend to stream. Avoid comparing a clean source-file player on your desktop with a browser view of the live stream; they are not the same chain.
Determine whether audio leads or lags
Before touching Sync Offset, identify the direction of the mismatch and where it occurs. Use a clear event with a visible and audible start, such as a spoken consonant, hand clap, or a sharp musical hit. A continuous background bed is a poor reference because it may have no visible event to compare.
In a local OBS recording, note whether the sound happens before the visible event or after it. Repeat the check at more than one point in the clip. If the error is similar at the beginning and end, it may be a fixed timing displacement. If it grows over the duration, suspect a rate or media timing mismatch rather than trying to compensate with one fixed offset. Do not diagnose direction by asking whether the sound feels “late” on an internet-delayed YouTube player alone.
Keep a simple note: test location, reference event, audio-leading or audio-lagging, whether the error stays constant, and whether it appears locally or only on YouTube. This prevents a common cycle of applying an offset, seeing one event improve, and making other events worse. If the sound is only a click at each restart and identifiable audio remains aligned with the picture, Sync Offset is not the right first control.
For a full production checklist around source material, the article on organising recorded lessons for a 24/7 stream is useful when several files form one scheduled or repeating channel. The same principle applies to music, news loops, and ambience: know which clip is playing and where its intended boundary falls before adjusting output timing.
Use OBS audio Sync Offset carefully
OBS audio Sync Offset delays an audio source relative to video in the OBS mix. It is a timing adjustment, not a loudness control, a limiter, or a repair for an abrupt loop seam. Its direction and result must be judged in the actual scene, because sources may be combined and may already have processing or delay elsewhere in the path.
Only test an offset after a local OBS recording demonstrates a consistent lead or lag. Change one relevant source at a time, record again, and compare the same reference event. If the error is not consistent, or if you have not established which way it goes, leave the offset alone. There is no universal value that can be recommended for an unspecified video, audio source, codec, scene, and playback chain.
Also check that you are not correcting the same delay twice. A source may have a filter, a device path, or another timing adjustment applied before it reaches the final mix. If you add an OBS offset to counter a delay that is already compensated elsewhere, the local recording may become misaligned in the opposite direction. Keep a record of the original setting and undo a test that does not improve the same event in a repeatable way.
If you use OBS for both recording and streaming, separate those checks. The OBS audio mixer technical details explain how the mixer’s input meter relates to source filters and the volume fader. A meter reading for an individual source is not a substitute for checking the final output mix, where multiple sounds can add together.
Test the actual source chain
For one repeating video, use an OBS Media Source and enable Loop. For a playlist, OBS’s VLC Video source supports Loop Playlist; it depends on VLC being installed, and the OBS guidance notes that a 64-bit OBS installation needs 64-bit VLC. OBS’s media source guide describes these playback controls. Choose the source type that matches the job rather than building a playlist out of rapid scene visibility changes.
Looping and clipping are separate controls. Loop tells OBS to repeat media; it does not keep the signal below the digital ceiling and does not promise that the audio samples at the end of the file transition smoothly to the samples at the beginning. The source format, its encoded timing, and the editing of the beginning and end all matter to what you hear at the boundary.
Test the source in the actual scene with its intended filters and other audio. Play the loudest passage, then listen to at least one repeat boundary. Watch the relevant source meter and the final mix meter while you listen. If there is a loud sound under music, voice, or another clip, the combined mix may peak higher than any one component on its own.
A useful test recording captures OBS’s intended output rather than just playing the file in a separate media player. The latter can help you inspect the source file, but it cannot tell you how OBS’s scene composition and filters affect the final mix. For more context on choosing a playback method, see free software for looping a playlist on YouTube Live; whatever source you choose, test the exact scene that will run.
Understand YouTube Live latency separately
YouTube Live latency is the time between OBS sending a programme and a viewer seeing or hearing it. It is not automatically the same as an audio-to-video mismatch inside the programme. A viewer may be behind the broadcaster’s live view while the audio and picture remain aligned with each other. Delaying audio in OBS to make one browser appear to catch up can put the programme out of sync for other viewers.
Check the local OBS recording first, then examine the YouTube playback using the same recognisable event. Make sure you are comparing the live stream with its own picture, rather than with a clock, an external player, or another device that is on a different delay. Browser buffering and the viewer’s connection can affect when the player presents the stream; do not infer the cause from the apparent delay alone.
If the audio and picture are aligned locally but the YouTube player behaves differently, keep the OBS offset unchanged while you investigate the live playback experience. Consult YouTube’s current live streaming latency guidance for the available latency choices and their trade-offs. Do not assume a latency setting fixes an OBS source timing issue, or that a particular setting is suitable for every channel.
This distinction matters for a 24/7 channel because viewers may join at different moments and use different playback conditions. A one-time comparison against your own browser is evidence about that playback, not a universal measurement of what every viewer receives. If you are also troubleshooting reconnect behaviour, keep it separate from audio timing; the guide to automatic OBS reconnection to YouTube Live on Windows covers a different failure mode.
Control peaks without confusing them with a seam click
OBS describes clipping as audio exceeding 0 dBFS in the recorded or streamed output. Start by lowering the source or sources that make the mix too loud, then listen again to the loudest part. This preserves more headroom than relying on a safety filter to repair a mix that is routinely too hot.
A Limiter can act as a ceiling against peaks that would otherwise cause clipping or distortion. OBS’s Limiter filter documentation says to place it last in the filter chain. That order matters: processing after the limiter could raise the signal again. OBS lists default threshold and release values in its guide, but defaults are not a universal target for every programme or mix.
The Limiter is for excessive peaks, not for repairing a click caused by an abrupt edit. A brief transient may still be audible even when it remains below the ceiling, and applying aggressive level control can alter the programme without fixing the discontinuity. Use the meter as one clue, then listen to the local recording at the repeat point.
If the final output is clean except for a recurring boundary click, inspect the media’s waveform and audio at the beginning and end in an editor suited to the file. The needed repair depends on the material and how the file was created; the available OBS documentation does not establish a universal crossfade duration or editing recipe. Make a revised test file, replace the source, and listen to multiple repeat boundaries before using it in a long-running broadcast.
Recheck after each change
Change one thing at a time. If you lower a source, add a Limiter, alter an offset, and edit the media all at once, you will not know which change addressed the symptom. Keep a copy of the original source and note the relevant OBS settings before testing, especially if the scene is already part of a live channel.
For a level problem, test the loudest section and the final mix after the gain change. For a seam click, test the exact boundary after replacing or editing the clip. For a sync issue, use the same visual-audio reference event in a local recording before and after any offset change. Then check the YouTube playback separately if that is where the reported issue occurs.
A short recording is a practical verification step, not a guarantee of what a long stream will do under every condition. Listen with headphones or speakers you know well, and avoid judging only from a tiny preview or a phone speaker that may conceal a brief artifact. If you change media encoding or replace a file, repeat the test: a new export can change timing or boundary behaviour.
If you operate a channel from a personal computer and the recurring job is the playback itself, keeping the file and scene ready is only part of the workload. StreamNeo can remove the need to leave your own computer running for an uploaded video stream, but it does not change the need to check that the source audio is clean and properly prepared.
Avoid assuming one offset fits every clip
A fixed Sync Offset may help a consistent, measured mismatch in one source chain, but clips can differ in their audio and video timing, start points, and edits. A playlist may also mix files prepared in different ways. An offset that makes one clip look right can make another worse, so test each distinct source and transition rather than copying a value from someone else’s setup.
If the mismatch changes over the length of a clip, do not keep increasing a fixed offset in the hope that one end will line up. Check whether the file itself has a timing problem and whether the mismatch exists in the local recording. If it occurs only at the loop boundary, investigate the seam. If the levels cross the ceiling, address level. If only the YouTube player’s delivery appears different, investigate latency separately.
The practical order is diagnosis, then a small controlled test, then verification. First classify the sound as overload, seam discontinuity, or timing mismatch. Next locate it in the OBS output or YouTube playback. Only then adjust the control that corresponds to the cause, and recheck using the same material. That sequence is slower than guessing once, but it avoids turning one ambiguous symptom into several new problems.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is a click at the loop point the same as audio clipping?
Not necessarily. Clipping is distortion caused by the output level exceeding the digital ceiling, while a click can come from an abrupt audio transition at the file boundary. If the click repeats at precisely the boundary and the mix remains below the ceiling, inspect the source seam rather than starting with a limiter or Sync Offset.
Should I use Sync Offset to fix audio that seems late on YouTube?
Only after a local OBS recording shows a consistent audio-to-picture mismatch and you have established which way it goes. YouTube Live playback has its own delivery latency, so an apparent delay in a browser does not by itself establish that OBS needs an offset. Check YouTube’s current guidance before changing latency choices.
Does enabling Loop make the audio transition seamlessly?
Loop makes the media repeat; it does not guarantee a gapless or click-free audio seam. Listen to the actual source in the intended OBS scene, and inspect the file if the artifact happens at the same point on each repeat. OBS’s media source documentation explains the loop controls but does not promise a seamless transition for every file.
Where should the Limiter go in an OBS filter chain?
OBS says the Limiter should be the last filter in its chain. Lower an overly loud source first, then use the Limiter as protection against peaks and recheck the final mixed output. A Limiter does not replace editing a defective loop boundary.