Timeline/performance problems since 25.2.0 Build 50

[Christian Leibig]

I've posted this in the other thread about the timeline issues, but maybe it's better suited as a new bug report.

Since the latest build (25.2.0 Build 50) I'm having a lot of timeline and other issues since this build. For example:

- GUI isn't loading properly on start (some black panels) unless I resize those panels.

- Timeline preview rendering start takes around 60-70 seconds, then goes at normal speed

- Timeline freezes frequently (stops updating the program monitor)

- External tools like Premiere Handy Tools and Excalibur are not working properly (very long delays of 60s+ until they apply the settings)

- Timeline often stops accepting input, I have to alt-tab away from Premiere and back again to be able to click on clips or start playback.

- Clicking a clip on the timeline does not update the data in for exampleEffect Controls. It only updates the data once I move the playhead. 

- sometimes most of the GUI stops responding to clicks unless I move the playhead or resize the corresponding panel

This is just off the top of my head. There's other weirdness going on, none of which I experience in the latest stable. 25.1 "just works", 25.2 currently is a master lesson in patience...

I'm sure it was working fine in the build before the playback bug (audio scrubbing) was introduced, because that's when Premiere beta was last working fine for me without major issues.

[Christian Leibig]

Most of the problems vanish when I disable "Color Manage Auto Detected Log and Raw Media". Especially the delay until rendering starts is gone.

Since I loaded the project in 25.1 and then back in 25.2 it seems the GUI problems on startup have vanished. Clicking on clips now updates the Effect Controls panel again. But the delays are all still present. It seems everytime Premiere needs to process a file it takes ~60s before it actually does something.

In this timeline we're mostly talking about 10-bit h264 files with ProRes Proxies.

[Christian Leibig]

