Copy link to clipboard
Copied
Adobe Media Encoder and adobe Premeire Pro 23.1 no longer render across multiple gpus and now severly underutilizes the cpu. Before the update Adobe cc would render using all of my GPUs with good use of my cpu and my render times were amazing. Now my renders only utilize 1 gpu and the cpu is down to 10 percent for the entire render for some reason. Please Adobe. Please test your software updates before you release them. Everytime there is an update there is something useful broken. Many of us rely on Adobe CC to get our work done and it's beyong aggravating to have to deal with broken release after broken release. Pleeeeaaase. Windows 10 Pro, AMD 2950x , 128GB ddr4 2667mhz, 2-2080Ti SLI, 3-2tb Samsung 970 Pro NVMe SSds OS-Scratch-Cache
Hello @nocturnetouch,
Thanks for the message. I apologize for the lack of response to this bug report. Are you still having this issue? I hope by now it is fixed. If not, please let us know.
I'll move your post to the Discussions board while we await your information.
Thanks,
Kevin
Copy link to clipboard
Copied
If Premiere was actually using both 2080s, you were doing fine. Premiere hasn't normally worked with multiple GPUs.
It would use one, ignore the other.
And that lack of working with multiple GPUs has led to a fair number of complaints and suggestions over the years.
Neil
Copy link to clipboard
Copied
I'm talking about the rendering process. The rendering process has used multiple gpus for a while now and also utizlied more of my cpu capabilities also. Do you have an explination for that? You also didn't address the underutilization of the cpu. I have thousands of hours in Adobe CC. It isn't my imagination. I regularly monitor the performace of my computer during heavy task. Is your comment regard to rendering? Because I rolled back ME and it rendered using all my gpus. I upgraded to 23.1 and the performance scailed down again.
Copy link to clipboard
Copied
I didn't question that it was using multiple GPUs for you. Just noting that it normally hasn't. So you've been getting amazing use of that setup. Surprisingly so.
I've never run a twin-GPU setup as I've never known anyone that found the second GPU used. It's a typical question when building a pro rig ... whatcha gonna run? If Premiere Pro, the biggest single (typically Nvidia card) you can afford. If Resolve, maybe get a pair, so the combined vRAM is higher. My rig was built by Puget ... to spec for a primary Premiere machine with secondary use in Resolve.
Premiere can at times work with the internal GPU and a discrete card. But even then, Premiere has a nasty habit of using one or the other. Which has resulted in many complaints on the forum here, including the last few months.
And yes, I've been asking the devs to support multiple GPUs for years at NAB. Their comments ... this is an NLE, not a grading app.
And as "rendering" and exporting both use pretty much the same capabilities/code, what you're rendering or exporting to is more important for how Premiere behaves than whether it's an internal 'render' or an export.
Past that, the user performance results were rather wide in 22.x. Some getting pretty bad performance while others were screaming along. 23.x has been even wider, which is just bizarre. Troubleshooting used to be a lot easier and more predictable.
And quite a few users have posted that 23.x has been more sluggish/laggy than 22.x, including under-utilizing their system. So you are definitely not alone there. Which is a right royal pain. Why the differences? No clue. No freaking clue. Which is frustrating.
Neil
Copy link to clipboard
Copied
I think you're confusing editing and time playback using multi GPU vs RENDERING with mult GPUs. When working on a timeline it does use only 1 gpu. When rendering Adobe CC has been good for using multiple gpus. I'm not sure why you're commenting because it appears you are behind on the technical advancements of Adobe CC. "Adobe Premiere Pro uses a single GPU during playback and multiple GPUs for other tasks such as Render In to Out and for export. " Source: https://helpx.adobe.com/x-productkb/multi/gpu-acceleration-and-hardware-encoding.html
Copy link to clipboard
Copied
Thanks for posting that link! I'm one of the few people who've probably read every word of most of their help docs ... frustrating as that is, as most of them are rather limited in working details. But I'd not seen that bit ... so that's not been in that doc for very long.
And ... it was interesting reading. Especially, as I'd been arguing about multiple GPU use at NAB last April with the devs. Without any mention on their part of any change to the multiple-GPU problem. And for many power users, that has been a problem.
And a source of many complaints here too. And as I work with and teach pro colorists, who are based mostly in Resolve or Baselight, rather a source of derision at times.
I'll now be contacting a couple folks to go over that in detail. Ahem.
I've got a 3960x but otherwise our rigs are pretty similar. Remember my comment about user variability? The 23.x builds scream on my machine. On yours, they under-utilize system resources. Why?
It even runs better on my 4-year old Acer Triton laptop than 22.x did. Again ... why on some kit it's good, on others, it's near garbage?
Neil
Copy link to clipboard
Copied
Whatever you can do to get Adobes attention to the bugs many of us are experience, especially us power users, is greatly appreciated. Keep fighting the good fight.
Copy link to clipboard
Copied
Always ... just always.
When they see me coming at NAB, the devs know they're gonna get a pointed list. They're nice people, they all are passionate at editing on their own time, they're mostly Mac geeks (big surprise, right?), and they're nice people.
We do disagree a lot. But politely. And they still smile when I walk up.
Both Resolve and Premiere are getting odd variability of user performance at this time. Very, very bizarre. And puzzlilng to the devs also ... but yes, I'll keep pushing.
Neil
Copy link to clipboard
Copied
Hello @nocturnetouch,
Thanks for the message. I apologize for the lack of response to this bug report. Are you still having this issue? I hope by now it is fixed. If not, please let us know.
I'll move your post to the Discussions board while we await your information.
Thanks,
Kevin
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more