A continuous YouTube stream from vMix starts with playback, not MultiCorder: use PlayList or a List input to run your video files, then send the vMix programme output to YouTube. MultiCorder has a separate job: it records selected sources into separate files while a production is running.
For a set of clips that should play one after another, choose PlayList when you need per-item transitions and timing, or List when you want a large collection treated as one input. Both can loop, but neither is a time-of-day scheduler. Here is how to set up the playback, check the stream, and decide whether separate recordings are needed.
What each vMix feature does
Think of the workflow as three different jobs: playback, streaming, and recording. PlayList and List handle playback. The vMix programme output is what you send to YouTube. MultiCorder can capture selected sources independently for later editing or archiving; it does not make a playlist run or keep a broadcast going by itself.
A PlayList sequences inputs already available in the vMix preset. You add those inputs, order them, and configure each entry’s start position, duration, transition and transition time. When Loop is enabled, playback returns to the beginning after the last entry. This suits a modest set of clips when you want to choose how the change from one clip to the next looks.
A List input is a collection of video or audio files presented as one input. It can move automatically to the next item, loop, and optionally shuffle. It also supports M3U files. vMix notes that a List avoids loading every video into the project simultaneously, which can be useful when the collection is large.
The programme output is the assembled picture and sound that vMix sends out. It may contain a currently playing input, transitions and other production elements. For a simple prerecorded loop, the playback input needs to reach that output; adding files to a PlayList or List alone does not put them on YouTube. Confirm the intended output in vMix before starting the broadcast.
MultiCorder is for recording sources separately from the main vMix recording. For example, you might stream a finished programme while also saving camera feeds as individual files for later editing. Those raw source recordings do not ordinarily include the programme’s effects or colour correction. The exception is when recording Output 1–4, which captures those outputs as configured. This is a recording workflow, not continuous playback automation.
Choose PlayList or List
Choose PlayList when each item is a vMix input and you want to control its place in a sequence, its start and duration, or its transition to the next item. It is a practical fit for a short set of prepared segments: an opening, several themed sections, and a closing sequence. You can set a transition per entry instead of applying one rule to the entire collection.
Choose List when your source is a changing folder of files, a longer catalogue, or an M3U collection that should be treated as one playback input. It can advance automatically and loop without requiring all of the videos to be loaded at once. Shuffle is available when a fixed order is not important, although it is a poor choice if viewers need a reliable progression, such as lessons in sequence.
| Need | Better starting point | What to check |
|---|---|---|
| Different transitions or timing per clip | PlayList | Configure each entry, then test the hand-off between inputs |
| One input representing a larger set of media | List | Check the file order, Auto Next and Loop settings |
| Playback that repeats without clock-based starts | Either | Looping does not create a time-of-day schedule |
| Separate source files for post-production | MultiCorder, alongside playback | Check edition, storage and recording workload |
You can also put a List into a standard PlayList if you want to combine a long file collection with other vMix inputs in a broader sequence. That adds flexibility, but it also adds another layer to check: confirm the List advances as intended and that the enclosing PlayList moves on or loops at the right point.
Before settling on either method, write down what viewers should see after the final item. If the sequence should simply begin again, looping is enough. If a particular programme must begin at a particular clock time, a loop is not the same thing; see the scheduling limits below. For a recorded service workflow, planning a scheduled church stream may help clarify the difference between preparing content and arranging when it airs.
Add and configure your media
Start with the source files and inputs you actually intend to broadcast. Check that each video opens and plays in vMix, that its audio is present where expected, and that the media remains available at the location vMix uses. A project that relies on a removable drive or a renamed folder can appear ready while still being unable to find a file after a restart.
For PlayList, add the relevant inputs to the preset, then open the PlayList control at the lower left of the vMix interface. In the PlayList window, choose an item under Available Inputs and use the right-arrow control to add it to the sequence. Arrange the entries in the intended order. Double-click an entry to configure its start position, duration, transition and transition time.
A duration of zero tells vMix to use the input’s duration. Use that when a clip should run to its natural end; specify a duration when you deliberately need a fixed segment. A shortened duration can cut off speech or music, so preview the final seconds of a few representative entries rather than assuming the next clip will begin at a convenient point.
Transitions are properties of individual PlayList items. A cut may be right for a sequence of lessons or news segments; a different available transition may suit a slower devotional or ambience channel. Choose deliberately and watch the hand-off. A transition that looks fine between two similar shots may make a sudden change in brightness or sound more noticeable between unrelated clips.
For List, add a List input and populate it with the video or audio files, or use an M3U file where that fits your library. Review the order shown in the input. If titles use a naming convention, check that the displayed sequence matches it; do not assume alphabetical order will produce the editorial order you expect. List can be used on its own or inserted into a PlayList for a more complex run of material.
Run through the whole chain with a small representative sample before preparing the full broadcast. Include a file with a different aspect ratio, audio level or duration if those differences exist in your collection. This is where you catch missing media, a silent item, an unexpected black frame, or a transition that is too abrupt. If the stream will carry a continuous audio bed, the guide to preventing audio drift covers a related problem worth checking in longer broadcasts.
Set looping and advancement
In a PlayList, enable Loop so the sequence returns to its first item after the last. Start playback with the PlayList control and observe at least one transition. A list that contains the right clips but has not been started will not produce continuous playback, and a sequence that reaches its end without looping will stop rather than begin again.
With List, check that automatic advancement to the next file is enabled, then enable Loop for repetition. Use shuffle only if a changing order makes editorial sense. If the files are lessons, a numbered course or a news rundown, shuffle can make the stream confusing; for a collection of interchangeable ambience scenes, it may be acceptable. Test the end of the list and its return to the beginning before relying on it overnight.
Playback repetition is not scheduling. vMix says it is primarily designed for live events and does not support time-of-day scheduling for 24/7 television programming. Its documentation describes PlayList and List as basic 24/7 playback options when content need not start at a particular time. Its support page also says vMix Scheduler is unmaintained and that compatibility is uncertain. Check the current vMix scheduling guidance rather than building a critical broadcast around assumptions about scheduler support.
This distinction matters if you want, for example, a morning prayer service to begin at a fixed local time and a different programme to follow at noon. A looping sequence can repeat material, but it does not promise to change content at those clock times. If the requirement is simply to play a long collection day and night, a loop may be enough. If fixed programme starts matter, assess a scheduling workflow separately and test it rather than treating Loop as a schedule.
Save the preset after the sequence is configured. PlayLists are associated with the active preset, so reopening a different or older preset can leave you with a different setup than expected. When restoring a channel after a computer restart, load the matching preset and confirm that the files, playlist order, loop setting and active playback input are still correct.
Send the programme output to YouTube
Before configuring the stream, confirm that your YouTube channel is eligible to go live. YouTube requires channel verification and no live-stream restriction in the past 90 days. The current YouTube Help guidance on live streaming explains eligibility and the current process; check it directly because account status and Studio screens can change.
In YouTube Studio, prepare a live stream and obtain the stream key for the event or stream configuration you intend to use. In vMix, configure the streaming output to use YouTube’s current requirements and the appropriate key. Exact control names can differ by vMix version, so use the current vMix interface and YouTube Studio rather than following a guessed sequence of buttons. Keep the key private: anyone with access to it may be able to send a signal to the stream.
Choose the resolution, frame rate, codec and bitrate based on the material and the upload connection you can sustain. YouTube’s encoder settings guidance gives current recommendations, including H.264 bitrate examples of 14 Mbps for 1080p30 and 17 Mbps for 1080p60. Those are YouTube recommendations for particular settings, not a guarantee that your connection can sustain them. The same guidance recommends a two-second keyframe interval, not exceeding four seconds, constant bitrate (CBR), and RTMPS as the recommended secure protocol.
Run a speed test and compare the available upload capacity with the chosen stream settings; YouTube itself recommends testing upload bitrate. Leave headroom rather than choosing settings that use all the connection’s capacity, especially if other people or devices share it. If your connection cannot sustain a setting reliably, lower the output rather than hoping a brief successful test represents a full night of streaming.
Do a private or otherwise appropriate test with sound and representative motion before the public broadcast. A still image may hide encoding or motion problems, and a silent test will not reveal a missing audio route. Check that the intended vMix programme reaches YouTube, that the sound is present, and that transitions and file changes work. During the live stream, watch YouTube’s stream health and respond to warnings; starting the broadcast is not the same as confirming it remains healthy.
If your source is a long recorded lesson or devotional set, prepare its sequence and stream settings as separate tasks. A guide to rotating recorded lessons without restarting offers another perspective on changing content during an ongoing broadcast. Whichever method you use, test changes before viewers depend on them.
Where MultiCorder fits
Use MultiCorder only when you have a separate need to retain source recordings. For example, a small business might stream a finished programme but want clean camera recordings for a later edit, or a local event team might need separate camera feeds for review. If all you need is a repeated file sequence on YouTube, MultiCorder adds recording work without solving playback or scheduling.
The vMix Help 28 page identifies MultiCorder as available in vMix 4K, Pro and Max. Confirm the current edition information on the official MultiCorder page before buying or upgrading; edition availability is a vendor fact that can change. The feature records selected capture sources into separate files as well as the main recording. Select the sources, recording format and destination folder in its settings, then start it when the production is ready.
Be clear about what each file contains. Recordings of raw inputs do not include the normal programme effects or colour correction. If you need a composed result, the main vMix recording or a configured output may be the more suitable record; MultiCorder’s Output 1–4 selections capture those outputs as configured. Choose based on what the editor needs later, not merely on the number of files you can record.
Storage is a practical constraint. vMix lists an SSD in its minimum requirements for MultiCorder and warns that a drive unable to keep up with simultaneous camera recordings can cause dropped frames. There is no universal capacity or speed figure that fits every combination of source format, number of sources and recording format. Check sustained write capability, connection compatibility, available capacity and how many recordings will run at once. Use a short test with the actual workload before a live production.
The vMix guidance also states minimum system requirements including an Intel Core i7 Quad Core or higher and a high-end graphics card with at least 1 GB onboard memory. Treat these as the vendor’s stated minimums, not a modern universal workstation recommendation: actual capacity depends on the system and workload. vMix recommends a fault-tolerant recording format and fast storage. Also note that MultiCorder cannot run at the same time as Instant Replay, so decide which function matters for the production before you build the workflow.
For a channel that simply needs a prerecorded file to stay on air while your own computer is switched off, using vMix means leaving the playback and streaming setup running on your computer. When the pain is that the computer must stay on for a cloud-run file broadcast, StreamNeo removes that specific need: you upload a video, provide your YouTube stream key, and the stream runs without keeping your computer switched on. It is YouTube-only and does not replace vMix when you need its live production controls or isolated source recordings.
If a local vMix setup is the right fit, verify the playlist and output on the actual machine you plan to use, then decide how you will recover after a power or connection interruption. If you want a continuous file stream without keeping that computer on, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
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
Is MultiCorder what makes a vMix playlist repeat?
No. PlayList or List handles playback and looping; MultiCorder records selected sources into separate files. You can use them during the same production for different purposes, but MultiCorder does not sequence or schedule the media.
Should I use PlayList or List for a large collection?
List is a useful starting point when you want many files presented as one input and do not need individual vMix input transitions for every item. PlayList gives you per-entry timing and transitions. Test file order and playback behaviour with your own media before relying on either overnight.
Does looping schedule a programme to start at a set time?
No. Looping returns to the beginning when the sequence ends; it does not start specific content at a clock time. vMix says it does not support time-of-day scheduling for 24/7 television programming, so check current vendor guidance if fixed start times are essential.
What should I check before going live?
Confirm YouTube live eligibility, the stream key and output settings, then test audio and representative motion. Verify that the playlist advances and loops, and watch YouTube stream health during the broadcast. For MultiCorder, also test that storage keeps up with the recordings you selected.