-
PP CC is not using my NVIDIA K5000 GPU for rendering
I believe this may be a GoPro/PP issue but I just got a new Hero3+ GoPro. I am running CC on my Win7 workstation. This is a HexCore 3.3Ghz i7 Extreme with 24Gb of ram and I have a Nvidia K5000 Quadro video card. Also, before purchasing my GoPro I have owned Neoscene and that is installed on my workstation. I installed my GoPro Studio software on my workstation and I see that it installed a 32 bit plugin into the Core folder for PP, which it does not like. I just let PP complain and go forward.
I used the GoPro Studio software to convert the raw files from the GoPro disk to .avi files on my local machine. I then imported those files into PP. I have a very simple composition that is only 90 seconds long. I put the CC Lens filter on the sequence to remove some of the fisheye from the GoPro. If I look at the project settings for my project PP clearly see’s my Nvidia Quadro card:
I put the playhead on the first clip which is 80 seconds long and clicked that clip on the timeline. I then went to Sequence -> Render Effects In to Out. PP starts to render and tells me it is going to take and hour and 10 minutes to render 80 seconds of video!!! I waited a bit to see if that figure was going to change but it never did. I have GPU-Z running on my workstation to monitor how my GPU is being used. When this render was going on GPU-Z showed the following activity:
Clearly something is amiss here.
For grins I loaded a previous Non-GoPro clip project and did a quick render on a sequence and my GPU took off and things rendered as I expected. I then took my entire GoPro project over to my MacBook Pro and loaded it into PPCC on that machine. This is a circa 2011 MPB with a QuadCore i7 and 16Gb of ram. PP on the Mac complained about the CC Lens filter as it does not exist on the Mac. I downloaded a trial version of the Dashwood Horizon plugin and did the same procedure described above. My MBP, without any GPU acceleration as it has a AMD video card, rendered the sequence in a little over 3 minutes.
If anyone has a clue as to what in blue blazes is going on I’d appreciate it.
-
7 Replies
-
Neither CC Lens (that’s an After Effects plugin, right?) nor Premiere’s native Lens Distortion are accelerated effects, so it makes sense that the needle on your GPU utilization wouldn’t budge.
Look for this icon next to an effect’s name to see if it’s accelerated:
[image].You can also also click that icon next to the effects search box to filter for accelerated effects.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
Thanks Walter, I will look at that. That being said, does it really sound reasonable that given I have 12 threads running on a 3.3Ghz CPU that it’s going to take 90 minutes to render 80 seconds of HD video? That to me sounds just crazy.
Just checked. You were right. I disabled the lens distortion correction and it took off and rendered the clip in less than a minute so it must have been the filter. Strange that it would take that long to fix lens distortion. I’ll have to throw that in Nuke and see what it does there.
-
CC Lens is an Ae-native effect, not a Pr-native effect (that I am aware of). I am not sure what that means for processing pathway or for efficiency. This might be worth trying in Ae, as it might be significantly faster there.
You might also try Pr’s native Lens Distortion effect instead of CC Lens in Premiere.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
If you download the latest gopro studio you will see it now has a fisheye correction feature.
———————————————–
Adobe Certified Expert Premiere Pro CS6
Adobe Community Professional -
Actually, in checking, I was using the native PP lens correction not the AE one. I did see the option in the new version of GP Studio for Lens correction. I will take a look at that. Just trying to figure out the best workflow for working with this camera. Takes some amazing video but it is fairly distorted.
-
Hi Phil,
Rather than rendering the timeline itself, did you try exporting via Media Encoder? The format you are rendering to, or exporting to, can have a bearing on the speed. Typically not recommended to render the timeline itself, unless you really need to for smooth preview, but then do NOT check “Use Previews” in AME otherwise you are transcoding that footage twice.
Hope this helps
Jeff Pulera
Safe Harbor Computers -
Hi Jeff,
Yea I actually did that. Usually, since PP is so fast with my graphics card I don’t render in the timeline as you mentioned. The GoPro is new to me so I was investigating things with it. The fisheye is an obvious effect you get with that camera and it is not always a desired effect. it is far less noticeable when making an outside shot but this particular footage was taken inside so square walls and corners looked particularly bad.
Thanks for the info.
Reply to this Discussion! Login or Sign Up