Warp Stabilizer causing black frames at transitions

Warp Stabilizer causing black frames at transitions

BEFORE ANYONE ASKS

Media cache cleared, repeatedly. Preview files deleted. Preferences reset. Premiere reinstalled roughly ten times. I have wiped this machine completely, reinstalled macOS from scratch, and reinstalled Premiere onto a clean system. The bug survived every one of those steps. Please don't reply with cache-clearing or reinstall instructions — that ground is covered.

THE BUG

A black frame appears at or near a transition under this specific combination:

1. Two clips adjacent on the same track
2. At least one of them has Warp Stabilizer applied
3. A cross dissolve, or any other transition, at the cut
4. Scale and/or Position keyframed on the affected clip via Motion

Remove any single one of those four and the problem generally clears. Restore it and the black frame comes back.

WHAT HAPPENS ON EXPORT — AND WHY THIS IS THE WORST PART

The export behavior is inconsistent, and that inconsistency is the whole problem. From the same timeline, on different attempts, I get one of three outcomes:

1. It exports clean. The black frame is visible in playback but doesn't make it into the file.
2. The export fails outright and doesn't complete.
3. The glitch lands in the finished film — usually a frame or two. Short, but plainly visible.

Same sequence, same settings, different result. That is not a fixed defect in a clip; that is a timing or race condition between the stabilization pass and the renderer. Something is not reliably handing off a valid frame at the transition boundary, and which of the three outcomes I get appears to depend on what wins that race on any given run.

There is a fourth related symptom: the render will stall on the affected clips for up to 60 seconds. No error, no crash, it just sits there. Same trigger combination every time — which fits the same theory.

It is also non-deterministic across sessions, not just across exports. Clips that played and exported clean will develop the black frame later. I can open a project that was fine yesterday and find black frames on cuts I have not touched, in a sequence where nothing changed. That points at the stabilization analysis rather than at the edit.

WHAT THIS COSTS

I need to be blunt about the practical consequence, because I don't think it's understood.

I run a video production business. Roughly fifty events a year. When outcome 3 happens, I have delivered a paid film to a client with a visible glitch in it — a wedding film, something they watch once and keep forever. I cannot catch every instance by scrubbing every frame of every delivery, and I shouldn't have to. When outcome 2 happens, an export I've scheduled around a delivery deadline simply doesn't finish.

"Sometimes it works" is worse than "it never works." A consistent failure I can plan around. An intermittent one means I cannot trust my own output, and my output is the product.

VERSION

Premiere Pro 26.3.2 (build 2) — the current release. This is not a stale install and this is not a machine that needs updating.

The behavior has been present across the last two to three versions I've run [fill in the prior version numbers if you have them]. This is not a regression in a single build. It has shipped repeatedly, through multiple release cycles, on fully supported hardware.

SYSTEM

Mac Studio (Mac15,14)
Apple M3 Ultra, 32 cores — 24 performance / 8 efficiency
512 GB unified memory
macOS [fill in version]
Premiere Pro 26.3.2 build 2
Media: long-GOP [fill in: H.264 or H.265, bit depth, resolution, frame rate, camera]
Sequence: [fill in resolution / frame rate / codec]
Storage: [fill in: internal SSD or external, and connection type]

To be explicit about what that means: this is a current build of Premiere, on Apple's top-tier desktop silicon, with 512 GB of memory, intermittently failing to render a cross dissolve. This is not a resources problem and it is not a configuration problem.

ON LONG-GOP, SINCE IT WILL COME UP

Yes, I'm aware long-GOP is harder on effects that need frame-accurate handling at cut points. I don't accept that as an explanation.

Long-GOP has been the working standard for well over a decade. At fifty events a year, nobody is storing everything as full-resolution intraframe 4K — the drive cost alone makes it absurd — and no professional NLE in 2026 gets to treat the format the entire industry actually shoots on as an edge case. If Warp Stabilizer cannot reliably handle long-GOP media at a transition, that is a limitation Adobe should document in plain language, not something a paying customer discovers from a glitched frame in a wedding film that has already been delivered.

THE BROADER POINT

Every release cycle brings an AI cursor, AI object masking, AI something. Every renewal brings a price increase. I would trade the entire feature list for a dissolve that reliably renders the frame it is supposed to render.

I ran Final Cut Pro 7 for well over a decade. Installed it once. It never did this. I now pay monthly, indefinitely, for software that intermittently refuses to do what it did last year — and the standard first response is to tell the customer to clear their cache and reinstall, which I have now done ten times over.

Nearly twenty years of professional editing behind me. I can reproduce this on demand. Warp Stabilizer with a transition and a scale keyframe is not exotic — it is ordinary event and documentary work, the bread and butter of a large share of your paying user base.

WHAT I'M ASKING FOR

A bug number, or confirmation that this is known and where it sits in the queue.

And from other editors: if you're on 26.3.2 and you use Warp Stabilizer with transitions, please try this combination and report whether you see it. Given that it's intermittent, try the same export more than once. If this reproduces on other machines it stops being something that can be put down to one user's setup.

I will hand over a stripped-down project file and the source clips that reproduce it the moment someone at Adobe asks for them.