Multistream editing

Multistream editing loads more than one Twitch VoD into the same editor session, lined up on a shared timeline. Every loaded streamer keeps their own video, chat, activity graph, and overlay render — but the playhead, the in / out brackets, and the timeline ruler are shared across all of them.

The feature is built for collabs, raids, GTA RP scenes, tournaments, charity events, and any moment where two or more streamers were live at the same wall-clock time.

Loading angles

Open /sync/new to start a session. The picker takes a list of Twitch VoD URLs or IDs, looks up overlap on the recorded_at timestamps, and lets you confirm the participating angles. The session lands at /sync/[ids] where ids is a list of the VoDs in the workspace. Each VoD is fetched the same way a single-VoD session is fetched — the video pipeline downloads HLS segments to S3, the chat pipeline downloads chat into Postgres (with the raw gzipped JSON kept on S3 as an archive), and you can watch the progress bars per angle.

There is no hard cap on angle count. Add as many streamers as were live for the event.

How angles are synced

Every Twitch VoD carries a recorded_at timestamp — the second that streamer went live. Multistream anchors each VoD to its own start, lines them up on one wall-clock timeline, and the overlap between them becomes the editable region.

The sync runs entirely in the browser. The code lives in the front-end editor, not in the worker. There is no manual offset slider and no server-side audio or chat-spike alignment pass — the Twitch timestamps are taken as ground truth and they are accurate to the second.

If a VoD does not overlap with the anchor VoD at all, the editor warns you and skips it.

The shared timeline

The activity graph stacks one row per angle, all on the same time axis. Where one streamer's chat spikes is rarely where another streamer's spikes — that contrast is the signal you are scanning for.

• Click anywhere on the shared timeline to seek every angle at once.
• Drag to bracket a clip. The in / out points apply across all loaded angles.
• Mute a row with the eye icon to remove it from consideration without unloading the VoD.
• Each row has its own filter chips, emote filters, and auto-highlight scanner.

The Twitch player thumbnail of the currently active angle plays in the preview area. Press 1, 2, 3… to switch which angle is in the preview without moving the playhead.

Clipping across angles

When you confirm a bracket with Clip, vod.ing cuts every loaded angle at those in / out points. You get one Clip row per angle, grouped under a single clip moment on the Clips page. Each angle is rendered independently — including its chat overlay if you tick the box per angle.

Per-angle chat overlay rendering means you can ship a clip where streamer A's POV is the main video and streamer B's chat is the overlay (or any other combination). Pick which angle's chat goes with which angle's video on the Clips page before promoting to the timeline maker.

Exporting to DaVinci Resolve

A multistream clip group exports as a multi-track FCPXML.

• Angle 1's video lands on V1, its chat overlay on V2.
• Angle 2's video lands on V3, its chat overlay on V4.
• Angle 3 → V5 / V6, and so on.

Every track is aligned to the same shared timecode so DaVinci opens the project with each angle stacked at the correct offset. From there, the normal multi-cam workflow applies: disable tracks to cross-cut, enable two at once for a split-screen, or right-click the assembled angles and pick New Multicam Clip to build a true multi-cam source from them.

The media bundle on the export page lists every clip MP4 and every chat overlay MOV across every angle. Download all of them into one folder alongside the .fcpxml before opening the project.

Plan gating

Multistream is available on all paid plans. Angle count is not gated by tier. The combined download and storage of multiple VoDs counts against your normal plan budget — a four-angle session loads four VoDs into S3, so plan accordingly if you load many long streams.