For editors and post houses
Tag AI as you cut, inside Premiere.
The plugin docks beside your timeline. Every tag records where the use starts, where it ends and how long it runs, then syncs into Audiovisual AI Log — so the production’s record gains the edit’s own detail, down to the frame, alongside everything the crew reports.

A lot of AI enters a production after the shoot ends.
The crew can report what they used on set and in prep. They cannot report what happened in the edit, because they were not there. The editor is the only person who sees this class of AI use, and it is the class most likely to reach the delivered master.
Generative extend
A shot is a few frames short, so the tail is generated.
Speech enhancement
A noisy location take is rebuilt into a usable one.
Masking and rotoscoping
A subject is isolated automatically instead of by hand.
Upscaling
Archive or phone footage is brought up to delivery spec.
Generated plates and stills
Backgrounds and inserts arrive from a generative tool.
Transcripts and subtitles
Dialogue is transcribed, then cut against, then delivered.
None of this is unusual, and none of it is a problem in itself. It just needs to be written down by the person who did it, at the moment they did it. The plugin adds that layer on top of the crew survey — the same production record, with the edit filled in.
Why the file’s own provenance isn’t enough
It sits next to the timeline, not in another browser tab.
The editor selects a clip, picks what the AI did and which tool did it, and saves. That is the whole interaction. The panel reads the rest — the clip name, its position in the sequence, the sequence frame rate — from the project itself.

The part that can’t be reconstructed later
Every entry carries a timecode, in and out.
The crew’s survey answers tell you what was used and how the work was made. A tag on the timeline adds the frame-level detail only the sequence can give: this use runs from 00:01:24:02 to 00:01:30:22 — six seconds and twenty frames, on this clip, in this sequence — and it is in the cut, because the tag is attached to a shot that made it there.
That difference matters when someone asks a narrow question. A distributor querying one sequence, an insurer asking what reached the master, a broadcaster asking whether a specific shot was generated — all of those are answerable from a timecoded record and guesswork without one.
Tags sync straight into Audiovisual AI Log, into the same production record the crew are already filling in. The editor’s entries sit alongside what the shoot reported, so nobody has to stitch two systems together at delivery.
- Start, end and duration for every tagged use
- Written down as the edit happens, with the sequence open
- Attributed to the editor who did the work
- Added to the crew’s survey answers, not a replacement for them
00:00:07:1500:00:16:239s 08f
Generative extend · Firefly
A001_C003_0922FR_001
00:01:24:0200:01:30:226s 20f
Speech enhancement · Adobe Enhance
A004_C011_0923MK_003
00:02:38:1900:02:42:073s 12f
Generated plate · Runway
GFX_city_plate_v4
In the final cut — the tag sits on a shot that made the edit
It can learn how your post house already names things.
Most facilities already encode a lot in a filename. A suffix for an upscale, a prefix for a generated plate, a folder that only ever holds synthetic voice. That convention is different at every house, and it is usually followed more reliably than any paperwork.
So the plugin should read it rather than ignore it. Teach it your patterns once and it proposes the right tag when a matching clip is selected, turning a form into a confirmation. The editor still approves every entry, and can override any of them.
Why suggestions, and never automatic tagging
GFX_city_plate_AI_v4.mov
Suggests Generated plate
A004_C011_UPRES_4K.mov
Suggests Upscaling
VO_scratch_ELEVEN_02.wav
Suggests Synthetic voice
The editor confirms or corrects every suggestion. Nothing is logged without a person agreeing to it.
The practical questions
The things post houses ask us first.
How do we get it?
Talk to us. We set the plugin up with each post house ourselves, so it matches how your projects are organised, and so the productions you cut are already connected on the Audiovisual AI Log side.
Which host application?
Adobe Premiere Pro, as a panel that docks alongside your existing workspace. Other edit systems follow the same idea, and Premiere is where we start.
Does it send our media anywhere?
No. It reads the names, positions and timecodes of what you tag. Your footage never leaves the edit suite.
Who controls the connection?
The editor connects with a key issued from the production’s Audiovisual AI Log account, scoped to that production and revocable at any time.
What if the suite is offline?
Tagging keeps working. Entries queue locally and sync as soon as the machine is back on the network.
Want this in your edit suite?
Getting the plugin starts with a conversation — how you cut, how your projects are named, and which productions it should report into. Leave your email and we’ll take it from there.
A real person reads every message.
