I'm happy with the rendering speed in PPro, and I see that hardware rendering is working there. It's been my understanding that AME was engineered to run in the background, allowing other work to be done in PPro without the 2 "getting in each other's way". While I'm waiting for AME to finish, this thread raises questions in my mind. I just made this change in the AME ".txt" file for my GeForce GTX 670 (i7, WIn 7 Pro, 32 GB, and I know it's not "certified" for CUDA), and now have it in both the PPro and AME ".txt" files. Adding another checkbox i AME prefs adds extra work for Adobe but doing it under the covers is pretty easy. 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. 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. I think in general people should post workarounds if they find them. 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 don't know how you do it but you are always there for people. I'm also grateful to you for all the amazing help you give people on this forum. Like "Use CUDA capable card even if not on supported CUDA list" checkbox or something. can you do something about this? I know it's a corner case but really - maybe something in AME preferences or something. Thought I'd just provide this little tip for people experiencing this problem.Īdobe. Voila! AME now encodes super speedly, like 4 times as fast as before!!! 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). I was noticing that when I queued the export to Adobe Media Encoder CC, it was taking forever to encode simple queued sequences.Īfter 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. 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. I'm running on a Mac Pro with an NVidia GTX 770 with 4GB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |