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
  • 27 replies
  • 2171 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

 

27 replies

Community Manager
August 14, 2025

This fix is now available in Premire Pro 25.4.

 

@Vova_GG I have verified that this fix is in fact functional in Premiere Pro 25.4.  Please confirm that your Out Point was not set to include the frame where the marker is placed.

 

@ThioJoe Regarding your question about patches, you're absolutely correct to mention the Beta.  The Beta is the pre-release of these fixes, just in the form of a full application instead of patches.  We release a new Beta almost every day, and encourage you to use the Beta to access these types of fixes prior to their official release version.

Participant
August 14, 2025

And of course they didn't fix it in the newly released 25.4, OMG!

ThioJoe
Community Expert
ThioJoeCommunity ExpertAuthor
Community Expert
July 17, 2025

@joelhb717 I really don't know why they don't release patch versions for bugs that have already been fixed in the beta, and instead make us wait a month 🤔 🤔. It was the same for a previous bug having to do with copying and pasting layers in the properties panel, it was fixed in beta but we had to wait.

Edit: Actually I was mistaken, it still does it in the beta as well at the moment.

Participant
July 17, 2025

I tried it and the solution in that post still isn't working for me. When will 25.4 drop?

Participant
July 17, 2025

Did we ever get an answer? I am still experiencing this bug and don't see an update on my creative cloud 

Participating Frequently
July 10, 2025

Thanks for your help! But still, when it was on one button, it was more convenient!

Community Manager
July 7, 2025

@positive_fashion0511 This functionality has been brought back using a different keybaord shortcut!  Please see the correct answer at this post.

Participating Frequently
July 6, 2025

Hello, is it possible to return frame-by-frame deletion by pressing the Q key again?

Participating Frequently
July 6, 2025

Здравствуйте, можно ли вернуть покадровое удаление повторным нажатием клавиши Q?

Community Manager
June 18, 2025

@numbbaby Thank you for this feedback.  Yes, you are correct - for your particular workflow this update to marker behavior does impact how you are using markers.  Unfortunately, the previous marker behavior caused significant mismatch potential between markers and the regions they annotated, and there existed no clean way to resolve these mismatches or remove the markers prior to making such an edit (which would also have been unnecessarily tedious).

I will definitely log your request for a togglable preference regarding this new behavior.  In the meantime, I'd recommend incorporating Ripple trim into your workflow.  Note that this updated marker behavior only applies to Extract edit operations, not Lift edit operations.  You can easily Lift a marked region, preserving your sequence markers, and then close the resulting gap with Ripple trim.