For an OBS-based YouTube Live stream, add the long ASMR video as a Media Source and enable Loop in that source’s properties. To investigate audio that plays twice, check that the file reaches your stream through one intended OBS audio path, then listen to the end-to-start transition in a test stream.
YouTube’s viewer Loop control repeats playback for someone watching a video; it does not tell a live encoder to replay its input. Looping the file in OBS and isolating its audio are separate tasks, and neither a particular setting nor a short test guarantees that every cause of duplicate sound has been found.
Add the long video as an OBS Media Source
In OBS, select the scene that will carry the ASMR stream and add a Media Source. Give it a recognisable name, such as ASMR long video, so you can identify it in the Sources list and audio mixer later. In its properties, choose the intended video file. OBS documents the Media Source as a way to play media files, including video and audio, within a scene. Its Media Sources guide describes the available controls; names and layout can vary between installed versions, so look for the property name rather than relying on a particular screen arrangement.
Make sure the source is visible in the scene and that the image fits the output canvas. A black screen or a cropped picture is a separate problem from audio routing, but it is easier to diagnose both while the source is visible in preview. If you have a collection of separate recordings rather than one long file, the setup may differ; for that case, a playlist approach for multiple videos may be a more relevant starting point.
Use a local copy of the file that you intend to broadcast, rather than relying on a browser tab or a player window as the source. A Media Source gives you a defined source to inspect and control inside OBS. Before changing audio settings, play the file and confirm that its picture and sound appear as expected in OBS preview. If the file itself has silence, overlapping tracks or an abrupt edit, those characteristics will remain relevant when it repeats.
Enable Loop for repeat playback
Open the Media Source properties and enable Loop. OBS describes this property as specifying whether the file plays again after playback has completed. With it enabled, the source is configured to repeat the file at the encoder side; it is not a viewer preference on YouTube.
Do not confuse Loop with Restart playback when source becomes active. OBS describes the latter as restarting the file when the source is in the current scene and visible. That can be useful when a source should begin at the start as it becomes active, but it is not the setting that makes a file repeat on completion. Decide whether you need that scene-activation behaviour separately. If you switch scenes during a broadcast, test what happens when you return to the Media Source instead of assuming it will resume or restart in the way you prefer.
After enabling Loop, play the source long enough to confirm that the control is active and the file starts correctly. If the file is very long, you do not need to wait for its natural end merely to inspect the setting, but you do need to check the actual boundary before relying on it for a continuous channel. A prerecorded stream buffering checklist may help if the broadcast has network interruptions; buffering and repeated source playback are different issues and should not be treated as the same fault.
OBS Loop and YouTube Loop do different jobs
There are two controls that can be described casually as “loop”, but they act in different places:
| Control | Where it acts | What it repeats | What it does not do |
|---|---|---|---|
| OBS Media Source Loop | In the encoder scene | The selected media file after playback completes | It does not diagnose overlapping audio paths or repair an audible edit in the file |
| YouTube viewer Loop | On a viewer’s YouTube watch screen | Playback for that viewer | It does not configure OBS or make a live encoder replay a file |
YouTube’s viewer Loop help page explains the watch-screen control. A person watching your live broadcast cannot use that control to change what your encoder sends. For a prerecorded source in OBS, repetition belongs in the source’s own properties.
A second distinction is what gets restarted. Loop repeats after the file completes; Restart playback when source becomes active is about the source becoming active in a visible scene. You may choose either or both according to how your scenes behave, but one should not be used as a substitute for understanding the other. If you are unsure which behaviour you have configured, check the property names in the installed OBS version and test a scene switch before going live.
Route the file audio through one intended source path
When the audio seems doubled, first map how the file’s sound could reach the stream. A Media Source can carry its own audio into OBS. Separately, desktop or application capture may also pick up the same sound while the file plays. If both routes are active and included in the output, the audience may hear the signal twice or hear it with an echo-like offset. This is a troubleshooting possibility, not a diagnosis: other causes can include a source or monitoring arrangement, the recording itself, or a separate stream-side issue.
Start with the OBS audio mixer while the Media Source is playing. Identify the meter associated with the media and the meters for desktop or application capture. If moving or muting one source changes the same file sound, note that before adjusting anything. Choose one intended path for the recording’s audio, then check that another active capture path is not carrying that same sound into the programme as well. Keep unrelated audio, such as a microphone or a separate background track, distinct in your reasoning; the aim is not to mute every source, but to avoid sending this file through two paths unintentionally.
OBS’s Media Source properties include audio-related controls, but the documentation does not promise a single switch that resolves every duplicate-audio case. Change one routing choice at a time, then listen again. If you mute desktop capture and the apparent doubling stops, that is useful evidence about the route; it does not establish that desktop capture is always the cause. If it continues, restore only the sources you need and investigate the other active paths rather than stacking additional filters or settings without a clear reason.
For a channel that will run unattended, write down which source is meant to carry the file audio and which sources are not. This makes a later scene edit less likely to reintroduce a second path unnoticed. It is also useful if another person helps operate the channel. Keep a clean working scene or copy before making substantial changes, so you can compare the altered routing with the original if the result is worse.
Check desktop and application audio capture
Desktop audio capture can be convenient when you want all computer output, but it can also collect the same video sound already carried by the Media Source. Application capture can create a similar overlap if it is pointed at the player or software producing the file’s sound. Inspect the sources actually present in the streaming scene, not just what you remember adding. A source may remain active even when you are not looking at its settings.
Use a controlled check. Start playback, watch the relevant mixer meters, and mute one capture path briefly while listening to the OBS preview. If the Media Source meter continues to move and the programme still contains the file sound, that path may be sufficient for the recording. If muting it removes other sound you need, record that trade-off and choose a routing arrangement that preserves the intended material without capturing the file twice. Avoid changing several sources at once: doing so can conceal which change made a difference.
If you use headphones for monitoring, remember that hearing the sound in your headphones does not by itself prove that the audience receives one copy. Monitoring and the programme output are not always the same path. Confirm the mixer state and make a short recording or test stream that you can listen to independently. YouTube’s live streaming tips advise monitoring stream audio and video quality; treat a local preview as an early check, not a substitute for checking what reaches YouTube.
If the file plays twice only at the loop boundary, do not assume desktop audio is the cause. The file may contain a duplicated sound or the edit may have a pause, overlap or abrupt change. Compare the OBS preview and the received test stream around the same boundary. Isolating the source path helps narrow the possibilities, but it cannot make an imperfect recording seamless.
Preview the end-to-start transition
A file can loop correctly as a playback control and still sound awkward at its seam. ASMR often makes small changes noticeable: a room tone can drop away, a breath can be cut off, or the opening ambience can arrive over the final sound. The loop setting repeats the file; it does not edit its ending or create a crossfade. The official OBS documentation describes the repeat property, not a guaranteed seamless-loop method.
To inspect the boundary, move playback near the final seconds and listen through the end and the beginning that follows. If the source does not offer convenient seeking in your setup, make a short working copy or use a separate preview method that lets you hear those two portions consecutively. Do not alter the only original without keeping a recoverable copy. Listen at the same level you expect to use on stream, because a transition that seems acceptable at a very low preview level may be distracting at normal listening volume.
If the seam contains a click, a sudden silence or two sounds colliding, locate whether it is present in the file itself or appears only in the OBS programme. A short local recording can help separate those cases. If the source recording needs an edit, correct the media before relying on the loop; if the doubling appears only in OBS, return to the routing checks. There is no universal OBS setting that guarantees a smooth transition for every recording.
Also check picture continuity. A black frame or a visibly different camera angle at the restart may make the repetition obvious even when the audio is acceptable. If your stream uses several scenes or transitions, test the Media Source in the full scene arrangement. Advice on OBS scene transitions for a continuous channel is relevant when scene changes, rather than the file seam alone, shape what viewers see and hear.
Test and monitor the stream
Before a public broadcast, make a test stream and listen to the received output, not only the local OBS preview. YouTube recommends test streaming and monitoring stream quality. Use an appropriate private or unlisted option if available for your channel and test purpose, and confirm the current controls in YouTube Studio. Check that the picture is present, the sound is at a usable level, and the boundary does not bring back a second copy. A test can reveal a problem; it cannot guarantee that a long unattended run will never encounter a different one.
Inspect the stream in YouTube Studio’s Live Control Room and verify that the intended stream is receiving audio and video. Keep your stream key private: it functions as a credential for sending a broadcast to your channel. YouTube’s encoder streaming setup guidance covers the encoder workflow; use the current Studio interface and help rather than relying on an old screenshot. If you want a broader measure of what viewers experience after going live, the guide to measuring YouTube Live performance can help you distinguish stream quality checks from audience metrics.
During the test, listen across the end-to-start point more than once if the file permits, and compare what you hear with the local source. Check the audio mixer for unexpected activity as well as listening for an echo or an apparent second layer. If you hear doubling, change one path or source setting at a time and repeat the test. Record what you changed; otherwise, it becomes difficult to tell whether a later improvement came from a real fix or a coincidental difference.
For an always-on channel, consider what happens after the test as well: who will notice a problem, how you will stop or replace a bad source, and whether the file remains accessible to the setup. If you run OBS on a computer, the stream depends on that computer and its session staying available. If the recurring burden is leaving a personal computer running to replay a prepared file, StreamNeo can remove that particular burden by taking an uploaded video and running it as a 24/7 YouTube Live stream without your computer switched on. That does not remove the need to check the recording, audio routing assumptions or YouTube’s current requirements before broadcasting.
Check that you have the rights needed for the sound and visuals in the file. YouTube says live streams are scanned for third-party content and may be interrupted when matches are identified; its copyright guidance for live streams explains the issue. A license or permission for third-party material does not mean a stream will never be interrupted, so check the current official guidance and any applicable rights-owner requirements before going live.
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
Does YouTube’s Loop button make my ASMR live stream repeat?
No. YouTube’s viewer Loop control repeats playback for the person watching a video on YouTube; it does not configure an encoder. To repeat a file sent from OBS, enable Loop on the OBS Media Source.
Why does the audio seem to play twice?
One possibility is that the Media Source audio and desktop or application capture both include the same file sound. Check the active mixer paths and test one change at a time, but do not assume that this is the cause in every case. The recording itself or another audio route may also be involved.
Does OBS Loop make the end and beginning sound seamless?
No setting described here guarantees a seamless boundary. Listen to the final seconds and opening seconds together, and edit the source file if its transition has a pause, overlap or abrupt cut. Then check the result in a test stream.
Is YouTube’s DVR limit a limit on how long OBS can loop?
No. YouTube’s DVR information concerns viewer controls such as rewinding or pausing a live stream, not the repeat behaviour of an OBS Media Source. Check YouTube’s current help for DVR availability on long streams, and treat that as separate from configuring the file loop.