Glitch on Warp Stabilizer dissolve causes export to fail

[JOHN MONDO]

When using the warp stabiliser effect on a clip that dissolves intoma still frame Premiere Pro will render stabilise 1 frame short causing the export to fail at this point. You can also see it as a glitch in the graphic at the end of the dissolve. Shortening the dissolve by 1 frame fixed the issue for me. 

Suggestion - it would be great if the warp stabiliser effect had the ability to add handles.

PP 25.2.3

MAC OS Sequoia 15.6.1

Apple M1 Max 32GB RAM

[Dani_V.]

Hi @JOHN MONDO, 

Thank you for reporting a problem and sorry you're experiencing issues. What kind of media are you working with (source, file type, frame rate) and is it Variable Frame Rate footage? You can find this information if you right-click the clip in the Project panel > Media File Properties. 

Do you see this with the cross dissolve only or other transitions? Are you able to export if you nest the stabilized clip and add the transition between the nest and still? 

Sorry for the frustration, 
Dani

[Peru Bob]

Try nesting and apply Warp Stabilizer to the nest.

[JOHN MONDO]

It's not a big issue. I just discovered it yesterday when I had two timelines out of 17 that were conistently failing on export. Media is 4K25P from a Sony FX6 and yes it was just a cross dissolve - I ddin't try it with any other transitions. Cross dissolve was set at 13F - changing it to 12F fixed the issue.

Type: MXF File  Image Size: 3840 x 2160 Frame Rate: 25.00 Source Audio Format: 48000 Hz - 24-bit - 8 Channels MXF File details: Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal) File generated by: Sony, Mem (2.00) AVC Unconstrained Bitstream Format: Sony Gamma: S-Log3 Cine 

[JOHN MONDO]

I could do that Bob - I often nest warp stabiliser but in this case it was simpler to just shorten the dissolve by a frame. If I had needed my dissolve to be exactly 13F I could have made it 20F, re-analysed the clip and then shortened it back to 13F. It was more about reporting the problem and seeing if Adobe can actually fix the root problem.

[Dani_V.]

Hi @JOHN MONDO,

Thank you for the additional information. The team is aware if this issue and will update the post when we learn more.

Dani