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.

[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

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

 

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

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

[Vova_GG]

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

[Ben Insler]

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.

[ThioJoe]

@Ben Insler Well it works as expected when the marker is at the cut and using Ripple Trim Next Edit To Playhead, but still deletes when using Ripple Trim Previous Edit To Playhead 🙃

[Ben Insler]

@ThioJoe 

but still deletes when using Ripple Trim Previous Edit To Playhead

When you use Ripple Trim Previous Edit To Playhead, you are removing everything from the playhead all the way back to the previous edit point, which includes the first frame of the clip on the B-side of that edit.  The marker in your screencapture is aligned on the edit point, which means that it is aligned with the first frame of the B-side clip at this edit.  The behavior you are seeing where the marker gets removed with Ripple Trim Previous Edit To Playhead is the correct behavior: that marker should be removed as it is within (and at the very first frame of) the range being rippple-trimmed.

It can be easy to think of edit points as boundaries between two frames, but it's much more accurate to consider the placement of edit points and markers at the start of a frame - conceptually, there is no way a mark can exist between frames.  Considering this, no marker can be placed between two frames, and thus, will always be inside or outside of a marked In/Out section.

[ThioJoe]

@Ben Insler  Yea I figured that was the reason.  Still, it's different than the behavior was for years before. Perhaps an option for this could also be added in the "Preferences > Trim" Menu.

Personally when I think of the marker's position, I think of it as "between" frames if it's lined up exactly with a cut.

[Vova_GG]

It no longer functions as it did for YEARS before, so now I either need to find ways to make it work as it did, or "accept" that someone decided to change it because they wanted to, or remain on the old version, where it functions as it should!

At the same time, really useful features are not added, but breaking the logic of the usual workflow that you have become accustomed to over the years is welcome!

“Nice” and “Thank you”!

[positive_fashion0511]

Сможете ли вы сделать это так, как это было? Неужели это так сложно, когда никто не просил вас сделать так, как сейчас?1 Но все просят сделать так, как было!

[positive_fashion0511]

Can you do it like it was? Is it really that hard when no one asked you to do it like it is now?1 But everyone asks to do it like it was!

[Dejan5C1F]

not fixed in the latest update ☹️

[positive_fashion0511]

Adobe Team,

Honestly, are we ever going to get a real response from someone at the company? Because at this point, every single update feels like it breaks something that was working perfectly fine before. It’s beyond frustrating.

Here’s just one example: the “Production” list. It used to be clean and simple, showing only project names. Now it’s cluttered with the full file path, which makes it messy and hard to read. Why was this change even made? And more importantly—how did it get past your QA team without anyone noticing?

And then there are the markers. This one is a dealbreaker. You’ve made it incredibly inconvenient to work on large projects and templates where markers used to be essential. Now, pressing Q just deletes a marker instead of letting me actually manage them. It completely ruins the workflow.

I’m asking you to roll these things back. Restore the markers. Restore the old “Production” list. Stop shipping updates that downgrade the experience. We’re not beta testers—you’re charging us real money for software that’s supposed to be professional-grade

[leakuslokus]

Hi! I have seen other entries about this and replies saying this is a premeditated change. 

I see it as a bug unfortunately, as it is very reasonable to apply markers at a clip start of an uncut stringout or even trimmed down selections (for example to see the first frame of a shot when in the marker window - this helps me a lot with quick navigation in big timelines) and I wish it would not be as it is in 25.4.1.

I understand this complaint is very finicky but how does this outweigh "lost markers laying around in a timeline", to quote one of the thread answers I read? 

I think if your devs want this feature, at best, it should be an option, as "copy and paste includes markers" is. At the same time, why not introduce a similar setting like "deleting clips includes markers" to get rid of lost markers in the process of clearing clips / cleaning timelines...