To make a Wirecast video playlist repeat, set the playlist’s end behaviour to Loop. In the Wirecast 13 Windows guide, that means playback returns to the first shot after the final shot; a clip’s own end behaviour is a separate setting.
This distinction matters when you are building a long-running YouTube channel: the playlist can be configured to repeat while an individual clip may still stop at its end, or a clip may loop while the playlist itself is set to hold. The exact controls can differ by Wirecast version, so use the guide as a description of the behaviour and confirm the labels in your installed release.
Add clips and confirm playlist order
Start by deciding what one complete pass through the channel should contain. A devotional stream might move from an opening slate to a sequence of bhajans and then a closing card; a study channel might use several ambience videos in a deliberate order. Add the intended video sources to the Wirecast playlist and check that the sequence is the one you mean to broadcast.
Do not treat the playlist as a folder. Its order determines what viewers see next, so inspect the entries rather than assuming that files were added in the desired sequence. If the opening item is a short title card, for example, it will appear each time the playlist restarts if the playlist is set to Loop. That may be intentional, but it can become repetitive when a cycle is short.
Check that each source is the correct file and that its audio is appropriate for the stream. A file that looks similar by name may be a different edit, have a silent lead-in, or contain a different ending. Scrub or preview enough of each clip to recognise it before you rely on the list for an overnight broadcast.
If your project uses a longer collection of pre-recorded material, the planning principles in this guide to making a 24/7 YouTube stream from pre-recorded videos can help you decide what belongs in a repeatable programme. The editing and playlist arrangement still need to be checked in Wirecast; a well-ordered set of files is not the same thing as a tested broadcast.
Before setting any loop control, note what should happen at the end of the final item. If the sequence should begin again with the first shot, the playlist needs Loop. If you want it to remain on the last shot instead, the behaviour is different. That choice concerns the playlist as a whole, not the playback rule for every source in it.
Set the playlist end behaviour to Loop
The Wirecast 13 Windows user guide describes the playlist end behaviour called Loop as returning playback to the first shot and continuing through the sequence. Set the playlist’s end behaviour to Loop when you want the entire ordered set of shots to repeat. This is the control that makes a playlist cycle, rather than merely making one video repeat.
Find the playlist-level end behaviour in your version’s playlist controls and select Loop. The guide provides the behaviour and a reference for Wirecast 13 on Windows, but it should not be taken as a promise that the current interface has the same layout or wording. If you do not see the same label, consult the documentation for your installed version and look for the control governing what happens when the playlist reaches its end.
A useful mental test is to imagine the last shot finishing. With the playlist’s end behaviour set to Loop, playback should return to the first shot. With a hold-style end behaviour, the playlist can remain on its last shot instead. That difference is easy to miss when you test only the opening of a sequence, so later in this guide, run through the final transition as part of a complete-cycle test.
The playlist setting does not mean that every source will restart at its own end in the way you might expect. A clip can have its own playback behaviour, and that behaviour may affect what happens while the playlist is on that shot. Keep the two decisions separate when you configure the list.
Set an individual clip to Loop if needed
Some clips need their own end behaviour. In the Wirecast 13 Windows guide, the source’s properties include a When Finished behaviour; choose Loop for a clip that should restart at its own end. This is useful when a particular shot is intended to repeat, rather than simply play once as the playlist advances.
For example, suppose your playlist includes a long sequence of videos plus a short ambience shot that should continue until you move to the next part of the programme. Decide whether that source should restart, stop, or follow another available behaviour in the installed version. The source-level choice is not a substitute for setting the playlist’s end behaviour: one governs a clip, the other governs what the playlist does at its end.
Open the relevant source properties and inspect the When Finished control if your release uses that label. Set it to Loop only when restarting that particular source is what you intend. If the clip should play once as part of a sequence, another behaviour may be more appropriate. Avoid changing every clip to Loop as a reflex; that can cause a shot to repeat where you expected the next playlist item to take over.
The Wirecast 13 guide also calls attention to the interaction between a playlist set to Hold and the last clip’s own behaviour. A playlist that is set to Hold can remain on its final shot even if that clip has a different end setting. In other words, changing the clip property alone does not turn a playlist that holds at its end into one that returns to its first shot.
The practical approach is to write down the intended result for each level before changing settings: should this particular clip restart, and should the full playlist restart after its final shot? Then verify both settings and test the transitions. This avoids diagnosing a playlist-level issue by repeatedly changing the properties of individual sources.
Understand playlist looping versus clip looping
The two Loop decisions answer different questions. Playlist end behaviour answers, “What happens after the final shot in the sequence?” A clip’s When Finished setting answers, “What happens when this source reaches its own end?” The word Loop may appear in both contexts, but the scope is different.
| Control | What it governs | Typical use |
|---|---|---|
| Playlist end behaviour: Loop | The complete sequence after its last shot | Return to the first shot and repeat the ordered playlist |
| Clip When Finished: Loop | One video source when it reaches its end | Restart that particular clip when it finishes |
| Playlist end behaviour: Hold | The playlist after its final shot | Remain on the last shot instead of starting the sequence again |
These are not competing descriptions of one control. You may need playlist Loop with individual clips set to play through once, so the playlist advances in order and then returns to the beginning. Or you may need a specific clip to repeat at its own end while the larger programme has a different end behaviour. Choose based on the programme you want viewers to see.
If the last item appears to stop rather than restart, check the playlist end behaviour first. If one clip stops or repeats unexpectedly before the sequence reaches its final item, inspect that source’s own playback behaviour. This simple diagnosis keeps you from changing the wrong setting.
There are other kinds of repetition in a YouTube stream too. If a YouTube playlist is repeating one item rather than progressing through the intended sequence, that is a different problem from Wirecast’s playlist end behaviour. The article on stopping a YouTube live loop from repeating the same playlist item addresses that separate situation; do not assume a setting with a similar name is controlling the same part of the workflow.
Verify controls in your installed version
The detailed playlist and clip behaviour cited here comes from Telestream’s Wirecast 13 Windows user guide. It establishes the distinction and describes what those settings do in that release. It does not establish that the controls sit in the same place or carry the same labels in every Wirecast version or on every operating system.
Telestream’s Wirecast version history is the place to check public release information. Before changing a production setup, identify the version you actually run and refer to its documentation. Look for the playlist’s end-of-sequence behaviour separately from the source’s end behaviour, even if the interface presents them differently from the Wirecast 13 guide.
Do not rely on a remembered menu path from a different computer or an older tutorial. Software updates can alter interface details, and a screenshot may represent another operating system or release. Confirm that the setting you change is attached to the playlist or to the selected source, rather than inferring scope from the word Loop alone.
If you cannot identify a control confidently, test on a short sample playlist before replacing settings in the programme you intend to run. Add two or more recognisable clips, set the behaviour you believe is playlist-level, and observe what happens after the last one. Then test a source-level behaviour separately. That small, visible test is safer than discovering the distinction during a live broadcast.
Test the YouTube stream before relying on it
Wirecast can send an encoder stream to YouTube. YouTube’s guide to creating a live stream with an encoder includes Wirecast among the encoder options. In YouTube Studio’s Live Control Room, prepare the stream and check that the incoming preview shows the expected picture and sound before you start broadcasting to viewers.
If live streaming has not been enabled for the channel, check YouTube’s current eligibility and setup instructions in advance. YouTube notes that first-time enablement may take time, so do not leave the channel setup until the hour you want to go live. Follow the current instructions in YouTube’s live streaming tips, and allow time to resolve account or encoder issues before treating the channel as ready.
Run a full playlist cycle in a controlled test. Confirm the opening shot, at least one middle transition, the final shot, and the return to the first shot. Listen for audio continuity as well as watching the video: a playlist can advance correctly while a source has an unexpectedly silent section, abrupt ending, or level change. A test that ends before the playlist’s final item cannot verify playlist looping.
YouTube recommends leaving about 20% upload-bandwidth headroom beyond the bitrate being sent. Treat that as YouTube’s recommendation, not a guarantee that the connection will remain stable. The upload available to the encoder can vary, particularly on a shared or wireless connection, so check the actual stream status and leave capacity rather than planning to use every bit of the measured upload rate.
YouTube also recommends RTMPS for encrypted ingestion and testing before going live. Its encoder settings guidance covers stream settings and the platform’s recommendations; choose settings appropriate to the resolution, frame rate and connection you can sustain. Do not assume that selecting a high resolution by itself produces a good stream if the upload connection cannot carry it reliably.
While testing, keep Wirecast’s programme output and the YouTube preview in view, then monitor the stream’s audio and video after it is live. A 24/7 schedule is an operating goal, not a promise that a computer, connection, encoder or platform will never fail. Check the system during the hours you plan to run it and have a clear procedure for recovering a dropped broadcast.
A desktop workflow also means the computer running Wirecast needs to remain available and connected for the broadcast. Consider the practical cost and reliability of leaving that machine on; the discussion of electricity costs for an old laptop used for 24/7 YouTube streaming in India can help you think through that operating trade-off. Check Telestream’s requirements for the Wirecast version you intend to run rather than assuming a particular computer will be suitable.
If keeping a computer running and recovering a dropped desktop stream is the part you want to avoid, StreamNeo removes that specific task by running an uploaded video as a YouTube stream without leaving your computer on. It is YouTube-only, so it is not a replacement if your workflow depends on Wirecast’s live production controls or another platform.
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 Wirecast Loop restart the playlist or just the current clip?
The playlist’s end behaviour set to Loop returns the sequence to its first shot after the last shot. A clip’s own When Finished Loop behaviour applies to that source when it reaches its end. Confirm which control you are changing in your installed version.
Why does the final video stop instead of the playlist starting again?
Check the playlist’s end behaviour, not only the final clip’s source properties. In the Wirecast 13 Windows guide, Hold can leave the playlist on its last shot, while playlist Loop returns to the first shot. Test the whole cycle after changing it.
Do the Loop controls look the same in every Wirecast version?
No. The detailed behaviour described here is from the Wirecast 13 Windows guide, and it does not establish identical placement or labels across releases. Check the documentation for your installed version and verify the result with a sample playlist.
Is a Wirecast playlist loop enough to guarantee a 24/7 YouTube stream?
No. It controls playback behaviour in Wirecast, not the reliability of the computer, network, encoder or YouTube connection. Preview and test the stream, leave upload headroom, and monitor the broadcast while it runs.