Skip to main content
Participant
March 21, 2019
Answered

Adobe CC 2019 doesn't utilize my 1080ti like Adobe CC 2018

  • March 21, 2019
  • 2 replies
  • 870 views

I built a Hackintosh (i7 8700K, 11GB 1080ti, Mac OS High Sierra 10.13.6) and I just upgraded all my 2018 CC apps to 2019 yesterday as I heard it's fairly stable build now. After a day and a half, I noticed everything being much slower in Premiere, After Effects and Encoder (main apps I use). 4K footage isn't playing back as smoothly as it did in Premiere Pro or AE. But the main difference is in Encoder where my render times more than doubled. It's recognizing my CUDA GPU in all the apps, but when switching between rendering options of Software Only to CUDA, it makes no difference. And the temperature on my GPU says it's not being utilized.

I understand that there are major changes in GPU support in 2019 CC but that only applies to Mojave (which doesn't support CUDA), right? High Sierra should still support this GPU as far as I understand. I also currently have the latest CUDA and display driver.

I downloaded 2018 again and these were the render times for the same exact 7 minute video clip (H.264, 1.5mbps target, 3mbps max):

Media Encoder 2018: 14min 8 sec

Media Encoder 2019: 31min 32 sec

I cleared my cache before rendering. I uninstalled CUDA and reinstalled it. Did the same with Adobe and clean installed the apps. No difference. I'm not quite sure why Adobe 2019 CC is not using my GPU as it did in 2018. Any ideas?

This topic has been closed for replies.
Correct answer alexp51918335

Seems like the problem is actually the format of the source drive, ExFat, and using ProRes 422. Nothing to do with GPU, OS.

I got the below excerpt from this link: Poor performance: Premiere Pro CC 2019 13.0 (Mac)

The issue is related to the combination of: Premiere Pro 13.0 (2019) / ExFat / Apple ProRes 422 Codec.

Premiere Pro 2019 -

I've used the same files, on the same drive in Premiere Pro 2018 without any issue, but when the same project is opened in Premiere Pro 2019, it gets really slow. I've created a new project in PP2019 and still have the issue with this same drive and same files.

ExFat -

When I move the files to a drive formatted Mac OS Extended (Journaled) , no problems. It works just fine. Even with the same project, same ProRes files. ExFat drive on a USB 3.0 or 2.0 bus, is slow. I'm going to test is on Thunderbolt and USB-C next.

Apple ProRes 422 Codec -

When I used the same project file and the same ExFat drive, but work on H264 files, no issues.

2 replies

alexp51918335AuthorCorrect answer
Participant
March 26, 2019

Seems like the problem is actually the format of the source drive, ExFat, and using ProRes 422. Nothing to do with GPU, OS.

I got the below excerpt from this link: Poor performance: Premiere Pro CC 2019 13.0 (Mac)

The issue is related to the combination of: Premiere Pro 13.0 (2019) / ExFat / Apple ProRes 422 Codec.

Premiere Pro 2019 -

I've used the same files, on the same drive in Premiere Pro 2018 without any issue, but when the same project is opened in Premiere Pro 2019, it gets really slow. I've created a new project in PP2019 and still have the issue with this same drive and same files.

ExFat -

When I move the files to a drive formatted Mac OS Extended (Journaled) , no problems. It works just fine. Even with the same project, same ProRes files. ExFat drive on a USB 3.0 or 2.0 bus, is slow. I'm going to test is on Thunderbolt and USB-C next.

Apple ProRes 422 Codec -

When I used the same project file and the same ExFat drive, but work on H264 files, no issues.

Participant
March 27, 2019

Glad you figured out your issue! Sadly, it seems we had different issues after all.

I've been using the exact same drive and project from 2018 to 2019, but using Mac OS Extended (Journaled) and XAVC files.

Participant
March 23, 2019

Similar situation here. I'm on a 2018 15" MPB with an external RX580.

PP 2018 utilizes the eGPU perfectly, while PP 2019 uses it (to some degree) while playing back the timeline. When exporting, PP 2019 does not even touch the eGPU, but relies on internal graphics and the MBP's dedicated 560X. It's pretty sad.

Adding my voice here to hopefully amplify the thread and hear any potential fixes.