premiere pro 23.0 doesnt use GPU takes CPU to 100%

[yossifor]

what worse is that when i change resoulution in timeline to 1\4 or 1\8 resolution tha elagging gets worse.

i have NVIDIA RTX 2080 SUPER and 32 giga ram DDR4 Intel core I5 6600.

[Fergus H]

We need more information about the problem you are having. Please update your post, following the information here: How do I write a bug report?

Regards,

Fergus

[yossifor]

Hi there is nothing real i can add. the footage is 4K from sony a6400 with no plugins and the problem is more when there are 2 layers of clips one over the other.

[RjL190365 · Accepted solution]

It is very likely that your CPU is severely underpowered for any type of 4k video editing whatsoever. In fact, a seven-year-old quad-core CPU that is only capable of single-threading (as in it completely lacks hyper threading) is barely suitable for even 1080p video work these days.

And due to the design of all video editing programs, Premiere Pro must consume a certain minimum amount of CPU processing power before it can utilize the GPU at all. Otherwise, all NLE programs - Premiere included - will choke.

As it is turning out, the i5-6600 is not quite powerful enough to even run any newer version of Premiere Pro properly. Worse, Intel driver support for that CPU and all other 6th-through-10th Generation CPUs has recently been depreciated into Legacy status.

And the fact that the RTX 2080 SUPER GPU that you have is seriously overqualified for your CPU is not helping matters even one iota.

[yossifor]

Hi

thans forthe answer.
so what is the recommended CPU or what should i change?

[Adam Speedy]

Hi. I do not think your CPU is the problem. I am facing the same problem with Premiere 2022 and 2023; to the point where editing is not possible. Even with proxies (cineform low quality), the timeline takes longer to play than without them. Something is very very wrong with the latest updates.

[RjL190365]

I also place some of the blame on the Microsoft Windows ecosystem itself. The way Windows updates work, it allows many of the old system files which clash severely with newer system files to remain in the system. This will result in performance issues and sometimes stability issues even when running ordinary programs.

And as part of my previous reply implied, Intel is now no longer maintaining mainstream support for any of its hardware that's even three years old, let alone seven years old.

So, all told, everybody in the tech industry is to blame. Planned obsolescence is definitely in play here.

[Adam Speedy]

Hi Rj. PPro 2021 works insanely fast on the same Windows machine. Windows updates (whilst I agree, they are messy) are not the problem here. 2022 and 2023 are insanely slow and buggy in my experience.

[RjL190365]

Actually, Adobe is not alone in this. Intel literally put a gun to every software companies' heads by dictating them to partially or completely discontinue support for all hardware that's more than 18 months (1.5 years) old.

By the way, 2021 ran abysmally sluggishly on my current rig compared to even 2022, let alone 2023. Old versions of Premiere Pro may not work properly on any newer hardware because of their required features that newer hardware now no longer supports at all.

[Adam Speedy]

So what you're saying is people shouldn't bother buying Adobe products unless their hardware is less than 1.5 years old? I'm running an intel i9-9900k and an RTX 2080. No other program I use has caused anywhere near as many problems as Adobe's.

I cannot find anything about this intel statement online, and I find it very hard to believe.

If it *is* true, I guess 90% of us can cancel our subscriptions and... what? Switch to different programs which have no problems at all? Or resort to piracy as Adobe is removing older versions of the programs?

You do realise Adobe has a reputation for releasing broken and buggy software versions, right?

This attitude of "Can't be our fault that our programs are slow and buggy" is just boring at this point. I am so fed up with Adobe's broken and buggy mess.

[devGuru411]

@Adam Speedy - I will second/third your answer.  I too am having a TON of issues when I never had issues before update v23.1 (Build 86).  I have edited 4k/6k/8k footage with no issues until this update.  Now I can barely play a few frames of video before it crashes with GPU acceleration on.  If I turn GPU acceleration off it will play the proies (cineform low quality) but not with GPU acceleration so it's a pain to turn them on and off.

My system specs are:

Intel i9 9th Gen CPU

64GB DDR4 Ram

NVIDIA GeForce RTX 2070

