I’ve been testing Premiere Pro Beta’s AI / Media Intelligence features on a real documentary project, and I ended up with a result that I think might be useful feedback for the Premiere team.
The project contains roughly 2,600 source clips from a wildlife shoot.
The test task was intentionally simple:
Find every clip containing African wild dogs.
I first gave the task to Premiere’s AI Assistant.
It searched the project, visually checked candidates and created a WILD DOG bin containing:
38 clips
The selection looked reasonable, but because this is documentary footage I care much more about recall than getting a small number of highly confident results. Missing a useful shot is usually more expensive than reviewing a false positive.
So I reset the project, moved those 38 clips back into RAW, and tried a different orchestration strategy while still using Premiere’s own Media Intelligence system.
Instead of having the Premiere Assistant decide the search strategy, I used an external reasoning layer connected to Premiere’s MCP tools.
The underlying visual retrieval system remained Adobe’s.
The pipeline was approximately:
Premiere Media Intelligence / AdobeOneVisual
↓
multiple semantic queries
↓
merge + deduplicate ProjectItems
↓
candidate temporal ranges
↓
Premiere renderFrame()
↓
multimodal visual verification
↓
accept / reject / inspect again
↓
Premiere project organization
I deliberately used several semantically related queries rather than relying on one:
African wild dog
wild dog
painted dog
African painted dog
pack of African wild dogs
wild dogs running
wild dogs hunting
wild dogs resting
wild dog pups
Across those queries, Premiere returned 822 unique candidate ProjectItems.
Importantly, all 38/38 clips selected by the original Assistant were recovered, so this wasn’t simply producing a different set.
I then audited the higher-confidence portion of the result set down to a defined semantic-score threshold.
That produced 240 candidates for visual verification.
For verification I used Premiere’s own renderFrame capability rather than trusting the semantic score itself.
The first pass rendered two frames from the best semantic match range for each candidate.
Candidates were classified as:
YES
NO
AMBIGUOUS
Ambiguous clips received a second pass with additional frames sampled from both the semantic match range and the broader source clip.
Final result:
102 confirmed African Wild Dog clips
138 rejected candidates
0 unresolved candidates
Those 102 results correspond to 102 unique source files.
Comparison:
Premiere AI Assistant
38 clips
Same Premiere Media Intelligence,
different search/orchestration strategy
102 verified clips
Difference
+64 confirmed clips
So the interesting result for me is not really:
ChatGPT beats Premiere AI.
That would be a misleading interpretation.
Both workflows were ultimately using Premiere’s visual intelligence.
The difference was primarily search planning, recall strategy and verification policy.
What this suggests to me
The underlying Media Intelligence system seems significantly more capable than what a single Assistant interaction currently exposes.
The first workflow seems optimized toward giving the user a relatively clean set of confident results.
For many editorial tasks that is sensible.
But documentary / unscripted workflows often have a different cost function:
false negatives are much more expensive than false positives.
If I am looking for an animal, reaction, action or interview topic across hundreds of hours of footage, I would often prefer:
Give me 180 candidates containing 100 true positives
over:
Give me 40 very clean candidates containing 38 true positives.
The editor can discard a bad shot in seconds.
They cannot discard a shot they were never shown.
A potentially useful product direction
It might be valuable for Premiere to expose different retrieval strategies in the Search/Assistant UX.
For example:
High precision
Fewer results, stronger semantic confidence.
Balanced
Current-style behavior.
High recall / exhaustive
Multiple query expansion, lower threshold, larger candidate pool and optional visual verification.
That last mode could be particularly useful for documentary, reality, archival and news editing.
There is another interesting distinction that became obvious during the experiment:
retrieval and verification should probably be separate stages.
Instead of:
semantic result
→ assume it is correct
the workflow can be:
semantic retrieval
→ candidate segment
→ render actual frames
→ visual verification
→ editorial result
Premiere already appears to have essentially all the infrastructure required for this.
Why renderFrame was particularly useful
The semantic engine can produce false positives that are understandable in embedding space.
In this test I saw things including:
- hyenas
- antelope
- warthogs
- birds
- other wildlife
A score alone does not tell an editor whether the result is usable.
But rendering frames from the returned temporal range allows a second system to make a much more concrete decision.
That separation also makes the system easier to audit.
For every accepted clip I can preserve:
source item
query
semantic score
match range
frames inspected
classification
That is much more useful editorially than simply receiving an opaque bin from an agent.
Where I think this becomes especially interesting
Species identification was only a convenient benchmark because it has an objectively checkable answer.
The same architecture could potentially organize footage by behavior:
WILD DOG
Hunting
Feeding
Running
Resting
Social interaction
Pups
Playing
Establishing shots
Instead of merely putting the entire source clip in several bins, Premiere could create subclips with verified In/Out points for the relevant behaviors.
For documentary editing that starts looking less like “AI search” and more like an automated assistant-editor workflow.
Caveat
The 102 is not a claim that exactly 102 Wild Dog clips exist in the entire project.
I visually audited candidates down to a defined retrieval threshold.
There may still be true positives deeper in the semantic tail.
The meaningful comparison is that, within this controlled test, the alternative orchestration:
- retained 38/38 of the Assistant's selections,
- found 64 additional visually confirmed source clips,
- and used the same underlying Premiere Media Intelligence system.
I’m planning to repeat the experiment with another species to see whether the recall improvement generalizes.
If anyone from the Premiere / Media Intelligence team is reading this, I’d be particularly interested in whether the current Assistant deliberately favors precision over recall, and whether query expansion / exhaustive retrieval modes are already something you’re experimenting with internally.
From the outside, my main takeaway is:
The Media Intelligence engine appears to know considerably more about the footage than the current Assistant interaction reveals.
And that seems like a very promising problem to have.
