To play property-tour MP4 files in sequence on YouTube Live from Ubuntu, use OBS Studio with its VLC Video source: add the files in the order you want, then send OBS’s output to a scheduled YouTube encoder stream. YouTube receives the live broadcast from OBS; it does not provide the local MP4 playlist.
The key work is checking that OBS can see VLC, testing the full playlist and its audio, and confirming the scheduled stream preview before you go live. Installation steps vary by Ubuntu release and packaging route, so check current OBS and Ubuntu guidance rather than relying on an older command as a universal fix.
Confirm your Ubuntu and OBS installation route
First check which Ubuntu release you are using and how you intend to install OBS. OBS’s Linux installation guidance describes routes for Linux, but packaging and supported instructions can change. Follow the current directions for your release, and consult Ubuntu’s own package guidance if you are unsure what a package source will install. Do not treat a command copied from an older guide as the only valid route.
After installation, open OBS and confirm that it starts normally. The exact interface can change, but you should be able to create a scene, add a source and open the streaming settings. If OBS fails to start or reports missing libraries, resolve that before building the playlist; otherwise a later playback problem can be hard to distinguish from an installation problem.
For this workflow you also need VLC installed, because OBS’s VLC Video source relies on it. The OBS media-source documentation explains the relationship and the supported playlist behaviour. If OBS came from a sandboxed package route, VLC may not automatically be visible to it; check the current instructions for that package and verify the source works before you prepare a long stream. A successful VLC installation by itself does not prove OBS can access it.
If you are weighing a local workstation against a different continuous-stream approach, the practical distinction is who has to remain responsible for playback and the encoder connection. Our guide to streaming prerecorded video from Linux without OBS covers a different route. For a desktop playlist with visible scene and audio controls, OBS gives you a straightforward way to inspect the output.
Install and configure the playback source
In OBS, make a scene for the property tours, then add a VLC Video source. Choose the option to create a new source, give it a recognisable name such as “Tour playlist”, and open its properties. Add the MP4 files there. Keep the files in a stable location on the Ubuntu computer, rather than moving or renaming them after you have configured the source; the playlist needs to be able to find them when playback begins.
OBS documents VLC Video as a source that can play a playlist, including MP4 media. Its media sources guide notes that VLC must be installed and that 64-bit OBS needs 64-bit VLC. If the source is missing or shows no media, check the OBS and VLC installation routes and their architecture before rebuilding the playlist. This is especially worth checking if one application was installed from a package format with separate access rules.
A single-file Media Source and a multi-file VLC Video source solve different problems. Use Media Source when you want to manage one clip at a time; use VLC Video when several files need to play in sequence and you want playlist controls such as loop and shuffle. The VLC source is the better fit for this property-tour task, but it brings VLC’s installation and visibility into the setup. You can compare OBS source behaviours in the official media-source guide.
Set the scene canvas and output to suit the footage you actually have. If one tour is landscape and another is portrait, or their resolutions differ, look at how each appears in the preview. A tour cropped to fill the frame may lose a room edge or a property detail; a fit-to-frame treatment can leave unused space. Choose deliberately and inspect the result rather than assuming every MP4 has the same shape.
Queue MP4 property tours in order
Add the files in the order viewers should see them. For example, you might begin with a short exterior approach, follow with the interior walkthrough, then finish with amenities and location footage. This sequence is controlled by the order in the VLC Video source playlist, not by the order in which files happen to appear in a folder.
Use clear filenames and keep a separate note of the intended sequence. Names such as 01-exterior.mp4, 02-living-area.mp4 and 03-amenities.mp4 make it easier to catch a wrong selection when editing the playlist. The numbering is a housekeeping convention, not a requirement for OBS. If you later replace a file, reopen the source properties and confirm the playlist still points to the correct path.
Keep shuffle off when the tour order matters. OBS’s documentation says shuffle is off by default, which preserves the configured sequence, but verify the setting instead of relying on a default. Randomly placing a kitchen or location segment before the opening exterior can make a viewing session feel disjointed, particularly if the stream loops while you are away.
Think about the point at which the playlist restarts. If the last clip is a location overview and the first is a close-up interior, the loop may be noticeable. You cannot assume that separate MP4 files will change over without a brief pause or a visual discontinuity: codecs, frame rates, audio tracks and file boundaries differ. A deliberate order can reduce the jarring effect, but only testing your actual files will tell you how the transition looks.
For a broader discussion of arranging multiple inputs in OBS, see how to broadcast multiple video sources to YouTube Live. Here the source is a playlist of recorded tours rather than a set of simultaneously active cameras, so the important control is sequence and repeat behaviour.
Set and test playlist looping
OBS documents playlist looping as enabled by default for the VLC Video source. Check the loop control in the source properties and decide whether repeating is appropriate for your broadcast. If the stream is intended to run beyond one pass, looping means the playlist starts again after its last item; it does not make YouTube construct a playlist or choose what plays next.
Before scheduling a public viewing session, play the list through in OBS. Watch the start of every file, each transition and the return from the final clip to the first. Listen for a level change, a clipped opening word, silence, or a soundtrack that carries awkwardly across a file boundary. A sequence that appears correct in a source settings window can still reveal problems when the actual clips play.
Property footage often includes narration, ambient sound or music. Decide whether each clip should retain its own audio and whether one clip is much louder than another. Adjust levels in OBS only after listening to the complete sequence; raising a quiet clip can make another one too loud. If you are adding separate narration or music sources, check that they remain in sync and do not obscure useful spoken details.
A loop is not always the best editorial choice. A viewer arriving halfway through a long tour may benefit from a short recurring introduction or a simple on-screen note that explains what is playing, while a repeated opening slate may become tiresome. The right treatment depends on the length and purpose of the tours. Review the full loop from a viewer’s perspective, not only the first minute.
Confirm that you have permission to broadcast both the video and every included audio element. Ownership of a property or permission to film it does not necessarily settle the rights for a soundtrack or other material included in the edit. Check the current YouTube policies and the permissions relevant to your material; no OBS setting can resolve that question for you.
Connect OBS to a scheduled YouTube stream
In YouTube Studio, open Go Live and create or schedule a stream configured for an encoder. YouTube’s encoder setup instructions explain the workflow. In the Live Control Room, retrieve the stream URL and stream key, then enter them in OBS’s streaming settings. Treat the key like a password: do not include it in a screen recording, public document or message, and use YouTube’s reset process if you think someone else has it.
The stream key connects OBS to the YouTube broadcast destination; it is not a playlist setting. Select the appropriate service and enter the details carefully. If you have multiple keys, label your notes without exposing the key itself, so that you can distinguish a property-tour broadcast from another channel setup without accidentally sending the wrong output.
Prefer RTMPS where it is available, following YouTube’s current encoder settings guidance. YouTube recommends constant bitrate (CBR) and a two-second keyframe interval, with the interval not exceeding four seconds. Choose a supported codec, resolution and bitrate that your computer and internet connection can sustain. Do not select a high output setting simply because one source file has a high resolution; the stream must be encoded and uploaded continuously.
YouTube’s streaming tips recommend keeping upload bandwidth headroom rather than using all of the available connection for the broadcast. Their current guidance calls for 20% headroom. Test on the connection you will use for the event, and account for other devices sharing it. A connection that looks adequate in a speed test can still be affected by household or office uploads while you are live.
The basic OBS encoder workflow is appropriate for sending a local MP4 playlist. YouTube also documents HLS as an ingestion option, but it involves different configuration and greater latency; it is not necessary for this desktop playlist walkthrough. For a separate prerecorded-video channel workflow, our article on turning existing YouTube uploads into a 24/7 live channel discusses a different starting point.
Preview audio and video before going live
Start the encoder from OBS early enough to let YouTube receive the signal, then inspect the Live Control Room preview. For a scheduled event, sending the signal is not necessarily the same as making the event public: review the preview and use the Go live control in YouTube when you are ready. YouTube recommends testing ahead of the event; its streaming tips include starting the encoder before the event so you can check the stream.
Check the picture for the first clip, a clip boundary and the playlist restart. Confirm that the important parts of each room remain visible in the YouTube preview, not just in OBS’s canvas. Listen to the preview as well as watching it: confirm speech is intelligible, music is not unexpectedly loud and no source is muted. The preview is the place to catch a wrong scene or missing source before viewers encounter it.
Keep an eye on OBS’s status and YouTube’s stream health while the broadcast is running. If the preview fails to appear, check the stream key, destination, network connection and encoder settings in a measured order. Avoid changing several settings at once, since that makes it harder to identify which change resolved the issue. If a scheduled stream is not ready, pause and troubleshoot rather than assuming that a successful local preview means YouTube is receiving it.
If the computer is also responsible for playing the files and encoding the stream, it must stay on and connected for the broadcast. Avoid sleep or automatic shutdown during the session, and do not move the source files. This desktop route gives you direct control over playback, but it also leaves the computer, VLC visibility and network connection in the chain that needs attention.
StreamNeo removes the need to leave that Ubuntu computer running for a file-based broadcast: you upload the video, connect your YouTube stream key, and the channel runs from the cloud with monitoring and automatic restarts if it drops. It is useful when keeping a local machine awake and connected is the specific burden you want to remove; it is YouTube-only and does not replace your checks on footage, permissions or the live preview.
When you finish, end the broadcast in YouTube Live Control Room and stop streaming from OBS. YouTube says streams shorter than 12 hours are automatically archived, but check the current encoder guidance for the handling that applies to your planned duration. Do not assume that an archived live stream is a substitute for retaining the original MP4 files and your own working copies.
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 YouTube play a playlist of MP4 files from my Ubuntu computer?
Not directly in this workflow. OBS plays the local files through its VLC Video source and sends the resulting output as an encoder stream to YouTube Live. YouTube receives the broadcast, while the playlist order and loop behaviour are set in OBS.
Why is VLC Video missing or unable to play files in OBS?
The source depends on VLC being installed and available to OBS, and OBS documents that 64-bit OBS needs 64-bit VLC. Check the current installation instructions for both applications and whether your chosen package route allows OBS to access VLC. Then test one MP4 before adding the full tour sequence.
Will the MP4 files switch without a gap?
Do not assume so. The result can depend on the files and their encoding, so play the entire playlist in OBS and inspect transitions and audio, including the loop back to the first file. If a pause or visual change is noticeable, revise the sequence or prepare the files differently before the scheduled stream.
Do I need to click Go live after starting OBS?
For a scheduled broadcast, start OBS so the signal reaches YouTube, inspect the Live Control Room preview, and then use YouTube’s Go live control when you are ready. Confirm the current YouTube interface and instructions before the event, as labels and eligibility requirements can change.