Skip to main content
dmiraie
dmiraie
Inspiring
January 12, 2017
Answered

"Use Maximum Render Quality" for Youtube ..?

  • January 12, 2017
  • 1 reply
  • 32017 views

Should my Youtube-destined Premiere exports "use maximum render quality"?  Thnx!

    This topic has been closed for replies.
    Correct answer excited_Genie16B8

    If you have CUDA turned on, then no.

    If you have CUDA turned off but aren't scaling any media, then still no.

    1 reply

    E
    excited_Genie16B8Correct answer
    Legend
    January 12, 2017

    If you have CUDA turned on, then no.

    If you have CUDA turned off but aren't scaling any media, then still no.

      A
      Ashley7
      Legend
      July 25, 2017

      Jim_Simon  wrote

      If you have CUDA turned on, then no.

      If you have CUDA turned off but aren't scaling any media, then still no.

      Hi Jim, Jim Simon​ ... I've been reading up on the render quality options... came across your answer here, as well as an answer from 2010 in the following post... Re: "Maximum Render Quality" Better to turn it OFF when using CUDA MPE?

      That other post is old I'm not sure how applicable it is these days which might clarify your answer to this thread...

      In that older thread, it seems that in some cases maximum render quality (MRQ) can benefit some render operations which still use the CPU despite the GPU being present. Does this no longer apply given advances in tech since that old 2010 post?

      I ask because your answer seems to imply that in the presence of CUDA there is no need to check the MRQ box where as that old post seems to imply there are cases for checking MRQ despite a GPU being present... cases which Adobe was apparently interested in diminishing over time. Perhaps they've been diminished to the point where the exceptions to the rule no longer apply.

      A general layperson's test that old thread suggests one can take is to render a complex portion of a timeline twice, once with/without MRQ... if the MRQ render yields a longer encode time with a GPU present, that old thread indicates the longer time means the CPU is being used because MRQ is checked... which therefore supposedly indicates additional work of value is being done in the CPU despite the GPU's presence.

      I'm guessing that way of seeing things may no longer apply or that you know MRQ has specifically no benefit for YouTube as a destination. Just curious which...  Thanks!

      A
      Ashley7
      Legend
      July 26, 2017

      For most work, MRQ MBD aren't needed. Using them will slow down exports, and occasionally may even cause problems. Both have only a few uses these days. From a very useful source ...

      Maximum Render Quality

      This is a high-quality resize operation that should be used when outputting to a different frame size from your sequence. It can reduce aliasing (jagged edges) when resizing images but is of no use when outputting to the same frame size. This operation significantly increases render times so only use it when resizing.

      Render at Maximum Depth

      This renders content at 32-bit color depth. Very few output formats actually support 32-bit color but processing at this depth can produce better quality for compositing and effects operations before being scaled back to the output format's bit depth. It can reduce or eliminate artifacts and banding in your video but that benefit comes at the cost of an increase in processing time, so only use it when completely necessary.

      You may benefit from this option in the following situations:

      • Your source media has a higher bit depth than the format you are outputting to
      • Your sequence contains heavy compositing or lots of layered effects (particularly 32-bit color effects)
      • Your sequence contains very high contrast or very low contrast images (for example subtle gradients)

      Although I do a modest amount of resizing on export, and at times go a bit nuts in Lumetri, I've not found either of them very useful (as far as improving an export) since about PrPro CC2014.

      Multiple-pass exports are also something I've not bothered with since about CC2014. It just doesn't do any better than the first-pass process seems to do these days.

      I've tested exports using each of these imported back into the project, and looked at them with the Program monitor set to 200%, and couldn't see any improvements. I'd suggest if you're concerned, do the same tests yourself. Takes maybe half an hour to do a few quick exports  & review them.

      If something slows the entire processing change down for results that are impossible to quantify, well ... it's only wasted time.

      Neil


      https://forums.adobe.com/people/R+Neil+Haugen  wrote
      For most work, MRQ MBD aren't needed. Using them will slow down exports, and occasionally may even cause problems. Both have only a few uses these days. From a very useful source ...

      Maximum Render Quality

      This is a high-quality resize operation that should be used when outputting to a different frame size from your sequence. It can reduce aliasing (jagged edges) when resizing images but is of no use when outputting to the same frame size. This operation significantly increases render times so only use it when resizing.

      Render at Maximum Depth

      This renders content at 32-bit color depth. Very few output formats actually support 32-bit color but processing at this depth can produce better quality for compositing and effects operations before being scaled back to the output format's bit depth. It can reduce or eliminate artifacts and banding in your video but that benefit comes at the cost of an increase in processing time, so only use it when completely necessary.

      You may benefit from this option in the following situations:

      • Your source media has a higher bit depth than the format you are outputting to
      • Your sequence contains heavy compositing or lots of layered effects (particularly 32-bit color effects)
      • Your sequence contains very high contrast or very low contrast images (for example subtle gradients)

      Although I do a modest amount of resizing on export, and at times go a bit nuts in Lumetri, I've not found either of them very useful (as far as improving an export) since about PrPro CC2014.

      Multiple-pass exports are also something I've not bothered with since about CC2014. It just doesn't do any better than the first-pass process seems to do these days.

      I've tested exports using each of these imported back into the project, and looked at them with the Program monitor set to 200%, and couldn't see any improvements. I'd suggest if you're concerned, do the same tests yourself. Takes maybe half an hour to do a few quick exports  & review them.

      If something slows the entire processing change down for results that are impossible to quantify, well ... it's only wasted time.

      Neil

      Thanks Neil... I am generally the sort of person who will do side-by-side tests to compare results for myself but the nuanced info you have above really helps to make better choices along the way despite any personal informal findings. I mean, I could do (and actually have done) side-by-side tests with my usual DSLR source footage and draw conclusions from that, but it wouldn't give me the resizing and 32-bit effects hints (and more) reflected above... nor would it clue me in should I start using source footage having a greater depth. Or... the one that really gets me... despite my tests showing no immediate apparent benefits, I use the settings just in case my tests didn't cover the mysterious cases where there's a benefit... elaboration as you've presented, I'm saying, removes that mystery and allows one to get more money for my own personal testing. Unless of course I test for each project, wasting time each project, to compare that the project's specific cases so to speak... rather than knowing what's under the hood here. Having just a hint at least can help, is all I'm saying. Wish this were clarified release-by-release in a readme or blog or something.

      So I'm working on a project right now that has some source footage (not photos but video) that is HD or other smaller odd ratios than 1080p (1080p being the output). Since those are scaled up to 1080p in the main timeline, would you recommend pre-rendering those to a mezzanine using MRQ... then pulling that into the main project... those sections don't need much ongoing work from original source so it seems taking care of MRQ upfront with a pre-render might be a good strategy for those effect "resize" operations... then avoiding the MRQ penalty on the main project. Currently, I've been going to CineForm with those but keeping at the original scaling, then scalling the Cineform in the main project... seems this is a case for maximizing scaling processing before the mezzanine (I tend to avoid over processing at that stage as I've gotten burned by doing too much, trying to be too efficient, before heading to mezzanine). What do you think on that?

      Thanks for the 2pass info... that was going to be my follow-up Q. ... okay, so I'll stay away from that for now. ... I'll also take some time out to do some experiments with my particular footage... but with some of the mystery removed the tests themselves will be more meaningful. Thank you for those clarifications.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices