Slow Exporting Performance with Premiere 2019 (Windows)

[jonathanf69699133]

Having the exact same issues. Over an hour to export a 6 minute video with a very capable machine. I think this 2019 release of CC is the final nail in the coffin for me. After being a professional adobe user for 8 years, I'm done. These releases just get worse and worse.

[b_johannes_bryan]

jonathan, is your drive formatted ExFAT? What codec are the source video files in?

[jonathanf69699133]

My drives are always, and have always been, formatted as ExFAT. This is a must for my workflow. The codec is XAVC S from the Sony A6500 and A7 III. I also have dynamic links in my project. I know a lot of these COULD be causing my issue, the thing is, they shouldn't be causing issues. These are all standard things. I shouldn't have to stop using dynamic link, change my workflow or the way I format drives, change my codec preferences etc.

The new curves and other features are cool, but FCP X and/or Resolve are just flat out better choices now. Premiere and After Effects are so full of bugs, slow downs and arbitrary hurdles that it's just not worth it anymore. Then there's also the fact that since 2018 PR and AE only utlilize about 1/4 to 1/3 of my 8th gen Intel CPU/Nvidia GPU processing power at peak loads due to being so unoptimized for modern hardware.

It's sad. I love adobe and WANT to use their products, but I no longer can in a professional environment.

[b_johannes_bryan]

I agree. Very frustrating. Hopefully Adobe will fix it.

[RichG13]

Upgraded to CC 2019 from 2018 and encoding times have doubled for me as well.

Windows 10 Pro

Intel Xeon E5-1630 v4 @ 3.7Ghz processor

Kingston 512GB SSDNow KC400

32 GB RAM

AMD FirePro W5100 v.24.20.12042.5

I used DDU and ripped the GPU driver out and did a fresh install.  Tried both Mercury settings (Software Only and  OpenCL) and processing times are doubled with little to no GPU activity.

[jonathanf69699133]

And of course, same as it has been for years, adobe staff doesn't care about these legitimate threads.

[Kevin-Monahan]

Hi JonathanF,

I understand our engineering staff has helped you with your export and it was a success. I also understand you were given some workflow tips that will assist you in the future. Since you have not returned to the thread, we will mark this one as solved (correct), unless you still have an issue you still need fixed. Let us know!

Thanks,
Kevin

[jonathanf69699133]

No, do not mark this as solved. My exports are not a success, they run, literally, ten times as slow as they did with PR 2018. This is ridiculous. I'm done with Adobe, This is the last month you'll get my money

[Wes Howell · Accepted solution]

Jonathan,

I work on the Premiere Pro engineering team and I'd be more than happy to help you resolve these issues.

We've been trying to isolate issues from a large thread that was headed in many directions.

I have been reaching out to users on the original thread for the past couple days.

Many issues have been related to specific drivers and hardware configurations. 

Can you share your hardware config details and current version of drivers being used?

[jonathanf69699133]

Wes,

I've already provided this information to you, but here it is again. I havn't had time to make a sample test project for you but will when I can get to it.  This is not a driver issue as has been suggested so many times to me in this thread.

It seems like my slow downs are definitely related to linked AE comps.

I am Running:

Windows 10 (Up to date)

Intel i7 8700k

16 GB RAM

Nvidia 1070 - (Driver Version 416.34 and I've tried walking this driver back already as well)

I'm a pro user of many years and have already been through the standard troubleshooting techniques, tried shutting down AE during export as suggested etc. No change. There is some sort of major problem in the link between AE and PR in 2019 which compounds with the already existing horrible utilization of my hardware by adobe products to make this years release unusable. I can edit and render 4K video faster in FCP X on my mac with integrated graphics and an i5 chip than I can on PR using my much more powerful Desktop PC. As a pro user of your products for years, I beg you, along with the rest of a lot of your community here, to stop the team from working on all these new fancy features and catch up on the hardware optimization side.

[Wes Howell]

Trying to clean up these threads and clear up confusion.  It's been hard to track posts and there have been multiple issues in the original  source thread.    I've managed to resolve several of those issues on that thread and am happy to do more investigation here.  If you can share a small project that would be great.   Please LMK.

Curious, are you using a desktop or a laptop?  

Are you seeing differences exporting to NTFS drivers compared to EXFAT?

Have you isolated the majority of the issues be Dynamic Link related?

Wes

[jonathanf69699133]

Hey Wes,

I am on a Desktop PC. My drives are formatted EXFAT, this is critical to my workflow as many of my clients are mac users, but I'll test a render to an NTFS and get back with you.

The issues of this particular slow down are definitely Dynamic Link related, although I can also say that rendering in general, even in last years 2018 version has taken a hit and doesn't utilize my hardware like it should or has in the past. I've tested this by monitoring my performance during many exports.

Thanks,

Johny

[Wes Howell]

Sounds good.

If you can do a quick comparison of a Dynamic Link project between 2018 and 2019 that would be useful too.  Or if you'd like to package up a small test project, I would also be happy to run some tests on my machines.

Not every aspect and feature in Pr is fully optimized for taking advantage of multiple threads. There are some bottlenecks that can vary by workflow.    We are definitely continuing to work on performance improvements including hardware decoding and hardware encoding feature and other things I can't mention.  Lots of moving parts. 

Wes