If you need to remove a sold home's footage from a property channel, first identify which playlist is actually supplying the video. For a local FFmpeg concat list, edit the source list, verify the remaining files, then restart FFmpeg or use a reload procedure confirmed for your exact build; changing the file alone does not establish that a running process will reread it.
A YouTube Live broadcast resource, an HLS media playlist and a local concat list are different things. Changing the wrong one can leave the sold listing on air, disrupt the feed, or alter a component that FFmpeg is not using.
Identify which playlist you are editing
Start from the running command, logs or dashboard, not from a file called playlist. Find the source FFmpeg opened and the output it is sending to YouTube. A text file containing lines such as file 'property-a.mp4' is likely a concat demuxer input. A YouTube Live broadcast or stream is an API-managed resource, while an HLS playlist describes media segments and is used only if your ingest workflow uses HLS.
The FFmpeg concat demuxer documentation describes a local list-file input. YouTube's Live Streaming API documentation describes broadcast and stream resources, which are not substitutes for that local file. If your command reads a local list and sends encoded video through an ingest URL, changing a YouTube broadcast setting will not remove a filename from FFmpeg's input.
HLS is a separate case: its media playlist references segments and follows HLS-specific rules. YouTube's HLS ingest guide explains that workflow. Do not edit an HLS playlist just because someone informally called your rotation a playlist; confirm that the encoder actually sends HLS to YouTube.
Look at the FFmpeg command line, process manager configuration, or operator notes. A local input might appear as -f concat -safe 0 -i rotation.txt; the exact options vary, and that example is not a recommendation to copy blindly. If a wrapper script or control panel launches FFmpeg, establish which file it passes in and whether it has its own reload function. The same filename may be a generated copy rather than the source of truth.
Also establish whether the sold property is currently on screen. Check the playback log or preview and note the current clip, the next clip and the expected transition. A change may require a process restart, and that can interrupt viewers depending on how the ingest and broadcast are managed. Plan the timing before touching a live rotation.
For background on the local-list workflow, see streaming a folder of videos with FFmpeg's concat demuxer. If your encoder is wrapped in a container, the Docker walkthrough for a 24/7 church stream can help you find where its configuration is supplied. These are context, not proof that your particular process rereads a file.
Back up the current source list
Before editing, make a copy of the active list and preserve its current order. Give the copy a name that makes its purpose clear, such as rotation-before-sale-removal.txt, and keep it somewhere that will not be overwritten by a startup script. If the list is generated automatically, back up the generator's source data as well; a later restart could recreate the old list from that data.
Record the current FFmpeg command, working directory and process manager settings. You may not need to change any of them, but they are useful when a restart behaves differently than expected. Keep the active broadcast settings, stream key handling and output options unchanged unless you have a separate reason to alter them.
A backup is useful for rollback, not for putting sold footage back on air by default. Keep the removed file available until the replacement has been checked, but label it clearly as excluded from the active rotation. That avoids a rushed cleanup turning into accidental deletion or reintroduction.
If another person operates the channel, note who is making the change and when you expect to apply it. One simple change record can say: sold listing removed from the source list; remaining files checked; encoder restart planned; preview to be verified. This keeps a handover from becoming a second, conflicting edit.
Remove the sold property's entry
Edit the source list that the live command actually reads. Remove only the sold property's entry, then leave the remaining entries in their intended order. If you want a new property to replace it, add the new path as a separate deliberate change; do not use the removal as an excuse to reorder or rename unrelated media.
The concat demuxer expects a particular list-file syntax. Follow the format already used by your command and the documentation for the FFmpeg version installed. Do not assume that a generic playlist editor understands concat directives. If the list has comments, options, or generated path prefixes, preserve the valid structure and remove the complete entry rather than only part of a line.
When the current clip is the sold property, decide whether to let it finish before applying the update or stop and restart now. Letting it finish may be less abrupt, but it leaves the footage on air longer. Restarting sooner may cut the current clip and may produce a viewer-visible interruption. The right choice depends on the listing's status, the channel's promise to viewers and the behaviour of your broadcast setup; neither choice is guaranteed to be seamless.
Do not conclude that saving the file changes the input of a running FFmpeg process. The reviewed FFmpeg documentation explains concat inputs and list-file options but does not promise that an already-open concat input will reread edits immediately. Treat the saved edit as a change waiting to be applied, unless the exact application around FFmpeg provides a reload mechanism that you have verified.
For a practical explanation of how the concat input is put together, use the folder-to-YouTube concat example alongside your own command. Compare its assumptions with your list and version; a tutorial command is not a substitute for identifying the active input.
Verify the remaining paths and files
Before restarting, read every remaining entry and check that its file exists at the path FFmpeg will resolve. A relative path depends on the process's working directory, which may differ from the directory where you opened the text file. If FFmpeg runs in a container or under a service account, verify the path from that environment rather than only from your desktop file browser.
Open each remaining video with a local probe or playback check if practical. Confirm it is readable and that the file is not a stale shortcut, a partial copy, or a path with a spelling or capitalisation difference. On systems where path case matters, Home.mp4 and home.mp4 may not refer to the same file. A quick, controlled check is cheaper than discovering a missing input during a live restart.
The concat demuxer's safe option defaults to 1; the documentation says that safe mode rejects unsafe paths and directives. Do not disable it casually to make a list with unusual paths pass. Prefer a tidy list of appropriate relative paths in a trusted working directory when that fits your setup. If a path is rejected, understand why and consult the installed version's documentation before changing safety settings.
Check that the list still has the expected entries and order after removal. If a script creates the list, inspect its output after generation: the script may reinsert the sold property from a catalogue or cache. Keep the removed clip outside any directory that a “play everything here” workflow scans automatically, or ensure the generator explicitly excludes it.
A useful validation pass has three parts: the sold property's path is absent, each intended remaining path resolves, and the sequence matches the channel's intended rotation. This does not guarantee the media has ideal encoding or that YouTube will accept every frame; it catches the source-list errors that a careful replacement can catch before broadcast.
Choose a confirmed reload or restart method
Next decide how the revised list reaches the active encoder. If your process manager has a documented reload action, verify that the action reloads the FFmpeg input rather than merely re-reading unrelated settings. Test it with a non-sale clip in a safe environment, or during a planned maintenance window, before relying on it when a listing changes.
If no such mechanism is documented and tested, the predictable method is to stop and relaunch the FFmpeg process using the revised list. Use the same known-good command and process manager configuration, with only the intended source-list change. A restart may interrupt the outgoing media or make YouTube show a reconnecting state; the exact transition depends on the encoder, ingest method and broadcast state.
YouTube models a live broadcast and its associated stream as distinct resources. That distinction is useful when planning a process restart: preserving the same broadcast setup may be possible, but do not assume that restarting FFmpeg means the broadcast itself must be recreated, or that every workflow preserves it automatically. Check the applicable YouTube workflow and your operator controls before acting.
For a hosted workflow where keeping a home computer running and relaunching a local encoder is the specific operational burden, StreamNeo removes that particular step: you upload a video, provide the YouTube stream key, and the stream continues from the cloud with monitoring and automatic restart if it drops. It is YouTube-only, so it does not replace a local FFmpeg setup when you need direct control of the command or a different destination.
If you operate FFmpeg on a virtual machine, the always-on VM guide may help you locate the process and its restart controls.
Check the encoder and YouTube preview
After applying the change, inspect the new FFmpeg log from startup. Look for confirmation that it opened the revised list and the intended first file, rather than a stale copy or an old working directory. If it reports a missing file, unsafe path or malformed list, stop and correct the source instead of repeatedly restarting with the same error.
Watch the local output or encoder status long enough to confirm that the expected clip is being read and that the process remains active. Then check YouTube's live control room preview or the appropriate monitoring view for an incoming signal. Confirm the broadcast is receiving video and audio as expected; do not treat a running FFmpeg process alone as proof that viewers are receiving the intended feed.
If the previous clip continues after you edited the list, first check whether the process was actually restarted or the confirmed reload action completed. Confirm that the command points at the file you edited. A duplicate list, generated configuration or second encoder process can make a correct edit appear ineffective.
If YouTube shows no incoming video after restart, compare the new output configuration with the saved command and inspect FFmpeg's error output. Avoid changing the stream key, broadcast resource and input list all at once: multiple simultaneous changes make it harder to identify the cause. If the stream reconnects, use the relevant YouTube status information and your logs to determine whether the interruption is temporary or the encoder has failed.
Keep the pre-change list and removed video until the revised rotation is confirmed. If something goes wrong, use the saved command and source list to restore the known state, then diagnose the issue off-air where possible. Test this exact change procedure with a harmless clip before the next sale, so you know how your own process manager handles it.
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
Will FFmpeg notice a concat-list edit while it is already streaming?
Do not count on that. The official concat documentation describes the input format and options, but it does not promise that an open input will immediately reread a changed list. Use a reload mechanism only after confirming it for your build and workflow; otherwise restart FFmpeg with the revised list.
Is a YouTube Live playlist the same as my local FFmpeg playlist?
No. A local concat list tells FFmpeg which files to read, while YouTube Live resources represent the broadcast and stream. An HLS media playlist is another distinct format, used when your workflow sends HLS segments to ingest.
Can I safely remove the sold property's video file after editing the list?
Wait until the new rotation is confirmed and you have a rollback copy of the source list. Also check whether a generator, another playlist or an archive workflow still uses the file. Removing it from the active rotation does not require deleting it from storage immediately.
How do I avoid a visible interruption when I apply the change?
There is no universal guarantee: the result depends on the process manager, encoder command, ingest method and broadcast state. Test the exact restart or reload procedure with a non-sale clip, then schedule the change when a brief interruption would be manageable.