Adobe Media Encoder CC - You Need to Add Unsupported CUDA Cards to supported_cuda_cards.txt

Forum|Forum|12 years ago
August 30, 2013
4 replies
24886 views

Hi Folks

I'm running on a Mac Pro with an NVidia GTX 770 with 4GB. Premiere Pro CC utilizes the GPU for playback and export but will give you a warning when you first enable CUDA in Mercury Playback Engine. However...

I was noticing that when I queued the export to Adobe Media Encoder CC, it was taking forever to encode simple queued sequences.

After doing a bit of research on the internet and even in these forums I realized that while Premiere Pro was being ok with supporting a non-supported card, Media Encoder was not. I added the GTX 770 to the supported_cuda_cards.txt file locate here: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/ (you will need to be slightly geeky to find and modify this file - more info than I care to provide in this post but you can look up how to locate files in Mac OS).

Voila! AME now encodes super speedly, like 4 times as fast as before!!!

Thought I'd just provide this little tip for people experiencing this problem.

Adobe... can you do something about this? I know it's a corner case but really - maybe something in AME preferences or something... Like "Use CUDA capable card even if not on supported CUDA list" checkbox or something.

Now I can get back to work.

-Keith

This topic has been closed for replies.

Paleus

Participant

Can someone please help me find the file I need to edit using CC on Windows PC?

I'm also not sure what I need to add to this .txt file as I am not entirely sure what my video card is.

Any help would be much appreciated.

Gazzaspi

Participant

Thanks Keith, well spotted..big improvement for me as well.

Gary

E

excited_Genie16B8

Legend

Dude, I never thought of doing this. I ran some tests and found that AME no longer respects GPU acceleration like it did in CS6. PP no longer requires the hack for it to work, I assumed AME wouldn't need the hack either and that Adobe purposefully disabled it in AME for some reason.

I love that you figured this out, and thank you for posting.

K

Keith MoreauAuthor

Known Participant

To Jim

You're very welcome for this. I'm also grateful to you for all the amazing help you give people on this forum. I don't know how you do it but you are always there for people. (I mean always!)

I have used the Adobe and the Creative Cow Premiere forums to research and get information that has saved me countless times, I think it is the least I can do to pay back. I think in general people should post workarounds if they find them. Software is complicated and there are bound to be bugs, Adobe is a company with finite resources so not everything will be discovered nor workarounds explained, especially in this 'unsupported' scenario.

In thinking back on it, I think if Adobe updates AME CC, it should just 'honor' that Premiere Pro is ok with the card, I think that information can be passed along with the dynamic link info from the sequence export or in the sequence somehow. Adding another checkbox i AME prefs adds extra work for Adobe but doing it under the covers is pretty easy.

Regards,

-Keith

K

Keith MoreauAuthor

Known Participant

Something else I discovered inspired by this thread.

In CC Premiere cuda .txt file..my Ge Force GTX 670 card is not on the default list ...yet I have GPU Acceleration. I have a second card in the system (GTX 560) and that is not listed either!

I will add the GTX 670 now but isnt that weird?

Thoughts? Maybe this is what the OP thread is all about?

To Shooternz: Are you sure you have acceleration with Adobe Media Encoder CC? The problem is with AME, not Premiere Pro CC, which will give you one warning when switching from software Mercury Playback Engine to an unsupported CUDA card but will happily use it it when you dismiss the warning. AME will only use CUDA if it 1) Is in the supported list file or 2) the file doesn't exist (according to Jason van Patton)