When audio and video fall out of sync in a 24/7 recorded lesson stream, compare the lesson source, encoder output, local recording and YouTube playback before changing anything. The first copy where the mismatch appears narrows the investigation; whether it stays steady or grows over time narrows it further.
There is no single delay value or setting that fixes every setup. Keep the comparisons simple and repeatable, note what each copy shows, and change only a setting that fits the evidence. That avoids masking one fault while introducing another.
Find the first copy that is out of sync
Start with one recognisable moment in the lesson: a spoken word alongside a visible action, such as a hand tapping a desk or a slide changing as the presenter speaks. Check that moment in each available copy, in order: the lesson file or source output, the encoder preview or output, a local recording, then the YouTube stream. You do not need laboratory equipment; you need the same moment and playback conditions for each comparison.
Write down what you observe rather than relying on memory. For example: “the source looks aligned; the local recording is behind; YouTube looks the same as the local file”. That points upstream of YouTube playback. If the local file appears aligned but the YouTube copy does not, keep the source and local recording unchanged while you investigate what happens later in the chain.
YouTube’s live-stream troubleshooting guidance recommends checking the stream in the encoder, looking for audio or video problems in the local archive, and checking CPU load and encoder errors. These checks are useful because a stream preview is only one view of the broadcast, not proof that every later copy is correct.
If the problem is actually missing audio rather than a timing mismatch, use a separate fault-finding path such as this guide to a YouTube Live stream with no sound over RTMP. For a timing problem, keep audio present in every copy and focus on when its relationship to the picture changes.
Compare the lesson, encoder and local recording
The lesson file is your reference point. Play the original locally and inspect several moments across it, not just its opening. A recording may be aligned at the start but have unequal audio and video track durations or another problem later in the file. If the original lesson itself is out of sync, the encoder cannot restore a correct relationship that is not present in its input.
Next compare the encoder preview or output with the source. Check that the intended audio and video sources are selected and routed, and that the preview is showing the lesson you expect. If the preview looks wrong, inspect the source routing and encoder state before looking for a YouTube-side explanation. YouTube’s guidance also names encoder errors and CPU load as areas to check when diagnosing stream quality. Treat a warning as a clue to investigate, not proof that it caused the sync issue.
A local recording gives you another useful boundary. If it is available, play it back in a player that can show both picture and sound, and compare it with the original and encoder preview. If both the encoder output and local recording show the same mismatch, the problem is already present before YouTube playback. If the preview appears correct but the local recording is not, investigate how that recording is made and whether the recording path reflects the actual broadcast output.
Do not assume that the local file is automatically a perfect witness. It may be recorded at a different point in the chain, or its playback application may behave differently. The value comes from comparing it with the other copies and seeing which differences repeat. Keep the original file and the test recording intact so that you can return to the same passage after a change.
This staged check also prevents unnecessary purchases. A cable, microphone or capture device is not a sync remedy unless you have evidence that the relevant component or connection is where timing changes. First identify the input and output that disagree; then inspect the associated path.
Check YouTube playback and the viewer’s device
If the source, encoder output and local recording appear aligned, compare the YouTube copy. Use the Live Control Room preview and stream-health information while the broadcast is active, then review the archive if one is available. The preview can show whether the outgoing stream appears healthy, while an archive lets you revisit a passage without trying to judge timing during a live session.
Check the same passage on another device or browser if you can. A problem that follows the YouTube copy across devices suggests a different area to examine than one that appears only on a particular phone, television or browser. A viewer’s device, player, network conditions or audio-output path can affect what they experience. One viewer report is worth checking, but it does not establish that every viewer receives the same mismatch.
Keep the test controlled. Use the same passage and avoid comparing a phone playing through a Bluetooth speaker with a computer using built-in speakers and treating any difference as a YouTube ingest fault. The aim is not to prove which device is perfect; it is to learn whether the symptom follows the stream or a particular playback setup.
A YouTube archive is not a dependable sole backup for a continuous broadcast. YouTube says a live stream under 12 hours can be automatically archived, but a stream exceeding 12 hours may not be captured at all; it also recommends keeping a local archive. See YouTube’s archive guidance and verify that your own local recording is being created and can be played. This matters particularly for a 24/7 channel: do not wait for a fault to discover that the only copy you expected to review is missing.
If a playback error rather than a sync mismatch appears, the investigation changes. This guide to devotional YouTube Live playback errors covers a different symptom. Keep the reports distinct so that a viewer’s inability to play the stream does not get mistaken for audio arriving at the wrong time.
Distinguish a steady offset from growing drift
A constant offset means the audio appears early or late by roughly the same amount at different points. You might notice a syllable consistently arriving after a visible mouth movement near the beginning and again much later. That observation suggests a steady displacement, but it does not on its own identify the cause or tell you what value to enter in an encoder.
Drift means the relationship changes as playback continues. A passage near the start may appear close to aligned, while a later passage looks more noticeably displaced. That calls for checking the duration and timing behaviour of the source and each copy over time, rather than adjusting to make only the opening look right.
There is no universal visual cue, measurement threshold or correction value that applies to every player, encoder and recording route. A mouth movement, clap or slide change can help you compare, but perception and playback conditions can make a small mismatch hard to judge. If you need a precise measurement, use a method documented for your editing or encoding software and verify the result in the resulting file; do not transfer a number from another setup without evidence.
Note the passage and direction you observe in plain language: “audio slightly ahead at the opening and later passage” or “audio behind by a similar amount in both”. These are useful working notes, not a claim of precise measurement. Also record the player and device used, since the viewer setup can change what you perceive.
The distinction affects what to investigate. A steady offset is a reason to inspect alignment and routing at the stage where the mismatch first appears. Growing drift is a reason to compare longer portions and inspect timing or track-duration behaviour at that stage. Neither label is a diagnosis by itself; it tells you what to test next.
Isolate the stage where timing changes
Use the comparisons as a simple fault boundary. If the lesson source and the encoder preview are wrong in the same way, start with the lesson and its inputs. If the source is aligned but the preview is not, inspect the audio and video sources routed into the encoder and its current state. If preview and local recording agree on the mismatch, you have evidence that it is present before YouTube playback.
If the local file appears aligned but YouTube playback does not, check the Live Control Room messages, stream health and the YouTube copy on more than one viewer setup. YouTube’s live troubleshooting advice points to outbound internet as an area to inspect when encoder output looks healthy. That makes network delivery a reasonable line of investigation, not a conclusion that internet conditions caused every sync fault.
For an uploaded or archived video, there is a separate check: the audio and video tracks may have different durations. YouTube’s upload troubleshooting page says to make sure their durations are the same and to edit the tracks in video-editing software before upload if they differ. That advice is specifically about uploads. Do not treat it as a universal instruction for correcting a live stream.
Keep a short record of the setup alongside each comparison: the source file, which input is selected, where the copy was made, and what device played it. That helps you avoid changing multiple things between tests. If a change does improve one copy but makes another worse, you can identify what changed and restore the earlier state.
Make changes only when the evidence supports them
Once you know where the mismatch first appears, inspect that stage rather than changing unrelated controls. If the original lesson is wrong, correct or replace the lesson source and review it before broadcasting again. If the encoder preview is the first bad copy, inspect its audio and video routing, configuration and error messages. If the YouTube copy alone differs, use the platform’s live-health information and compare playback conditions before changing source timing.
Check the actual configuration messages in the Live Control Room. YouTube documents format and audio-setting errors, including H.264 video and AAC audio in described cases, and recommends a 44.1 kHz sample rate in certain error messages. It also says the primary and backup streams should use the same audio sample rate. These are configuration checks for the cases described by YouTube, not proof that changing a format or sample rate will repair a particular sync fault. Consult YouTube’s encoder settings and error guidance and follow the message relevant to your stream.
Make one supported change at a time, then repeat the same comparisons. Avoid stacking a source edit, encoder adjustment and playback-device change together: even if the symptom moves, you will not know which change mattered. If the encoder documentation does not explain a proposed delay or timing control for your exact setup, do not guess a value. The research available for this problem does not establish one correction procedure for every encoder.
A 24/7 broadcast also needs a reliable way to keep and inspect a copy. Verify that the local archive file is growing and that a section can be played, rather than assuming the recording exists because the stream is live. If recurring restarts or gaps are another concern, see how to loop a YouTube Live video without a gap at the restart point; that is a continuity question, separate from sync correction.
Retest with a longer segment
A short opening test can miss drift. After a justified change, compare the same opening passage and at least one later section from a longer test broadcast or recording. Include audio and movement similar to the real lesson: speech, visible gestures, and any slide or scene changes that viewers rely on. You are checking whether the relationship stays consistent, not trying to meet an invented universal threshold.
Review the encoder preview, local recording and YouTube playback again. Note whether the problem disappeared, stayed the same, changed direction or appeared in a different copy. If the change helped only at the opening but the later passage worsened, the result has not established a fix; return to the evidence and investigate the stage where the timing changes.
For a continuous channel, repeat the practical health checks during normal operation as well. Confirm that the local recording continues, inspect available stream-health messages, and revisit a later passage after the channel has run for a while. YouTube recommends a local archive backup; its automated archive limits mean that the local copy is especially important for a long-running source.
Keep a simple incident note with the date, source version, test passage, copy checked, playback device and change made. This is not a substitute for a proper technical measurement, but it keeps troubleshooting reproducible. If the fault returns overnight, you can compare the new evidence with the last known-good test instead of starting from memory.
For a channel that depends on an always-on broadcast, the operating arrangement can also determine whether your own computer must remain on and whether a local recording is easy to monitor.
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
Should I adjust audio delay first?
No. First compare the source, encoder output, local recording and YouTube playback. An adjustment made before you know which copy first goes wrong can mask the symptom or create a new mismatch elsewhere.
What if the recording is aligned but YouTube is not?
Check the Live Control Room preview and health information, then compare the YouTube copy on another device or browser. If the difference follows the YouTube copy, investigate the broadcast and delivery stages; if it appears only on one viewer setup, check that device’s playback path as well.
Why does the stream start in sync but become worse later?
That pattern is consistent with drift, but it does not identify its cause. Compare a longer segment at the source, encoder output, local recording and YouTube playback, then investigate the first copy where the relationship changes.
Can I rely on YouTube’s archive for a 24/7 stream?
No. YouTube says a stream over 12 hours may not be captured at all, and recommends keeping a local archive backup. Check that your local file is recording and playable while the channel runs.