Well with (evidently) GoPro media which need Lens Distortion effect not being my needs I really do not have any idea especially when you add another CPU intensive effect Warp Stabilization that really leaves me in the dark. Let me think on this one and maybe experiment a bit, I do have a bit ot 4K GoPro footage that I will run on my x99 system to try to find some clues. I basically only deal in editing on tripod mounted 1080 AVCHD and 4K XAVC-S media.
it appears to be not fully utilized. I am curious if I have something misconfigured, or if it is just a Premiere limitation
I wonder what others are experiencing CPU performance wise with rendering similar effects with this footage. Anyone?
This may or may not be the case, but typically when a customer asks, "why isn't my hardware fully being optimized?" there are a lot of potential reasons for readings which may be unexpected. To simplify, this is usually because different codecs respond to rendering and encoding performance in different ways. Some push full use of the CPU, while others only take 30%. While customers expect 100% CPU usage at all times, it can't be the case every time.
The reason that your footage takes a long time to render, in general, is that you're using a couple of computationally intensive effects, one of which is not GPU accelerated. You are also rendering to a different codec than the source footage, both of which are not "smart render" codecs.
With smart rendering, if you transcode your GoPro footage up front to DNxHD and render to DNxHD, you may have better performance in the timeline, faster renders, and faster encodes. Just a couple of suggestions.
Oh my goodness. Transcoding the media to DNxHD made a load of a difference. I used Adobe Media Encoder to "Watch" a folder and it made it practically seamless. I dropped the files to transcode, waited a few minutes, and voilà — media was ready to go. Rendering the same clip preview (from in to out) with Warp Stabilizer enabled takes approximately 10 seconds. This is much more like what I was expecting. Also this produces a 100% CPU usage.
Of course, adding Lens Distortion Correction drops the usage much lower. This is understandable considering we are dealing with, as you said, much more intensive calculations.
Thanks for your recommendations!
1 person found this helpful
premiere should always be close to 90-100%, unless there is a hardware bottleneck (which your system doesn't appear to have).
if you find any effect (like lens distortion) or function (like rendering previews) is preventing premiere from using 90-100% cpu usage regardless of the media format, then there is a problem with that effect or function. if some effect is more cpu demanding (more intensive calculations), then its even more important its functioning properly to use 90-100% cpu usage and avoid a software bottleneck causing low cpu usage.
since you have 100% usage with dnxhd, it appears mp4 footage or your gopro hero 3 footage might be tripping up premiere. if you have other mp4/h264 footage or files to test, you could check if its just the gopro hero 3 footage or all mp4 files having issues. the problem might be a combination of mp4 or gopro hero 3 with certain effects. transcoding is a work-around, but you may want to also submit a bug report about which media and effects cause the low cpu usage to have adobe fix it.
That's the concern I had. Why would it not be using a large majority of the CPU if in fact it is processor intensive calculations. I submitted a bug report as I tested other MP4 files with the same issue.
Good to test and post the bug/feature for the results. Some of the mov & mp4 stuff doesn't work nearly as well in the Lumetri as say, DNxHD or Cineform also. Which I've posted about. It's all the sort of thing that helps the teams make better stuff for us to use ...
Some of the mov & mp4 stuff doesn't work nearly as well in the Lumetri as say, DNxHD or Cineform also. Which I've posted about. It's all the sort of thing that helps the teams make better stuff for us to use ...
there will always be some performance penalty with mp4/h264, its the nature of delivery codec's that were never suppose to be used for recording or editing. so the overhead (latency and extra cpu usage) with mp4/h264 is far greater than dnxhd or cineform and adobe can't fix that. that doesn't mean it should have lower cpu usage like in the first post of this thread. premiere being unable to max out cpu usage is a different issue vs delivery codec decoding overhead.
- premiere being unable to max out cpu usage is a different issue vs delivery codec decoding overhead.
- premiere should always be close to 90-100%, unless there is a hardware bottleneck (which your system doesn't appear to have).
Thanks for clarifying this issue much better than I could. I hope we can find the problem going on here. Thanks to bhwhite for filing the bug.