Inspiring

Warp Stabilizer Glitches and Skips Frames

Forum|Forum|7 months ago
December 4, 2025
3 replies
293 views

Dear community,

Thank you in advance for any guidance you may have.

I am having a terrible time with Warp Stabilizer on my new computer build. The issue is specifically with a project that has about 1,500 sub clips, 860 sequences containing 1 subclip, many of which have a stabilization effect on it.

I have no problem stabilizing these images on my older computer build. On the new build (specs below), many of the warp stabilized images are jumping or skipping frames; the image will go forward and then jot backwards. Other keywords: glitch, jitter, skip.

The issue is rarely the same: If I find a glitch on a clip, and then go back 10 frames and replay, it will not glitch the same way.

Stabilization Settings

I am not using any subspace warp - all position and scale, and my percentages for stabilization are low.

I have attached a screenshot of my stabilization settings, but here they are again:

Parameter Value

Motion
Position	960.0, 540.0
Scale	118.0
Scale Width	100.0
Uniform Scale	Enabled
Time Remapping
Warp Stabilizer
Result	Smooth Motion
Smoothness	10 %
Method	Position, Scale, Rotation
Preserve Scale	Enabled
Borders
Framing	Stabilize, Crop, Autoscale
Auto-scale	(102.7%)
Additional Scale	100 %
Advanced
Detailed Analysis	Enabled
Fast Analysis	Enabled
Rolling Shutter Ripple	Automatic Reduction
Crop Less <-> Smooth More	50 %
Synthesis Input Range (seconds)
Synthesis Edge Feather
Synthesis Edge Cropping
Hide Warning Banner	Enabled

Tried so far:

Essay 1: New Projects –> The issue didn't replicate itself, but…
- I made two new files on both my HDD raid system, and my NVME. In both cases, there is only a new project file with only 1 clip. There is no jumping or glitching in either case. This lead me to try two things:
  - Essay 2: Using original project file, Pause Dropbox Sync–> Still issues
    - Reason: The folders I created above were outside my Dropbox folders. Dropbox can be weird with saving premiere files, so I turned off sync and reanalyzed the images. Still glitching.
  - Essay 3: Copy the old project contents into a new project file –> Still glitching
    - Reason: If there was no glitching when there was only 1 clip, then surely…But no, same issue.
    - Is the project size causing the issue?

Essay 4: Rollback GPU Driver –> Nope
- Every time I analyze the WS, I can hear my driver ramping up like it's going to war. I believe WS uses GPU. I have no other playback issues beside the analyzing and rendering of the WS clips, so I looked into these NVIDIA 4080s, and there is a lot of user feedback lamenting the new drivers are unstable.
- I rolled it back to 566.36, per this video: (https://youtu.be/NTXoUsdSAnA?t=490), no difference.
Essay 5: Change GPU Driver to "Studio Driver" instead of gaming –> Nah
Essay 6: Cleared the cache, reset preferences –> nothing
Essay 7: Burn sage around computer–>Helped a little

My specs are below. My old computer is working off a 1080 graphics card, this new one is a 4080 super.

Premiere

25.6.3 (build 2)

Computer

Property Value

OS	Microsoft Windows 11 Pro
Version	10.0.26200 Build 26200
System Name	MARCELLA
System Manufacturer	ASUS
System Model	System Product Name
System Type	x64-based PC
Processor	Intel(R) Core(TM) i9-14900K, 3200 Mhz, 24 Core(s), 32 Logical Processor(s)
Motherboard	ASUSTeK ProArt Z790-CREATOR WIFI
BIOS	American Megatrends Inc. 2801, 11/29/2024, UEFI
RAM	128 GB

Graphics Card

Property Value

GPU	NVIDIA GeForce RTX 4080 SUPER
Driver Version	32.0.15.6636
Resolution	2560 x 1440 x 59 hertz
Color Depth	32-bit

Examples

I have included two examples of what's happening, as well as screenshots of the frames prior to any effect being put on plus the warp settings.

MEX22_-_041_-_CLN_w2_m1_xpe_xws.zip

CAMP20_-_019_-_CLN_w3_m0_xpe__xws.zip

M

mw998Author

Inspiring

Dani! Dani ol' Dani my friend. In short, I got it working by rolling back premiere to Version 25.2.0, the version where it was working on my old computer. I also:

1) Updated my Bios. Intel i9-14900K chips have known stability issues that require this update. My comptuer was new, so I hadn't gotten to it yet. I did this before rolling back, and the problem was still there.

2) I unchecked h264 encryption decoding in the editing>preferences>media section (left the other one checked). I did this after 1, but before rolling back the version, and it didn't work.
3) I drew a line with salt across the threshold of my office door, muttered ancient texts, eyes rolled back like the sleeves of my long silk robe. The glitching may have gotten worse, it was hard to tell, but all the plants in my office came back to life. I did this before the rollback to the older version of premiere, but after 1 and 2.

Thanks again for your help.

Best,
Max

p.s. high quality playback had no effect.

M

maximeb24899079

Inspiring

Hi.
I got the same issue with Optical Flow applied to a clip with speed change. The only way to get rid of those glitches is to render the clip and/or the portion where the clip is in the timeline.

This is an issue I know for quite some time and I'd really like to know what must be done to stop it.

I work on a MacBook Pro M1 Max on Sonoma.

D

Dani_V.

Community Manager

Hi @mw998,

Thanks for reporting a problem and sorry you've been experiencing issues. So the exact same project in your old build is playing fine (and same Pr Pro version)?

Is the Stabilizer added on the sequences or the subclips? What if you add it to a trimmed source clip itself (not a subclip)?

Any chance you have High Quality Playback selected in the Program monitor (any difference if deselected)?

Regarding your media, what kind of files are you working with (format, fps, resolution, etc) and where are they stored (are they also in Dropbox)? Does the sequence and media frame rate match?

Sorry for the frustration,

Dani

Stabilization Settings

Tried so far:

Premiere

Computer

Graphics Card

Examples

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.