Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro WYSI *NOT* WYG — problems with Use Maximum Render Quality setting for output

  • WYSI *NOT* WYG — problems with Use Maximum Render Quality setting for output

    Posted by David Lawrence on September 20, 2012 at 3:10 am

    Hi All,

    I’m enjoying my transition to Premiere Pro 6 very much and so far it’s working well. I recently used it on a simple job. Doing the job itself was a breeze, but I ran into an output problem that surprised me. I’m hoping you can help.

    My workflow involved sending my client h.264 previews, as well as screen grabs made using the Export Frame button in the Program monitor.

    When the video was finished, I exported to ProRes 422 with the Use Maximum Render Quality setting checked (I left it off for the h.264 previews).

    I was surprised that the final render for a particular effect was so much lighter than the screen grab and h.264 client previews. I did a test render to ProRes with Maximum Render Quality off and the shot looked correct. I don’t think this is a gamma bug. Based on my tests, Maximum Render Quality is significantly changing the way the video looks in this shot.

    The effect I was going for was a shaped spotlight. I made a white filled polygon over a black background in the titler tool and overlaid it on top of the video below at 60% opacity. In the end, I went with a different technique, in part because of the inconsistency between the previews and the final. Here are screen shots:

    Question: how can I avoid this in the future? What do I need to do to make sure what I see in the Program monitor is *exactly* what I’ll get in my final render?

    Thanks for your help!

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

    David Lawrence replied 13 years, 8 months ago 6 Members · 12 Replies
  • 12 Replies
  • Tero Ahlfors

    September 20, 2012 at 4:08 am

    Have you checked your prores codec setting? The gamma correction should be turned off. It’s on by default.

  • David Lawrence

    September 20, 2012 at 4:34 am

    [Tero Ahlfors] “Have you checked your prores codec setting? The gamma correction should be turned off. It’s on by default.”

    Hi Tero,

    In my screen shots above, the ProRes codec settings are identical. The only difference is the Use Maximum Render Quality setting.

    The ProRes gamma setting makes no difference. I tried the test again making sure to specify that gamma was set to none and had the same results.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • Erik Lindahl

    September 20, 2012 at 7:50 am

    Is it just a file-viewing problem? I.e. do the exported elements look different if viewed on an externa monitor through Premier or After Effects?

  • Tero Ahlfors

    September 20, 2012 at 11:10 am

    Ok,

    Do you require the maximum render quality tab to be checked eg. do you have any resizing or scaling in the video?

  • Petros Kolyvas

    September 20, 2012 at 4:50 pm

    I’ve found similar issues; I can’t export ProRes or DNxHD with Maximum Render Quality checked. Opacity and multiple layers involving transparency don’t render out properly.

    This is a carry-over issue from CS5.5 and seems to affect Quicktime-wrapped destination media.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • David Lawrence

    September 21, 2012 at 3:13 am

    [Erik Lindahl] “Is it just a file-viewing problem? I.e. do the exported elements look different if viewed on an externa monitor through Premier or After Effects?”

    I don’t have an external monitor. These files are for all digital delivery and distribution (web, and mobile devices) so I use my monitor as a reference and so far no complaints from the client ever.

    The maximum quality rendered file looks wrong in any application I play it back in.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • David Lawrence

    September 21, 2012 at 3:16 am

    [Tero Ahlfors] “Do you require the maximum render quality tab to be checked eg. do you have any resizing or scaling in the video?”

    No scaling, but I am transcoding from XDCAM EX to ProRes for the master. I notice that the video looks grainier if maximum render quality is unchecked. With it on, it looks better. The difference is subtle, but I see it and I want to give my clients the best quality I can.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • David Lawrence

    September 21, 2012 at 3:18 am

    [Petros Kolyvas] “I’ve found similar issues; I can’t export ProRes or DNxHD with Maximum Render Quality checked. Opacity and multiple layers involving transparency don’t render out properly.

    This is a carry-over issue from CS5.5 and seems to affect Quicktime-wrapped destination media.”

    Wow, really? This is a huge problem if true. Is this documented anywhere?

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • Jon Barrie

    September 21, 2012 at 10:53 am

    Are you using a Cuda Card? Try to turn that off and work in Software only mode. The setting with CUDA puts the export into linear color space, which lifts the Gamma, turning it off takes you out of the color space change.

    – JB

    Jon Barrie
    Adobe Video Solutions Consultant ANZ
    Jon’s YouTube Tutorial Page
    follow Jon with twitter

  • Chris Tompkins

    September 21, 2012 at 6:02 pm

    Your not alone, I see this with the drop shadow effect too.
    It was a problem with CS5.5 as well.

    Lame Adobe.

    Chris Tompkins
    Video Atlanta LLC

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy