Premiere Pro 25.6 is no better

[real_5081]

I am doing a simple edit, there's no grading, no transitions, no LUTs, no 3rd party plugins, and the performance is the worst I have EVER experienced in 15 years of editing. It's not even just that the playback is slow and frames take a long time to load, navigating the app itself is slow. Everything is laggy! The timeline cursor doesn't even scroll smoothly.

Can you just drop this whole push for AI tools and focus on updates that are stable? 

My rig: Windows 10, 4090 GPU, Ryzen 9 5950, 128gb ram, NVME drives 

[real_5081]

It consistently takes 2-3 seconds clicking anywhere in the timeline for the program monitor to update. Playback is laggy, pressing play takes a few seconds stopping takes a few seconds.  This is an editing app! We are dealing with frames that are a tiny fraction of a second.  

Spending your time introducing AI search functions is NOT worth the loss of basic functionality with every version released. 

[Kevin-Monahan]

Hi,

Thanks for the post and the info you provided. What kind of footage is this? Have you tried launching without third-party plug-ins? You might also try deleting media cache files. Press Shift at launch and try those things in the Reset Options dialog box. Let us know if that helps.

Thanks,
Kevin

[Joey28105522y4q7]

I am having the same issues as the original poster across multiple different projects. 

[Kevin-Monahan]

Oh, I'm sorry to hear that. Maybe I can assist. Can you tell me the kind of media you are using and system information. That would help. 

Thanks,
Kevin

[real_5081]

Hi Kevin, 

My system is Ryzen 9 5950x 16 core, 128gb RAM, 4079 GPU, NVME drive for media, another for cache.  

This can be literally any kind of footage. The app just runs very, VERY slowly regardless of what file types are used.  I've tried all that, none of it works properly and it's specifically the 2025 release. The 2024 release is t as bad and the 2023 release is far better 

[R Neil Haugen]

I'm running a Ryzen 3960x 24-core w 128GB of RAM, and a 2080Ti ... mostly BRAW, with some mov ProRes, a bit of H.264/5, other spread out media. Heavy color work, only a bit of Warp, and graphics and transcritions of course.

I'm not having any troubles editing, so what the freak is the difference between our setups? That's bizarre.

[Cameromanov]

Yes, you're absolutely right!
I recently updated Windows to 11 and it started slowing down completely.
I edit weddings shot in 4K 4.2.2. H265, and now the color is acting up. No matter what settings I use, there's a color shift (in contrast), but the color changes when exporting. Sometimes the contrast also jumps right in the preview window. I won't even mention the lack of a decoder! On 25.3, the decoder randomly switched to the 5090 during editing and workflow. Now it's completely unstable, the card works intermittently. BUT THE MEMORY IS CONSTANTLY AT 80-95%.
Adobe is NOT NORMAL!

I have both Intel and Nvidia decoders checked in the decoder column, but the integrated Intel one works more often.

I'm constantly stressed while working, with freezes and bugs popping up one after another. I open Da Vinci, and everything works fine. My graphics card is constantly loaded during workflow. Why are the developers so negligent in their work?

My configuration is:
13900K + 5090 + 192GB DDR5 4800 (48x4)
My work project files are stored on two 4TB Kingston Fury Renegade SSDs.

[R Neil Haugen]

What are you full CM settings, and the media, and your export space?

Is the difference only outside Premiere, viewing in a player, or when you re-import an export into Premiere?

[Cameromanov]

Rendering is done on a 4TB Fury Renegade, which has over 1.5 TB of free space.

I'll send screenshots of the settings.

The contrast shift occurs during editing, right on the timeline. Several frames have to be recolored.

A separate issue is seeing completely different contrast in random clips after rendering.

The player I use is Media Player Classic.

[Cameromanov]

The thing is, I have never encountered the problem of contrast variations in WIN 10.

[RjL190365]

I am placing some of the blame on the entire computer tech industry's "race to the top." That is, hardware is pushing to higher and higher prices while the cheap hardware either stagnates or disappears.

And support for Windows 10 officially ended this past October, with no more free security updates, meaning that its continued usage while online may lead to an increased risk of external hacks, malware or ransomware.

Hence, the need for software companies to incorporate Ai in their software. Had a software program ditched Ai in favor of stability, this would result in that software falling far behind everybody else while also increasing in price, making the "stable" product a highly niche product that's so expensive that very few individuals would even want to purchase.

I am sorry, but that's the way it is.

[real_5081]

No sorry, Adobe can't blame the whole tech industry for the fact that their apps are bug riddles disasters.  Even Adobe fonts fails to work adequately, that's nothing to do with hardware getting more expensive. 

[RjL190365]

Every single NLE has a lot of problems, not just Adobe. Resolve, for example, does not even have a software encoder of its own, instead relying solely on the Windows-native Microsoft Media Foundation framework for H.264 and HEVC encoding, which in turn relies solely on whichever GPU hardware encoder installed by the GPU drivers. This actually delivers the worst of both worlds in terms of image quality: the fast quality of a low-quality encoder with the slower-than-expected performance that's typical of the highest-quality settings for a given hardware encoder. Thus, if your system were equipped with a CPU that required a discrete GPU just to even run at all, and your chosen GPU lacks a hardware encoder, Resolve will simply have the H.264 and HEVC exporting choices grayed out, making them completely unavailable.

The paid Studio version offers GPU-acceleration of its own plus additional encoding options for the MMF hardware encoding framework (hence the "hardware" instead of the "native" encoding mode).

And only the Studio version can utilize software encoding-and only with a third-party, added-cost plugin which includes this encoder. That saves Blackmagic Design the costs of including its own encoder for H.264 and HEVC.

Moreover, Resolve cannot read AC3 files that are embedded in any viddo file; such files are simply imported with no audio.

[real_5081]

OK...

[R Neil Haugen]

I'm always surprised at the number of users that don't seem to realize there are pluses and minuses to all the apps. I use Resolve daily ... and work with many people routinely who are based in Resolve.

I'm quite aware that the 'other side' has plenty of it's own issues. But then, if your workflow doesn't hit one, how would you know? Or care?

None of these apps are close to perfect, more's the pity.