And yes I realize the CPU is an older CPU but it was bench tested better/faster than the current i9 at the time and again, I have NEVER had any issues editing the footage until after the v23.1 update.  Also Davinci edits the footage just fine.

The statement about Intel putting a "gun to the head" of software companies is also BS.  I am an intel partner and I reached out to them directly and yes they still support processors that older than 3 years old.  This is on ADOBE 100% - or at least 99% - and it is one of the biggest reasons people are moving to Davinci and other platforms on a daily basis.

[RjL190365]

Here's the problem:

Until the very recent announcement of the legacy support for Skylake through Comet Lake CPUs, Intel has been doing this (depreciating or even completely discontinuing support of its older parts) without telling any of the consumers a single word about it. It may have told the software companies, who also fail to tell its consumers about this.

At least Intel did tell its consumers (who actually visit the chipmaker's Web site directly) about the impending depreciation or EOSL of its Skylake-derived parts - which means everything from the 6th- through 10th-Gen CPU parts. Nvidia does the same (at least for those consumers who visit the GPU maker's Web site directly, and not just the PC manufacturers' Web sites, who are guilty of the exact same hiding-the-truth offense) for its older GPUs.

In other words, everyone involved, not just Adobe, has been hiding the truth from its consumers. Adobe only did what someone else told it to do.

[devGuru411]

Respecfully, as I mentioned, I am an intel software/hardware partner - that means I have access to their teams and I just reached out and was told that this is "BS".  Intel knows about Adobe's issues and knows that Adobe is blaming them and their position is that this is a bug in Premiere 23.

LIKELY - it will be fixed in a future revision (unless Adobe wants to loose every user on an Intel CPU and NVIDIA GPU to someone like Davinci) but they will probalby not admit fault, it will just be "fixed" magically as so many other little issues are after they tell us "its not a bug".

[RjL190365]

That I do agree on. It seems as though every single update to Premiere Pro has introduced new bugs. I would like Adobe to get these bugs fixed. But if that meant foregoing support for newer hardware and eliminating much of the must-have format support, then the company would be in huge trouble as it would have fallen far behind the NLE competition.

[R Neil Haugen]

I use both Resolve and Premiere daily. I am also regularly on the LGG and BM forums. And I work with/for a bunch of colorists based mostly in Resolve.

The variability of user performance *even on similar machines* across these apps is frustrating at this time. And no, Resolve is no silver bullet for all performance issues. They've got bugs and odd performance issues also.

In Premiere, my 24 core Ryzen screams. Another user with such a similar build it must also have been a Puget rig posted total crud running similar media. Why? No clue.

Resolve runs similar to Premiere on my desktop but is such a dog on my Acer laptop I removed it. Pr 2023 runs beautifully on that laptop.

Others have the complete opposite experience. Why? No clue.

I like troubleshooting but at this time it's a mess. Used to be a lot easier to puzzle through.

And Pr 23.1 definitely has some issues. Program Manager Francis Crossman posted about H264/HEVC issues on Macs w 23.1, suggesting reverting at this time to 23.0.

Well, at least it's easier to have multiple versions or move between them in Adobe software.

But at this time it's very frustrating.

Neil

[Adam Speedy]

I have an i9-9900k and still have the same problem.

[yossifor]

HI

thanks for the answer. for now i rolled back to an older Nvidia stidio driver which helped a lot.
like many here say, i love Premire but the amount of bugs and crashes due to version update is ridicilous. 

[davidj94964383]

I have the same issue with an I9 and rtx 3090, so youre not alone. Any resolve?

[R Neil Haugen]

As always, what media, what effects used, and what specific version of PrPro?

[davidj94964383]

Zero effects, proxies and low res preview same issue, cpu taxes out and gpu under utilized. Most recent PrPro. I think ive traced it to the Canon R5 footage. So frustrating that new equipment cant jive without added steps to the workflow.

[R Neil Haugen]

David,

Create a new thread on this, with specifics of your hardware, OS, and PrPro version number, with the information on that problem with the Canon R5 media.

We'll see if 1) we get others with the same issue and 2) we can get their formats staffer to hop into the discussion.

Neil