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

[ThioJoe]

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

[Ben Insler]

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.

[numbbaby]

I am used to putting markers in a sequence, say, for when music hits happen (much easier to see than marking the music track itself - plus sometimes music gets re-edited but with the timing of the hits remaining the same), then editing/extracting/etc. video with the audio tracks locked - but still using the sequence markers exactly where they are.

Right now any video extracting I do removes any sequence markers that happen to be over what I am removing.

Changing the behavior of this is fine, but without a doubt needs to be user toggeled (or a bit more clumsily, say 'Sequence marker lock') on or off.  Right now, my normal workflow is very impacted by this change, since I am now consciously avoiding any video extracts around 'music hit sequence markers', and that's just absurd.

[Sami Succar]

I know this isn't ideal, but you can create an adjustment layer over the whole timeline and add your markers directly on it. It would behave like it used to.

[Ben Insler]

@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.

 

[Vova_GG]

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]

I can move this to Bugs.

Thanks,
Kevin

[positive_fashion0511]

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

[positive_fashion0511]

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

[Ben Insler]

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

[positive_fashion0511]

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

[joelhb717]

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

[joelhb717]

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

[ThioJoe]

@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.