I have done some more testing and found a difference in behavior between 25.1 and 25.2 that causes the delays (still haven't found the cause of the GUI issues, which come and go).

Setup:

Timeline is a very light 3 minute edit of h264 10bit footage using ProRes proxies. Above all I have an adjustment layer with Lumetri for some global corections. Now the difference is when I change anything in that global layer.

In 25.1:
Any changes to Lumetri are fine, and Premiere keeps working as expected. No extra reads or traffic on the network.

In 25.2:

Once I change anything in Lumetri in that global layer, rendering any output to the program monitor hangs, as does rendering previews. While this is going on I can see Premiere generating 300-400Mbps of traffic over the network to the NAS. The NAS is on a 10GBit connection and is normally not the bottleneck, it can go much faster. This traffic goes on for about a minute, after which everything goes back to normal.

My best guess is that touching the global layer causes Premiere to read/touch all underlaying files to update something color related. Possibly also sending off every file to the GPU to be processed.

TL;DR:
When making global changes 25.1 is quick and 25.2 causes a lot of read activity, preventing any work being done until every file has been read/processed.

[NintendoMagnavox]

I had to revert back to using 25.1. It was unworkable with that constant delay. It's funny because for some reason I had forgotten I updated so I wasted quite a bit of time trying to decipher including deleting everything off my cache drive.

[ZISIS357496398m75]

Same issues as @Christian Leibig here! Rolled back to 25.1 beta version!

[Kirsi21888295ykon]

Same issue here as well. I'm using Macbook Pro M1 MAX and MacOS 15.

[Christian Leibig]

On Build 55 right now, problem still persists.

It's even worse than I thought. First I thought it was just a Lumetri triggering this, but I just added a simple text layed over the whole timeline, and that, too makes Premiere reload all files (I assume) again. Network traffic for about a minute before the program monitor shows any updates again. The delay also happens again if you undo changes to that layer. None of that activity is cached, and I'm on 128GB of RAM.

[Christian Leibig]

Any updates regarding this? I feel that I have provided a lot of info regarding where the delays come from.

[Kirsi21888295ykon]

Is this a MAC issue only? I don't have this issue with my PC.

[Christian Leibig]

No, I'm on PC (Win11, TR3960, RTX3090, 128GB RAM)

[Kirsi21888295ykon]

Spoke too soon. This happens also on my PC. I had a project that was created probably in an earlier version of Premiere Pro beta. I couldn't see the issue in that project, but when I added new files to the project the situation is the same now. Whenever you do a change in timeline there is a minute or two pause on everything. Adobe please comment on this issue. What is the point of beta if you don't comment anything on reported bugs. There have been cases when a bug that was discovered in beta was also present later in a stable version. This can't happen with this issue.

[Kirsi21888295ykon]

Issue: Timeline freezes when trying to do almost any change somewhere
Adobe Premiere Pro version number: 25.2.0 build 65
Operating system: Windows 11 Build 26100.2605
System Info: CPU, GPU, RAM, HD:

CPU: AMD Ryzen Threadripper 7970X

GPU: Nvidia 3090 RTX

GPU driver: Nvidia Studio driver ver. 566.36

RAM: 128GB

Hard Drive: NVME, NAS with 10Gbit/s connection to a computer, doesn't make any difference where files are located

Video format: Canon R5C 8K Raw, DJI Pocket 3 4K HEVC, DJI Mavic 3 Pro 5K x264, does seems to happen on all of the media files I have.

Workflow details: Put files on timeline and try to do a change in the Lumetri basic panel or switch adjustment layer with a effect on it on or off. The more you put files into a timeline the more sluggish it gets.

Steps to reproduce: Create a new sequence and put files in it. Then add an adjustment layer top of the media files -> Timeline freezes for 30 seconds or so. Change a color setting in a Lumetri basic panel in any of the clips in timeline -> timeline freezes. Basically almost anything you do will result in a timeline freeze. Premiere for me is unusable in this beta version. Beta 25.1 is working fine.

[jhhammond]

I'm having the same issue.

Apple M1 Max

32 gb ram

400 gb of free storage

working off a T9 4 TB with solid cable.  500 gb of free storage

Project is mainly footage from C70.  All frozen timeline scenes are of C70 HEVC .mp4

Loading time of project is up to 10 minutes.  

Timeline playhead freezes constantly.  First started when in Color workspace and when essential sound tab was open.  

[Jorge Jaramillo Hdz]

Agree, since 25.2 Premiere Pro Beta has become unusable, I mean it was a time when I edited entirely in Beta, it was much better than the official release, but now it's impossible to work with.

[Satish_Ramakrishnan]

Would it be possible for you to show the issues via a screen recording? 

[Kirsi21888295ykon]

Here is one from 25.2:

IMG_5616.MOV

And here is the same project in 25.1:

IMG_5613.MOV

[Satish_Ramakrishnan]

Thank you! Could you try to remove the adjustment layer and apply the Exposure change to the clip directly and see if the performance (of monitor refreshing and playback starting) is any better compared to 25.1?

[ZISIS357496398m75]

@Satish_Ramakrishnan This issue exist to a fresh Timeline too!

[Satish_Ramakrishnan]

Could you please explain what you mean by a fresh timeline?

Do you mean one clip, one adjustment layer on top, adjustment layer selected, lumetri exposure applied. Then clip selected, lumetri exposure modified. Compare this with 25.1 and you see 25.2 being this slower?

[ZISIS357496398m75]

@Satish_Ramakrishnan I mean that is no different if there is a adjustment layer of the top or not. The issue still exist!

[Kirsi21888295ykon]

It is the same without adjustment layer. There are number of things that cause timeline to freeze. For example changing settings in Lumetri basic panel and turning adjustment layer on or off. Also there are numerous threads about this issue already in this forum if you look for them. Please fix this.

Effect controls lagging - Adobe Community - 15074221

Program Monitor is completely broken in version 25... - Adobe Community - 15043686

UI Lagging Issue When Extending Text Layers on Hig... - Adobe Community - 15064669

Lumetri Effect huge input lag in PrPro 25.2.0 buil... - Adobe Community - 15046909

[Satish_Ramakrishnan]

We still do not have an in-house repro, a critical step towards a fix. Thanks though for confirming that the issue exists without the adjustment layer. So let's only look at what's in the clip. I want to understand if the performance has degraded with Lumetri or all effects in general. Could you try to apply other effects and see if you see the same behavior?

Do you also see the problem with a clips (and the proxies) in the local machine as well? Also are the latest Beta builds any better?

[Kirsi21888295ykon]

Latest beta still have this issue and it makes no difference whether files are in NAS or local NVME drive. This also happens with other effects too and when placed on individual clips and not on an adjustment layer. It also happens when track output for the adjustment layer is off and you make changes in Lumetri, timeline freezes. If you type the value in Lumetri basic panel and not move the sliders, then there is no freeze. If you have about five minutes of clips in timeline, then there is no freeze, but when you add more clips then it starts to happen. So Adobe when doing your own tests please put enough clips in timeline and different clips, not just one clip copied. 

[Christian Leibig]

What I found is I am getting these delays mostly occur when I'm changing values with the arrow keys (like shift+up to increase by 10). If I manually type the value and increase by 10, the change is instant. If I do shift+up I have to wait for Premiere to respond again.

Maybe that's the missing link to reproduce on Adobe's side.

[Kirsi21888295ykon]

@Satish_Ramakrishnan any news on a fix for this? As I have said this bug is so severe that it is making the use of this program impossible.

[Satish_Ramakrishnan]

This issue is being investigated internally. We do not have any updates as yet. Will let you know as and when this is fixed.