Copy link to clipboard
Copied
This is what I noticed - when I exported my final media in 13.0 I was able to select hardware encoding in Encoding Settings -> Performance. However, after upgrading to 13.1, when I try to set the same hardware encoding, I get a message that my system doesn't support hardware encoding. And yes, the render time is orders of magnitude slower.
My system:
It seems strange that the same hardware configuration could be supported for encoding in 13.0 but not in 13.1.
Okay - I found a way to get the export time to be reasonable. What I did was to take an old project that I developed in 13.0 and open it in 13.1. The system then converted the project file and when I used it to export, the rendering took minutes rather than hours. Strangely enough, when I re-opened the 13.1 file that I created from scratch, the render times for that file are now reasonable as well. I suspect this has to do with corruption within the media cache but I can't be sure.
Copy link to clipboard
Copied
Make sure your drivers are up to date, starting with your GPU. Pull drivers directly from the manufacturer's website, NOT Windows Update. Hope this helps!
Copy link to clipboard
Copied
If the drivers weren't up to date, would I have been able to set hardware encoding when using 13.0? Something changed between 13.0 and 13.1.
Copy link to clipboard
Copied
It turns out that I was able to enable hardware encoding by tweaking some of the output parameters. However, it is still painfully slow to render the output file. At least 5 times the render time of the same project when using 13.0.
Copy link to clipboard
Copied
Wayne,
Sorry, man. Can we please see a screenshot of your Export Settings dialog box? Also your Project Settings > Renderer.
Thanks,
Kevin
Copy link to clipboard
Copied
This is what the progress bar looks like 60 seconds after clicking Export:
Copy link to clipboard
Copied
Hi,
Nothing looks out of the ordinary, but I have a feeling it's something we're not seeing or some info about your system which is not yet known. For example, this sounds like a desktop but could it be a laptop with an integrated CPU/GPU?
If it is a laptop, then I feel your integrated CPU/GPU is at fault and is running the incorrect Intel drivers. For that, this post may help: Extremely Slow Exports with Premiere 2019
Thanks,
Kevin
Copy link to clipboard
Copied
It's a desktop. I've never had any problem in the past with any previous versions of Premiere Pro. Thanks for the link but it seems to focus on the differences between PrPro 2018 vs. PrPro 2019. The problem I find is between PrPro 2019 13.0 (which renders fine) and PrPro 2019 13.1. So it would seem to be a moot point the differences between the major versions with respect to driver sensitivity.
Something has changed between 13.0 and 13.1 that affects the final rendering and I'd be glad to work with anyone on the technical team to resolve it. If I have to I'll just revert to 13.0 but then I'll never be able to upgrade.
Copy link to clipboard
Copied
Same here.
Win 10 Pro (1809)
9900k
64GB RAM
GTX 2070
Last week everything was fine, since monday encoding is incredibly slow, no matter if directly out of Premiere or AME.
I have two projects right now, one in FHD, one in 4K, 5 and 4 minutes long. I encoded early versions last week to show my coworkers, encoding took around 10 minutes, both once in h264 and h265. Hardware encoding was always enabled.
Tweaked the projects just a little bit (changed text in lower thirds, removed a clip) and right now, encoding takes around 6-18 hours?!
Export Settings are the same like last week.
Tried reinstalling Premiere, deinstalled gpu drivers with DDU and installed (from 419.X) to the newest 430.86 version (directly from nvidia). Nothing changed.
While exporting again, i noticed that for the first few seconds of encoding my CPU and GPU are completely utilized @100%, but it suddenly stops and they won't go over 1-2% of utilisation. There is definitely no thermal throttling, CPU won't go over 50°C and GPU is at 65°C for a short moment.
Also tried encoding an older project in Premiere 13.0 with the same effects and lower thirds, which works absolutely fine?
//Edit:
I also just installed the newest, for my DELL available, UHD 630 drivers from 25.20.100.6471 to 25.20.100.6617. No changes.
Copy link to clipboard
Copied
I had similar Issues on my Windows 10 computer. Playback was also painfully slow and GPU (GTX 1080 Ti) was rocking at 100%.
A driver update solved the issue for me (GRD - whql - 430.86 - just released last week). Make sure you do a clean install and also remove CUDA Software/Drivers in case you have them installed separately. That worked for me.
I had tried various drivers and that one solved the problem. So do a double check on those drivers.
Copy link to clipboard
Copied
Yeah but that's not the issue. Playback is working fine and GPU isn't running at 100% but at 0-1%.
Drivers are removed with DDU and the most recent downloaded from nVidia / DELL.
Copy link to clipboard
Copied
Yes - preview/playback is fine. It's just the export that's painfully slow. And again, the distinction is between 13.0 and 13.1, not between the major versions
Copy link to clipboard
Copied
Didn't help a bit. I installed 430.86 and the rendering (both for previews and for final media export) is still incredibly slow between the two minor versions. Something significant changed. I noticed that the prproj format is different between 13.0 and 13.1 and the file will be converted when going from the former to the latter. That's probably a clue.
Copy link to clipboard
Copied
Okay - I found a way to get the export time to be reasonable. What I did was to take an old project that I developed in 13.0 and open it in 13.1. The system then converted the project file and when I used it to export, the rendering took minutes rather than hours. Strangely enough, when I re-opened the 13.1 file that I created from scratch, the render times for that file are now reasonable as well. I suspect this has to do with corruption within the media cache but I can't be sure.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now