A Windows scheduled task can launch OBS or another encoder at a chosen time, while the encoder repeats a video file and sends it to YouTube Live. It does not, by itself, guarantee that YouTube will make the broadcast public or that a failed stream will recover.
An external SSD can supply OBS with a local media file, but it is only the file source: the computer still reads and plays the video, encodes it, and sends the stream over the network. External-drive support here is an inference from OBS’s documented local-file workflow, not an explicit certification of external SSD playback by OBS or YouTube.
How an external SSD fits into the setup
Think of the setup as a chain of separate jobs. The SSD stores the video. OBS reads that file and makes it a source in a scene. The computer runs OBS, encodes the picture and audio, and sends the resulting stream to YouTube’s ingest service over your internet connection. YouTube then handles the live event and its viewer-facing page.
The drive does not take the encoding workload off the computer, and it does not send the stream to YouTube. It is storage, not an encoder or a network connection. This distinction matters if you are choosing between an SSD and a more powerful computer: a faster drive may make file access convenient, but it will not compensate for a computer that cannot encode the chosen resolution or a connection that cannot sustain the upload.
OBS documents Media Sources as a way to use local media files, with controls such as looping. Using a file on a mounted external drive follows that local-file workflow, but neither OBS nor YouTube documentation cited here explicitly certifies external SSD playback. Treat the drive as an ordinary file location that you must test in the real account and schedule context.
For a single devotional video, a bhajan programme, or an ambience scene that should repeat, the SSD can make it easy to keep a large source file separate from the computer’s internal storage. The computer still needs to be on and running OBS throughout the broadcast. If you want the source on internal storage instead, the same OBS media-source workflow applies; a local copy may be a simpler choice where the external drive’s connection is unreliable.
If the main concern is what happens at the join between repeats, see the guide to looping one video without a black screen. That issue is about the file, player and encoder behaviour, not about whether the drive is internal or external.
Connect the SSD and keep it mounted
Before adding the file to OBS, connect the SSD directly to the computer where the scheduled task will run. In Windows, confirm that the drive appears in File Explorer and note its drive letter and folder path. For example, you might keep the source in E:\LiveChannel\evening-loop.mp4; use your own actual path rather than copying this example into a task.
A drive letter can change if other removable storage is connected or Windows assigns a different letter after reconnecting. If OBS points to a path that no longer exists, the scene can open without its intended media. Keep the SSD connected in the same port if practical, avoid changing drive assignments casually, and verify the file path again after a reboot or a disconnection. For a channel that cannot tolerate a missing source, consider storing a second copy on the computer’s internal drive and updating OBS to point to that copy if needed.
Check that the Windows account used by the scheduled task can read the folder. Access in your usual desktop session is not proof that a task running under a different account has the same access. This is particularly important if the SSD is encrypted or if its files are restricted to a particular user. Sign in as the intended account and test the exact file before relying on an overnight launch.
Also consider power and physical reliability. A loose cable, a power-saving setting that disconnects the drive, or someone unplugging it can interrupt file access. Secure the cable, keep the computer and drive in a place where they are unlikely to be disturbed, and check Windows power settings so the machine does not sleep during the broadcast. These steps do not make the stream failure-proof; they reduce avoidable interruptions in the storage path.
Keep a copy of the source and the OBS scene configuration somewhere separate from the live SSD. The channel backup guide covers the value of preserving media and setup details together. Do not put a stream key in a file that is shared with an untrusted person or left in a publicly accessible folder.
Select the video as an OBS Media Source
Open OBS and choose the scene that will carry the loop. In the Sources panel, add a Media Source, give it a clear name such as Main loop, and browse to the video on the mounted SSD. A descriptive source name makes later checks easier, especially if the scene also contains a logo, clock or background audio.
Use the source’s controls deliberately. If the video file contains its own audio, check whether OBS should use that audio and confirm the right audio device or track is being sent. If the stream should be silent, mute or disable the source audio rather than assuming silence from a preview. Watch the OBS audio meters and listen to the preview with headphones before publishing, since an unintended soundtrack can be as disruptive as a blank picture.
Set the source to fit the canvas in the intended way. If the video has a different aspect ratio from the OBS canvas, decide whether to crop, letterbox or use a background layer. Inspect the preview at full size: a small preview can hide black margins, clipped subtitles or a logo placed outside the visible area. If your channel uses text in Hindi or another script, check legibility at the size viewers are likely to watch.
Test the exact path after restarting Windows. A source that works while you are configuring OBS may not work if the SSD mounts later, has a different drive letter, or is not accessible to the account that starts the encoder. Launch OBS using the same Windows account and conditions you intend to use for the scheduled task, then confirm that the media is playing before testing YouTube.
Enable Loop for one file
For one repeating video, open the Media Source properties and enable its Loop option. OBS will then repeat the source when playback reaches the end. Start playback and leave it running long enough to observe the transition back to the beginning; a still image in the preview does not prove that the file is repeating correctly.
Pay attention to both picture and sound at the join. A hard cut may be acceptable for a visual loop of clouds or a static devotional image, but it may be jarring if music ends abruptly or a spoken introduction is cut in half. The transition depends on how the source file was edited and how the player handles its end; looping cannot create a smooth edit where the file itself has none. If the programme needs a seamless musical transition, prepare or edit a suitable source rather than expecting an encoder option to repair it.
OBS source settings and scene settings can be changed independently, so revisit the Media Source properties after duplicating a scene or replacing the file. Keep a short note of the intended source path and whether looping is enabled. That simple record helps distinguish a media problem from a scheduled-task or YouTube problem when something changes later.
If you use FFmpeg rather than OBS, do not copy a generic file-to-RTMP example and assume it loops indefinitely. FFmpeg’s documentation shows real-time file input and an RTMP output form, but that example is not a YouTube-specific command and does not establish an infinite-loop configuration. Validate loop and encoding options against the exact FFmpeg build you use. A guide to an FFmpeg playlist with mixed MP4 and MKV files is relevant when you are building a multi-file sequence rather than a single OBS source.
Use a playlist for several clips
If the channel needs a sequence of different clips, a playlist is often easier to manage than treating each clip as a separate live event. In OBS, you can use a Media Source playlist where supported by your version, or assemble a scene and playback approach that has a documented order and repeat behaviour. Add the files in the sequence you want, and test what happens after the last item: some configurations stop, while others can repeat the sequence when configured to do so.
Avoid mixing files solely because they appear to play on your desktop. Different resolutions, frame rates, codecs or audio layouts can make transitions unpredictable. Test the whole sequence, not just the first file, and watch the switch from the final clip back to the first. The older mini-PC playlist discussion is useful background when the same computer must both play a sequence and encode continuously.
Use filenames and folders that make the intended order obvious. For example, 01-opening.mp4, 02-song-a.mp4 and 03-closing.mp4 are less ambiguous than a folder of similarly named exports. Keep the original files unchanged elsewhere until the playlist has been tested; changing or moving a file on the SSD can break the path saved in the source or playlist.
A playlist does not remove the need to check each transition, audio level and aspect ratio. A sequence that plays correctly in isolation may still have a long pause, a black frame or an unexpected audio change between items. Run the complete sequence locally and inspect it before setting the Windows task, then repeat the check through YouTube’s preview.
Set up the YouTube event and scheduled launch
Create or schedule the broadcast in YouTube Studio’s Live Control Room. Set the title, visibility and other event details, then configure an encoder stream. YouTube says first-time live-stream enablement may take up to 24 hours, so enable and test the channel well before the intended broadcast rather than making the first test the event itself. A scheduled broadcast can provide an upcoming watch page and allow viewers to set reminders.
YouTube’s encoder setup instructions say to enter the YouTube Live server URL and stream key into the encoder. Treat the key as a password: do not paste it into a public script, share it in a support screenshot, or include it in a log that other people can read. YouTube explains its live-stream settings and stream-key controls; if the key is exposed, reset it in Live Control Room and update OBS before the next run.
In Windows Task Scheduler, create a task that starts the program you intend to use, with the correct executable path, arguments and working directory if needed. For OBS, do not assume that starting the executable is the same as opening the right profile and scene: test the launch with the saved configuration you will use for the live channel. Windows can start a process on a schedule, but it cannot infer whether the video source is present, the correct profile loaded, or the broadcast has become public.
Choose the account and run conditions deliberately. Microsoft’s schtasks documentation describes scheduling programs and starting or stopping tasks, but it does not establish a universal checkbox combination for every encoder setup. A task may run under an account that cannot read the SSD, may lack access to the desktop session needed by your application, or may start while the network is not ready. Test under the same account, trigger and sign-in conditions as the actual schedule.
Decide how YouTube should transition from encoder input to public live. In the manual scheduled-stream flow, start the encoder, wait until YouTube shows the preview, check it, and then click Go live in Live Control Room. YouTube also offers auto-start and auto-stop controls in stream settings; if those are enabled, the control flow can differ. Check the settings on the actual broadcast and test the behaviour, rather than assuming the Windows task alone makes the event public.
| YouTube start method | What the scheduled task does | Trade-off |
|---|---|---|
| Manual go-live | Starts OBS or another encoder; you inspect the preview and click Go live. | A person can catch a bad feed, but must be available at the start. |
| Encoder auto-start/auto-stop enabled | Starts the encoder, with YouTube’s configured controls governing the broadcast transition. | Less manual intervention, but the actual event settings and encoder behaviour need testing. |
For a channel where a person cannot be present at the start, do a controlled test with the intended auto-start settings and observe the public event from another device or account. If the channel instead prioritises a human check, schedule the task early enough that someone can inspect the preview and act. Do not leave a scheduled task that starts a second OBS process while the first is already streaming; query or stop the existing task and process before retrying.
Check computer and network responsibilities
During the stream, the computer remains responsible for reading the media from the SSD, decoding and playing it, compositing any scene layers, encoding the output and uploading it. YouTube recommends settings according to resolution and codec; for RTMP/RTMPS it recommends a two-second keyframe interval and constant bitrate, and its bitrate guidance varies by format. For example, the YouTube recommendation for 1080p at 30 fps is 10 Mbps for AV1 or H.265 and 14 Mbps for H.264. These are recommendations, not promises of smooth playback, and your available upload capacity must support the configured bitrate with room for normal variation.
Check the computer’s performance while OBS is active. Look for sustained high CPU or GPU use, encoder overload warnings, dropped frames and audio sync problems. If the machine struggles, lower the output resolution or frame rate, choose an encoder setting the computer can sustain, or use a more capable computer. The SSD does not perform encoding, so replacing it with a faster drive is not the first fix for encoder overload.
The network path matters separately from the file path. A local file can play perfectly while the upload connection falters. Prefer a wired network where practical, pause large uploads or downloads during the stream, and test at the time of day the channel usually runs. If viewers see buffering, use the buffering troubleshooting guide to separate upload and stream-health symptoms from media playback issues.
Windows power behaviour also matters. The machine must not sleep, restart for updates or lose power while the event is live. Set a deliberate power plan, plan updates for a maintenance window, and use a battery backup if a brief local power interruption is a material risk. None of these measures guarantees that the broadcast will stay live; they address common local causes that a scheduled launch cannot overcome.
FFmpeg users can consult the official background-task FAQ, which recommends -nostdin to prevent interactive input checks when running in the background. The FAQ also documents redirecting standard input to NUL on Windows. This is relevant when running a validated FFmpeg command from a task; it is not a substitute for checking the command’s file loop, encoder settings, log output or YouTube connection.
Keep logs that record when the task started and whether the encoder reported errors, while protecting any configuration that contains the stream key. Write down a clear stop procedure and make it easy to identify the active process. If a task is retriggered after an apparent failure, first determine whether the original process is still running; two encoders trying to use the same channel key can create confusion and may interrupt the intended stream.
A local scheduled-task setup is a reasonable fit if you want direct control and can maintain the Windows computer, storage path and network. If keeping a computer on overnight is the specific pain, StreamNeo removes that requirement by taking an uploaded video and running the YouTube broadcast while your computer is off; it does not change the need to prepare the file and configure the channel correctly.
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
Can I stream directly from an external SSD?
You can select a local file on a mounted SSD as an OBS Media Source, following OBS’s documented local-file workflow. That does not mean OBS or YouTube explicitly certifies external-drive playback, and the computer still plays, encodes and uploads the stream. Test the path after reconnecting the drive and under the Windows account used by the task.
Does a scheduled task automatically make the YouTube event public?
Not necessarily. In YouTube’s manual scheduled-stream flow, the encoder starts first and an operator checks the preview before clicking Go live. Auto-start and auto-stop settings can change that flow, so verify the actual event settings and test them before relying on unattended operation.
What happens if the SSD disconnects overnight?
OBS may lose access to the media file, so the source can stop behaving as intended even while the computer and network remain available. Secure the drive and cable, check the path after a restart, and keep a separate copy of important media. An internal copy can be a practical fallback if external-drive mounting is the fragile part of your setup.
Will a stream be archived if it runs all day?
YouTube Help says streams shorter than 12 hours are automatically archived; it does not establish the same archive outcome for longer streams. If you need a replay, check YouTube’s current guidance and plan a separate recording or archive workflow rather than assuming a long broadcast will be saved.