How to rehearse an AI live stream in OBS

Start with one video source, one safe fallback scene and a local recording. This walkthrough helps you find out what happens when generation falls behind before you put a show on air.

Pick the job the generated video will do

Choose one moment the audience will notice. A host cues a visual when introducing a new topic, a moderator approves a prompt for the next scene, or a camera gets a stylized treatment during a short segment. Write down who creates the input, what counts as a usable result and how long the host can keep the segment moving while it arrives. A rehearsable goal is “the host can introduce the next scene while the producer prepares it.” It gives you a clear moment to measure and a way to tell if a delay will matter.

This workflow works with a local clip first. Use media you own or have permission to show. A test recording can stand in for the first generated clip, and a second short recording is enough to simulate an update. You can learn how the show behaves before signing up for an API, buying compute or sending camera footage to an outside service.

Choose the right OBS source

Camera or AI effect. Add a Video Capture Device for a direct camera feed. If a tool such as FasterLivePortrait reads the camera itself, use Window Capture on Windows or macOS Screen Capture in window mode to capture its generated preview. Check the operating system’s screen recording permission if the preview is black. Use a still or a local clip for the fallback if OBS and the effect cannot open the same camera at the same time.

Browser overlay. Add a Browser Source, paste the overlay URL and set its width and height to the overlay’s intended size. Test transparency, cropping and visibility before adding a service such as StreamRio. Keep service-generated overlay URLs private if they contain an access token.

Prepared AI video. Add a Media Source, enable Local File and select the clip. Enable Restart playback when source becomes active if a scene cut should start the clip from the beginning. Turn Loop on only if you want it to repeat. Monitor and record a short section to catch duplicate audio capture before the rehearsal.

Live captions. Decide where viewers should get captions. A caption overlay captured in a scene appears in the video. For selectable subtitles, check whether your delivery platform offers a separate caption track. Mux Live Captions is one documented option. In a private stream, turn captions on in a separate viewer and compare their timing with two short spoken lines. Verify that the stream has one clear microphone path first.

Try a two-scene rehearsal with a test overlay

  1. Create a scene named Program and add a program card, your own short clip or a color source as the background. Add a Browser Source above it using the test overlay URL. Set the source size to 640 × 120, then move the overlay to a corner.
  2. Check that the background shows around the rounded card and the blue bar moves. The overlay uses a simple CSS cue and has no audio. If it displays in your browser but OBS is blank, check the URL, source visibility and layer order, then refresh its cache from the source properties.
  3. Create a separate Fallback scene containing a still or a local clip. Start a local recording, read a short sentence using one microphone source, switch to Fallback and then return to Program. Use the recording to check that the overlay returns, speech stays audible and the cut never exposes a private window.

Build two scenes and test the cut

Set up OBS using its official Quick Start Guide. In your programme scene, add the generated-visual placeholder and any on-screen explanation viewers need. A producer who already has a hosted view can test it using a supported capture source for that computer. Pick a source you can inspect in preview and avoid capturing windows that may reveal credentials or private messages.

Build a fallback scene that makes sense even if viewers arrive halfway through an interruption. It can keep the host on camera, show a simple program card or play a prepared clip. Keep speech audible and set the fallback’s audio level alongside the incoming scene. Start a local recording. Play the first clip, switch to the fallback without warning, then return when the second clip is ready. Watch the recording with sound. Look for a blank frame, a duplicated audio track or a visible pause that nobody on the team knew how to fill.

Keep completed output in a queue

For clip-based formats, put approved output in a small queue before it reaches the program scene. A clip becomes ready when it opens and plays, audio is understood and an operator has checked the content. Start a rehearsal with a short wait between finishing and showing it. This gives the producer room to catch a mislabeled clip or replace one that does not fit the segment. Make a simple note for each item describing its approved prompt, playback order and fallback if it fails.

Next, simulate a timeout. Keep the prepared clip in preview until it is actually ready and see whether the host can finish the setup smoothly from the fallback scene. If playback is already running, decide before the show whether to extend the segment, fill with a prepared clip or move on. For a continuous effect instead of clips, the equivalent test is to disconnect the effect source and cut to the clean input. The Daydream listing explains this rehearsal for a camera effect and identifies access checks you would still need to make.

Measure handoff times and costs

Record the time the producer approves the input, the time output is ready to play, the time it is visible in the OBS recording and, if you have a private test stream, the time it appears in a separate viewer. A stopwatch or an on-screen timestamp is enough for a first run. When a test uses two devices, start from a shared clock or record both views in the same frame so the timestamps are comparable. Collect several trials after a cold start and again once the flow settles.

Keep failures alongside the successful times. If a ten-second scene arrives after you have already moved on, mark it as late even when the file eventually looks fine. In a private stream, troubleshoot delivery separately from generation. If local output looks healthy and the remote player continually interrupts, check the encoder and connection. OBS documents how to investigate network dropped frames and unstable connections.

If you use a paid service in a later rehearsal, write down what it charges for. A service might bill completed jobs, generated seconds or the time a live session remains open. Divide the total rehearsal cost by minutes of usable material that went into the programme and keep that figure beside the service’s stated unit price. It captures the effect of retries and unused output. Use your own observed invoice or usage records before estimating a full show’s costs.

Know when to go live

Rehearse the handover between the host and the person approving output. Decide who monitors the public feed, how an unsafe prompt is removed and who can cut to the fallback while the problem is investigated. A practice audience can consist of one trusted viewer on a separate device. Ask them to identify when the generated scene arrived and whether the interruption made sense. For an audience-directed show, see the guide to multiplayer AI video before deciding how much control to give viewers.

At the end, save the OBS recording and a short log. Note what the operator could recover from, what a viewer saw and which part of the system needs another rehearsal. If the queue still empties too quickly, shorten the interactive segment or schedule more prepared material. Once a delayed input and a failed output both have a clear on-air response, you have a better basis for deciding whether to add a real generation backend.