on premiere 2025.1.0 you cant see the cut mark any more on video tracks if track is too skinny. can you please fix this? yes issue occurs on new and old premiere projects.
BugAcknowledged
TOPICS
Performance or Stability
,
User experience or interface
@AndyOates I'm sorry about this, it was a mistake on our part. The bug has been fixed in the Beta version you can download today if you like, and the fix will be in the next release.
The part that divides the clips used to be visible, but now it blends with the label color, making it hard to notice the division between clips... Will this be fixed in the next update?
Since the last update, it's barely possible to distinguish cuts in the timeline when video tracks are minimized. They should be visible, just like the cuts in the audio tracks right below. Hope Adobe will correct this in the next update !
Since 25.1. the stroke opacity and color that indicate in and out points in a timeline have changed and while I understand the aesthetic improvement, this change has been a little impractical.
Not that it's not a good change, it's just gotten a touch too hard to tell where clips start and end.
I use pr a lot and this caused immediate hickups for me.
Maby it's just a bug, maybe the tweaking went a little off the road or maybe its just me - anway I thought it ma ybe worth pointing out.
I've attached screenshots of 25.0. and 25.1. in case my text here doesnt cut it ^^
Thanks for reporting this issue. The good news is that it is something we are aware of and have already fixed in beta. The next version of Premiere Pro will fix this problem. As a workaround, if you increase the track height to any height above the minimum, the issue goes away. We will be adding mention of this to our Known Issues documentation soon.
When clips or slugs are at minimum track height, the cuts lines between adjacent clips are either invisible or 1 white pixel borders *WHEN video names are enabled. However, the cut line IS visible at minimum track height when video names are DISABLED.
I don't know if this is considered an 'aesthetic choice' or an unintentional bug but it is not helpful as I use slugs extensively to mark timeline sections and this workflow is impeded when I minimize track heights for complex timelines. Even though you can tell where clips begin and end generally by clip names, it isn't precise at different magnifications.
Adobe please sort this out with the next update of Premiere!
The latest version is so far so good in my opinion but when I zoom out in the timeline the individual clips can no longer be seen clearly. It looks like one big clip. The lines are there but they are much too subtle.
This is so frustrating as I have to zoom in just to see where one clip ends and the next clip starts.
This has slowed my editing down to a completely unacceptible level.
I just want to add that I've been a professional editor for 22 years. A lot of things have bothered me with various software updates over the years (the new audio handle badges for one!) but this is truely the first one that has prompted me to reach out and report. I will have to look at other software if Adobe don't address this.
@AndyOates I'm sorry about this, it was a mistake on our part. The bug has been fixed in the Beta version you can download today if you like, and the fix will be in the next release.
While I've got you, will there be an option to hide the audio handle badges in any future releases? It's still quicker to use shortcuts for this and they just get in my way!
Sinceramente, não é viável continuar usando o beta, porque o projeto que você abre no beta, você não pode mais abrir no Premiere normal, porque é uma versão mais antiga, e o beta ainda tem outros bugs. É difícil usá-lo. Eles disseram que a próxima atualização corrigiria isso. A próxima atualização será em 2026 por acaso? Que atraso e ainda somos os mesmos...
Honestly, it's not feasible to keep using the beta, because the project you open in the beta, you can't open in the normal Premiere anymore, because it's an older version, and the beta still has other bugs. It's hard to use it. They said the next update would fix this. Will the next update be in 2026 by any chance? What a delay and we're still the same...
@edno_4235 The issue was introduced in v25.1 and it will be fixed in v25.2, which will be shipping this spring. There is no need for you to use the beta: the simple workaround to this issue is to make the track higher than the minimum. Our apologies for the inconvenience!