Skip to main content
ThioJoe
Community Expert
Community Expert
June 17, 2025
Question

In 25.3, Ripple Trim Edit to Playhead deletes markers at the ends

  • June 17, 2025
  • 21 replies
  • 1985 views

See the attached video for what I mean. This only seems to have started happening with the latest update to 25.3.

 

Problem Behavior:

  • If there is a marker exactly at the cut the "ripple edit to playhead" action will be going to, it will delete that marker instead of preserving it like before.
  • If there is a marker exactly at the playhead when a "ripple edit to playhead" is done, it also deletes the marker instead of preserving it

 

This at least affects these shortcut actions, but there could be others that the behavior affects too:

  • Ripple Trim Next Edit To Playhead
  • Ripple Trim Previous Edit To Playhead

 

 

Screencaps:

 

New bad behavior in 25.3

In that example I show as having a marker both at the playhead and the cut point, but to be clear it will delete the marker even if it's only one of them, it doesn't need to be both.

 

Expected Behavior (Example from Premiere Pro 2024, but same as before the 25.3 update)

 

Windows System Info:

  • Premiere Pro Version: 25.3.0 (Build 84)
  • Windows Version: Windows 11 Enterprise 24H2 (Build 26100.4351)

System Hardware:

  • CPU: Intel 13900KS
  • GPU: Nvidia 5090 FE
  • GPU Driver Version: 576.66
  • RAM: 128GB
  • Storage: NVMe SSD - Optane 905P 1.5TB

 

21 replies

Community Manager
June 17, 2025

Hi @ThioJoe ,

We recently updated marker behavior when performing actions like this (Ripple Trim Previous Edit to Playhead, Extract, etc.).  Sequence markers within the region being extracted now clear when performing an edit that ripples the timeline.  This prevents resulting oprhaned sequence markers from remaining in the timeline and incorretly annotating clips that they were never intended to align with.

 

There is a known bug related to this in Premiere Pro 25.3 where a marker that is placed exactly on the out point of the cleared range is also cleared.  It soulds like this is what you are experiencing, and is already fixed for Premiere Pro 25.4.

Participant
June 23, 2025

So, when can we expect a 25.4 fix? Because this bug is annoying, and I have to downgrade to the previous version!

Kevin-Monahan
Community Manager
Community Manager
June 25, 2025

I can move this to Bugs.

 

Thanks,
Kevin

 

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio