MediaCopilot

MediaCopilot is Cires21's AI media-operations product. It turns video assets into transcripts, subtitles, dubbed audio tracks, automatic clips and enriched metadata. C21 Live Control integrates with MediaCopilot by handing off finished Recordings — or clips cut in the Recordings Editor — as a post-stream export.

The combination covers the full content lifecycle: C21 Live Control runs the live operation and produces the Recording; MediaCopilot turns the Recording into searchable, multilingual, clip-ready assets.

Prerequisites

Two prerequisites apply before this integration can be configured:

1. A MediaCopilot account. MediaCopilot is a Cires21 product contracted separately from Live Control. The account, its tenant URL and the API token used by Live Control are provisioned by Cires21 as part of the service contract — there is no self-service signup that connects to Live Control. Contact your Cires21 representative to provision a MediaCopilot tenant for your installation.
2. The C21LiveEditor license on the Live Control instance. The Recordings Editor — the surface that cuts a clip from a finished Recording and pushes it to MediaCopilot — is gated by the C21LiveEditor license. Without it, the Editor tab is hidden from Recordings and the integration cannot be used from the UI. See Licenses for the license model.

What gets sent

The unit of transfer is a Recording (or a clip extracted from a Recording through the Recordings Editor) — never live frames. The export triggers from the Editor's export panel once the Recording reaches a terminal state (its ended_at is set, that is, the Live stream that produced it has stopped).

The asset that lands in MediaCopilot carries:

• The Recording file (the container is chosen on the Editor's Output encoding picker — one of ts, mp4, fmp4, audio).
• A sidecar JSON with the source Live stream identifier, the encoder Device identifier, the started_at / ended_at timestamps and any operator-supplied metadata.
• The available qualities captured for that Recording.

MediaCopilot processes the asset asynchronously and returns transcripts, subtitle files (VTT, SRT, STL), dubbed audio tracks, generated clips and enriched metadata.

Hooking it up

The bridge is configured under Integrations → MediaCopilot. A System Administrator:

1. Receives the tenant URL + API URL + API key from Cires21. These are issued when the MediaCopilot service is contracted; Live Control does not provision them itself.
2. In Live Control, opens Integrations → MediaCopilot. By default the integration points at the public MediaCopilot SaaS endpoints; turn on the Custom endpoint toggle only if you need to point at a staging tenant or a proxy.
3. Pastes the API Key (the bearer token).
4. Saves.

The form exposes three fields (URL, API URL, API Key) plus the Custom endpoint toggle that controls whether the first two are editable. Once the integration is saved, MediaCopilot becomes a selectable export target in the Recordings Editor.

The flow

The hand-off is operator-driven from the Editor:

1. The Live stream produces a Recording because one of its configured destinations is of type Record. The Recording can still be in progress or already closed — the Editor opens either state.
2. An operator opens the Recording in the Recordings Editor, sets in/out marks if a clip is desired, picks MediaCopilot as the export target in the export panel and submits.
3. Live Control runs the cut and posts the resulting asset (with the sidecar metadata) to the MediaCopilot ingest endpoint. The token configured on the integration authorises the call.
4. MediaCopilot picks up the asset, places it in the configured collection and runs its processing pipeline (transcription, subtitling, dubbing, clip generation, metadata enrichment — depending on the template).
5. Output assets become available through the MediaCopilot UI and API. Live Control retains a reference to the MediaCopilot asset id on the original Recording so an operator can jump between the two.

The transfer is asynchronous: the asset is available locally on Live Control immediately; the MediaCopilot output becomes available when its pipeline completes, typically within a small multiple of the Recording's duration.

Cross-links

• Recordings — How a Recording is produced.
• Recordings Editor — Cut a clip from a Recording and choose MediaCopilot as the export target.
• Licenses — The C21LiveEditor license that gates the Editor tab.
• Cut a clip in the Editor and send it to MediaCopilot — Step-by-step how-to.

FAQ