You rotate product comparison videos by sending YouTube Live a continuous feed from an encoder that plays your files in sequence. YouTube Live is the destination for that feed; it does not take a playlist of uploaded videos and rotate them for you.
You can run the encoder on a computer with OBS or use a hosted playout service. The first gives you direct production control but depends on your equipment and connection staying available; the second can keep playing without your computer on, but its controls, costs and availability need checking.
How prerecorded videos become a live feed
A live stream is a real-time video and audio signal sent by an encoder to YouTube. In this case, the pictures and sound are prerecorded, but the encoder still sends them as a continuous broadcast. The playlist belongs to the playback workflow, not to YouTube Live.
The encoder reads a file, sends its frames and audio, then moves to the next file or returns to the beginning of the sequence. If that process stops, the feed can stop or become unhealthy even though the files remain available on your computer. A successful upload to YouTube is not the same thing as a functioning continuous stream.
You create or schedule a broadcast in YouTube Studio’s Live Control Room, then configure the encoder with YouTube’s stream URL and a private stream key. YouTube’s encoder setup instructions explain where those values go. The encoder sends the feed to the destination; it does not transfer ownership of your playlist to YouTube.
This distinction helps with troubleshooting. If the live preview is black, investigate the encoder’s source and output as well as YouTube’s receiving status. If one video plays but the next does not, look at the playlist software and the files’ transitions. For background on the connection itself, see this plain-language explanation of RTMP.
Prepare a comparison-video sequence
Start by deciding what viewers should learn from the rotation. A useful sequence might introduce the products, compare one or two specific features, summarise the trade-offs and then return to the opening. Put the most useful context in the video itself: people may join midway and cannot be assumed to have seen the preceding comparison.
Make each file understandable on its own. Identify the products and the basis of the comparison on screen or in narration. Keep prices, availability and product claims current, and date information where that helps viewers judge it. A video that loops for weeks can outlive a sale or a product revision, so schedule a review of the files rather than treating the first upload as permanent.
Before adding files to the sequence, watch and listen to each one from beginning to end. Look for damaged sections, missing audio, accidental blank frames, abrupt volume changes and overlays that obscure the product. Check that the audio is present in the exported file, not just audible in the editing project. A file that plays correctly in an editor can still behave differently in the playout application.
Use consistent resolution, aspect ratio and audio layout where practical. The goal is not to claim a particular configuration guarantees acceptance; it is to reduce avoidable changes at file boundaries. If one video has a very different frame rate or audio arrangement, test that transition closely. Make a written playlist in playback order and keep a copy of the final files and their names so you can identify a bad item quickly.
Think about the loop as a programme, not just a folder. Avoid putting two nearly identical product segments next to each other if that makes the rotation feel repetitive. Use short title cards or spoken transitions to explain what is changing, and avoid long black or silent gaps between segments. For a channel that also rotates its presentation, this guide to rotating stream titles and thumbnails covers the separate channel-page task.
Choose local OBS or hosted playout
The central question is who is responsible for keeping the encoder feed running. With local OBS, your computer, power, operating system, internet connection and OBS process all matter. With hosted playout, the provider runs the playback workflow, while you remain responsible for the content, configuration and monitoring. Neither choice removes the need to test.
| Decision | Local OBS | Hosted playout |
|---|---|---|
| What must remain available | Your computer, power, connection and encoder | The provider’s service and your configured stream; your computer need not stay on for playout |
| Production control | Direct access to OBS scenes, sources, overlays and live switching | Controls depend on the provider’s current features |
| Work to maintain | Updates, sleep and restart settings, local files, resource capacity and connection | Uploads, playlist setup, service configuration, monitoring and cost |
| Often suits | An operator who wants hands-on control and can maintain the local setup | An operator who wants prerecorded playback without leaving a dedicated PC running |
| What to verify | That the machine can play the sequence and send the feed reliably | Current playlist features, recovery controls, limits, support and total cost |
OBS is useful when you want to switch scenes, add live graphics or take direct control during the broadcast. You can test available media-source or playlist workflows and decide whether your production needs scenes or automation. The trade-off is that a local setup inherits local failure points. A power cut, operating-system restart, network fault or accidental shutdown can interrupt the feed.
Hosted playout shifts the continuous playback work away from your own computer. That can be practical if you do not want a PC running through the night, but hosted does not mean failure-proof. Check how the service handles a failed file, a dropped connection, playlist edits and restarting a broadcast. Also check its current cost and whether its controls fit the way you need to update comparisons. A service’s own documentation can establish its stated features, not independent proof of reliability.
If you choose a local machine in India, include the electricity and network arrangements in the operating plan, rather than considering only the software. This guide to the electricity cost of running OBS continuously in India discusses the power side. If you choose hosted playout, compare the service cost and the work it removes from your routine; do not assume that a cloud label alone settles the decision.
Connect the encoder to YouTube Live
First check the channel’s current live-stream eligibility and activation status in YouTube Studio. YouTube’s live-streaming help page describes account requirements and restrictions. Activation can take time for a channel that has not streamed before, so confirm the channel is ready well ahead of a planned launch rather than discovering the issue at the start time.
In Live Control Room, create or schedule the stream and obtain the stream URL and key for the encoder workflow. Enter these in the encoder’s broadcast settings, then select the playlist or scene that supplies the video. Keep the stream key private: anyone who obtains it may be able to send a feed to the configured destination. Do not put it in a public document, screenshot or tutorial, and regenerate it if you believe it has been exposed.
Before going live, confirm that the encoder is using the intended source and that the output includes both picture and sound. Start the feed and check YouTube’s preview and stream-health information. Make sure the picture is not cropped, text remains legible and audio is audible without distortion. Stream health is a useful signal about what YouTube is receiving, but it does not prove that every later file in the sequence will work.
If you are new to the setup, a private rehearsal or an unlisted test can help expose configuration mistakes before a public launch. Confirm the visibility setting and audience expectations before using either. Once the sequence has been tested and the broadcast is ready, switch to the intended public or scheduled mode in Studio.
Test the sequence and transitions
Do not stop testing after the first video appears. Let the encoder complete a full pass through the playlist and watch every boundary. The second file may have a different codec, frame rate or audio layout; a source that works at the start may fail only when the sequence advances. The continuous-stream workflow guide is also useful when you are considering where local files should live.
During the test, check for black frames, frozen pictures, abrupt changes in loudness, silence, unexpected aspect-ratio changes and any playback pause between files. Listen on the kind of device your audience is likely to use as well as headphones. Read on-screen labels at normal viewing size, particularly product names, prices and comparison claims. If a transition is intentionally quiet, make it clear enough that viewers do not mistake it for a fault.
Test the recovery path too. Practise removing or replacing a defective file, restoring the intended order and restarting playback. If the encoder loses its source, know what viewers will see and how you will restore the feed. In a local setup, also check that sleep settings, updates or a scheduled restart will not interrupt an overnight run. In hosted playout, learn which controls are available to you and whether a playlist change affects the active broadcast immediately.
Write down the working settings and the order of files. A short operating note can identify which playlist is current, who can access the channel and what to check if the feed stops. The aim is to make ordinary maintenance repeatable, not to assume the stream will need no attention once it begins.
Plan for interruptions and recovery
A nonstop broadcast has dependencies even when the videos are prerecorded. Local operation depends on power, the computer, the encoder software and network connectivity. Hosted operation depends on the provider’s playout and on a working configured connection to YouTube. In either case, content files can fail, a key can be changed, or the broadcast can be interrupted for reasons outside your direct control.
Decide in advance who will notice a problem and what they will do. Keep a way to check the public playback and the Live Control Room status. If there is a failure, determine whether YouTube is still receiving a feed, whether the encoder is playing, and whether the problem is limited to one file. Avoid making several changes at once: identify the failing point, restore a known-good source and confirm the receiving preview before leaving the stream unattended again.
For local OBS, check power arrangements, network stability, automatic sleep, operating-system updates and whether the computer can run the workload without becoming unstable. For hosted playout, check what monitoring and restart controls are actually provided, and how you can reach support. These are operational checks, not a guarantee that a stream will remain live. Keep a clean copy of the approved playlist so recovery does not depend on reconstructing it under pressure.
Consider how you will handle a longer interruption with viewers. A pinned message or channel update can explain that the feed is being restored, if you have a way to publish one. A restart may create a new broadcast or archive behaviour that differs from the original session, so check what Studio shows rather than promising that a replay will remain continuous. For a stream planned to run beyond a day, review YouTube’s current guidance on streams ending after 12 hours.
Understand policy and archive constraints
A comparison channel should treat rights and product disclosures as part of production. You need appropriate rights for music, footage, product imagery and other material in each prerecorded file. The fact that a segment is prerecorded or part of a loop does not remove those responsibilities. YouTube identifies copyright strikes and matches with another copyrighted live broadcast as possible reasons for live-stream restrictions; review its current live-stream restrictions guidance before relying on an old workflow.
Product comparisons also need careful, supportable claims. Make clear what you tested and avoid presenting a limited experience as a universal result. Where a video includes paid product placement or an endorsement, YouTube says its restrictions on paid promotions apply to live streams as well. Check YouTube’s current rules and the disclosure obligations that apply to your own jurisdiction and commercial relationship. The relevant legal wording can depend on those details; this article cannot determine it for every creator.
Do not treat a continuous prerecorded loop as automatically approved or automatically prohibited. The available platform guidance does not settle that blanket question. Review current Community Guidelines, Terms of Service and any applicable monetisation rules for the channel and content you plan to publish. A channel’s acceptance, monetisation status or eligibility should not be inferred from the fact that its encoder can send a feed.
Archive behaviour is another separate question. YouTube’s encoder guidance says streams under 12 hours are automatically archived; it does not establish that one longer, nonstop session will be archived indefinitely. If the replay matters, check what Studio currently offers for the planned broadcast and make your own recording where you have the rights and capacity to do so. Do not rely on a livestream archive as your only copy of a product demonstration or disclosure record.
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 YouTube Live rotate my product videos for me?
No. YouTube Live receives the continuous feed sent by your encoder; your local playback software or hosted playout workflow supplies the videos in order. Set up and test that sequence before relying on it for a public stream.
Can I use OBS to rotate several prerecorded videos?
Yes, OBS can be part of a local workflow for prerecorded playback, but the exact source or playlist method depends on your setup and available software. Test a complete rotation, including audio and transitions, and account for the computer, power and connection needing to stay available.
Does a hosted playout service guarantee the stream will never stop?
No. Hosted playout means your own computer does not need to remain on for playback, but it does not remove every failure point or guarantee uninterrupted delivery. Check current controls, recovery options and service terms, then monitor the broadcast.
Will YouTube archive a nonstop stream for viewers to watch later?
YouTube’s encoder guidance says streams under 12 hours are automatically archived, but that does not establish indefinite archiving for one longer session. Check the current behaviour in Studio and keep a separate recording if you need a dependable copy.