5dtorgb vs adobe media encoder7/14/2023 I'm way out on the bright side of nowhere here. I’m sure other people are reading this as well.In AME, I created an encoding Preset where I didn't select the "Match Source" tick box and instead set the Height & Width dimensions manually to 1920x1080. Can’t thank you enough for your time and knowledge. Regarding prior question # 2, When I check the Max Render in PPRo sequence, does that only affect the timeline render in PPro and has nothing to do with the export to disc? Meaning, can I uncheck it in PPro and just check it in AME for disc output? (I’m not using previews in AME when exporting to disc.)Īnd for prior # 3, If I should check it in PPro, should I check it in AME as well? I get the feeling it will help for upscaling, I guess some testing is in order, because when checking that box it adds a great deal of time when processing a 2 hour film so I’d like to know if it is all worth it. I wish there was more unity in the answers. “Mo” says to check it for up or downscaling but doesn’t issue reason or referral. I think jaggies occur during downscaling, which is what he may be referring to. “Neil” says to check the Max Render when scaling, but doesn’t clarify upscale or downscale. I’ve read the posts in the links you gave me. Thanks Larry for your quick and informative reply. Just thought I’d append this, for any of your users that have experienced this phenomenon. This is a bit annoying, as premiere likes to “randomly” change my default export settings from time to time, so I have to always confirm that “Use Maximum Render Quality” box is checked. AND checking the box in the AME preset doesn’t seem to help either…I HAVE to check it from the initial export window in premiere, or some gfx end up pixelated. Also, checking “Use Maximum Render Quality” in sequence settings doesn’t seem to make any difference with this phenomenon, btw….only when exporting. Or, maybe I’m doing something incorrectly elsewhere in my settings/workflow? I always use “Set to Frame Size”, not “Scale to Frame Size” on graphics, btw. I should mention that I’m on a “maxxed-out” Mac Pro 5,1 (cheesegrater) with an Nvidia GTX 770 card using CUDA (which means I’m still in High Sierra & Premiere 2019, to keep CUDA support), so maybe newer machines/premiere 2020/Metal have made this checkbox obsolete, like you said. I’m not sure why some and not others (I’m sure it’s connected to scaling of some sort, but strangely it doesn’t seem to be determined by the resolution of graphic, as some that are HIGHER res than sequence get pixelated sometimes, while some others that are lowered and being scaled up do not), but it happens. I’ve found that if I don’t check “Use Maximum Render Quality” in export settings when exporting, that SOME of my graphics/images end up pixelated. Hello Larry, thank you for all your work over the years helping us editors! Given the number of effects that are now GPU accelerated, there is no benefit to using Maximum Bit Depth, because that is used by the GPU automatically. In that case, turn Maximum Render Quality on. When exporting from Premiere, leave both these options off unless you are scaling images larger and seeing jagged lines on the edges of your images. ![]() When creating a new sequence in Premiere Pro CC, make sure both options are turned off. In Adobe Media Encoder, which handles all exports from Premiere, make sure that the Video Renderer is set to Metal (or the soon to ship Metal 2). As of this time, scaling is still CPU-based, and only effects calculated using the CPU are affected by this setting. The only reason to turn it on is if you are scaling your images – up or down – and see jagged edges on clearly defined diagonal lines. If you have a GPU, this, too can be turned off. If you have a GPU, Maximum Bit Depth is irrelevant as you’re already getting that performance if applicable to your media. The short answer is: As Adobe migrates toward more GPU-based effects both of these options are quickly becoming unnecessary. But, what do they do and when do you use them? ![]() These settings can be applied to individual sequences or an entire export. Because of this, these two render options appeared many years ago and have been confusing editors ever since. However, converting Premiere from CPU-based effects to GPU-based effects is neither simple or fast. Since then, as GPUs took over the rendering load from CPUs, editing has gotten much, MUCH faster! A GPU is optimized for rendering digital images quickly in a way that a CPU just can’t. And, at the time, I thought that was amazingly fast!) ![]() (I still clearly remember adding a Gaussian Blur to a clip in Premiere 4, back in 1998, that took 30 seconds to blur a single frame of video. And, as you can imagine, that took a long time. In the beginning, before GPUs existed, all video scaling and rendering was done by the CPU.
0 Comments
Leave a Reply. |