Activity › Forums › Adobe Premiere Pro › Adobe Premier Pro CC not using GPU in playback or encoding…
-
Adobe Premier Pro CC not using GPU in playback or encoding…
Tero Ahlfors replied 10 years, 11 months ago 5 Members · 12 Replies
-
Ruski Snajper
September 1, 2015 at 11:08 pmSo, somebody, whoever it was, didn’t thought it’s worth mentioning that none of the default codecs do any GPU
GPU Acceleration is what I got Adobe Premiere Pro for, because Vegas doesn’t appear to use it much either – i believe this is false advertising, i will be returning the product if I don’t get this POS working under a month.
I don’t do any effects, I shorten the videos, or I combine multiple clips, that’s it, so somehow, for some reason that doesn’t apply for GPU acceleration, WTF?
I hear some people saying “dump radeon go nvidia”, it is still not an excuse this is Adobe’s fault and when they display “GPU Acceleration” they should have made it clear which ever brand actually works and displayed notes for what GPU acceleration actually applies to.
Plus, I’ve seen videos on youtube folks posting reviews of GPU Accelerated encoding and times … however I’m not sure if they were sure it was actually using GPU since the video I looked at didn’t show any … I had searched web, there was absolutely nothing from Adobe.
Then I happen to find, which usually happens, I find what I need on some hole of the internet when it’s already too late, some link that sends me to an adobe website which talks all about GPU acceleration, after 10 links I get here.
https://helpx.adobe.com/premiere-pro/system-requirements.html
Oh so because I happen to have a “too new” GPU, it has OpenCL, I don’t understand, since when OPENCL needs per-GPU model code, just ridicolous.
Then I find this one https://blogs.adobe.com/premierepro/2013/06/adobe-premiere-pro-cc-and-gpu-support.html
Which hopefully happens to have this:
This is no longer necessary in Premiere Pro CC. As long as you have a reasonably modern card with at least 1GB of VRAM, you will still be able to enable that card in the Project Settings dialog.
There is no such setting, nor a warning of any “this GPU is not certified”.
And the link it sends me to is an old one for CS5
https://blogs.adobe.com/premierepro/2011/02/cuda-mercury-playback-engine-and-adobe-premiere-pro.html
Which finally says after saying “some effects” etc pretty much nothing that I planned to use for the next year:
It’s worth mentioning one set of things that Premiere Pro doesn’t process using CUDA/OpenCL: encoding and decoding.
Ah it’s just worth mentioning in a little small blog post, nothing to worry about, three two one, one two three, what the heck is bothering me.
And the CS5 link send me to CS6 in which says this:
Everything that Premiere Pro CS6 can process with CUDA, with four exceptions:
Fast Blur effect
Gaussian Blur effect
Directional Blur effect
Basic 3D effectAnd what can CS6 process with CUDA ?
Oh … “The only thing added for Premiere Pro CS6 is the Push transition.”
So … they added nothing in CC ?
That’s all folks, i’ll be back in 50 years counting my retirement savings and happily GPU Accelerating my H.795 codec.
How can you people live with this, I mean, what the heck those little effects that are used in most projects less than 20% and not even all of them to combine that benefit, here and there, not GPU accelerating the actual coded makes in my opinion the whole feature like a tacked on little thing, a really small deal from what the internet was telling me. What a JOKE, how long is H.264 out there, what’s going on, is adobe still in 1998 ?
-
Tero Ahlfors
September 2, 2015 at 8:08 am[Ruski Snajper] “How can you people live with this”
Premiere (and computer hardware) has come a long way. I’m doing my work on a older iMac and I don’t even use the GPU on it. H264 is faster than realtime as are Prores and MXF based codecs that are mostly used in pro productions. I don’t know what kind of performance you are expecting from it. Also it’s pretty weird that people are staring at CPU and GPU usage and are really concerned that they’re not using 100% all the time, because that’s not how software uses the available resources.
Reply to this Discussion! Login or Sign Up