Connect an AI live avatar to OBS

OBS is the recommended V1 bridge between LiveCanvas and a destination platform. LiveCanvas produces and monitors the avatar output; OBS composes or captures it; the operator keeps control of the destination account and final broadcast action.

Before opening OBS

Complete the Campaign preflight in Studio. The selected avatar, matching voice, six motion candidates, scene, approved facts, approved runbook, subscription, live-minute reserve, GPU worker, and output route must all be ready.

Watch the 30-second preview with sound. Do not continue if the output volume meter does not move, the face or mouth looks wrong, or Studio reports a missing audio track.

Add the Browser Source

1. Open the Session Output panel and copy the clean capture URL.
2. Add a Browser source in OBS and paste the URL.
3. Set width to 720 and height to 1280. Use the portrait workflow at 25 fps.
4. If your OBS version provides it, enable Control audio via OBS.
5. Open the source with Interact and click Enable audio when the preflight layer appears.
6. Confirm the Browser source is not muted and its meter moves during scheduled speech.
7. Make a local 30-second recording and play it back before configuring the destination stream.

The capture URL is short-lived, read-only, and revocable. It must not appear in public screenshots, support messages, logs, or shared scene collections.

Full scene and clean output

Use the full-scene route when LiveCanvas owns the background, product layout, and overlays. Use the clean or green-screen route when OBS provides the surrounding composition. Test both separately because a correct full scene does not prove that chroma key, scaling, and audio are correct in the clean scene.

Audio preflight

Browser autoplay may start video without sound. The one-time Interact → Enable audio action is intentional. Verify all four layers:

• the Worker generated speech;
• the rendered segment contains an AAC audio track;
• the output page reports non-zero browser RMS;
• OBS receives the source in its Audio Mixer and local recording.

Do not solve an OBS-only mute by restarting the GPU. Studio identifies whether the failure is TTS, media encoding, browser unlock, browser volume, or connection.

Disconnect and recovery

If the media route drops, the output page enters Safe Idle and retries while Studio reports the condition. Keep OBS open, monitor recovery, and pause or stop when the signal does not return. Fault time must not continue billable live usage.

The operator uses LiveCanvas—not OBS—to pause, resume, stop, rotate the output token, and review session settlement.

Open the complete setup guide or prepare a stream.