Anjin Media

Output and control

Know where every moment came from.
Keep the edit accountable.

Every selected segment remains connected to the source recording, time range and plan version that produced it, making review and reuse more dependable.

One video or an entire archive.

Source provenance product demonstration

Source provenance

Source provenanceLINEAGE VIEW
Episode 03 · A
Episode 03 · B
HOOK28:05–28:20
BODY27:21–27:35
CLOSE27:07–27:16
Source-grounded vertical podcast edit with traceable timecodes

RENDER V1

source_groupstart_msend_mscameraep0316850001700000A

What is source provenance in AI video editing?

A traceable record connecting rendered segments to the original media and editorial decision.

Cut segments record source timecodes and references. Render results retain the plan version and provide structured edit-decision information.

Controls and evidence

See what the system used and produced.

Useful automation leaves something a person can inspect. Anjin keeps the edit connected to its brief, source media and output settings.

SOURCE PROVENANCEVERIFIABLE OUTPUT
source_group
The recorded session from which a moment was selected.
timecodes
The start and end range inside the original source.
angle
The camera source used where multi-angle media is available.
plan_version
The reviewed editorial plan used for rendering.

Why it matters

More control, less timeline work.

01

Verify quotations

Return from a selected statement to the exact recorded context.

02

Review with confidence

Inspect what the system used instead of accepting an unexplained output.

03

Reuse responsibly

Keep source identity attached as moments move into new edits and systems.

Fit and boundaries

Use the capability where it genuinely helps.

Anjin is strongest on speech-led recorded material where the editorial job can be described clearly and every selected moment needs to remain verifiable. It supports human judgement with searchable evidence, a reviewable plan and structured outputs.

A strong fit

Recorded knowledge with a story inside it

Interviews, podcasts, webinars, discussions and archive programmes benefit when the useful material is distributed across a long recording or several selected sessions.

Keep elsewhere

Final craft and image-led montage

Detailed colour, sound design, motion graphics and wordless visual storytelling remain finishing tasks for a professional editor and their preferred creative tools.

Evaluation checklist

What should you verify before adopting source provenance?

CHECK 01

source_group

Confirm that the workflow exposes this clearly: the recorded session from which a moment was selected.

CHECK 02

timecodes

Confirm that the workflow exposes this clearly: the start and end range inside the original source.

CHECK 03

angle

Confirm that the workflow exposes this clearly: the camera source used where multi-angle media is available.

CHECK 04

plan_version

Confirm that the workflow exposes this clearly: the reviewed editorial plan used for rendering.

Questions about source provenance

What can I trace in an Anjin edit?
You can trace planned segments to their source group, source time range and, where applicable, speaker and camera angle.
Why does plan version matter?
It identifies the exact reviewed structure used for a render, even when later revisions create newer plans.
Does provenance prove a claim is true?
No. It proves where recorded material came from. Editorial and factual verification still require human judgement.
Can provenance data be used through the API?
Yes. Structured plans and result sidecars support programmatic review and downstream workflows.

Use source provenance in your next edit.

Start with footage you already have and a clear description of the result you need.

One video or an entire archive.