Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve How to bypass input LUT for selected shot?

  • How to bypass input LUT for selected shot?

    Posted by Andrew Shtern on July 28, 2011 at 9:13 am

    Hi all.
    I have an Alexa project, about 50 cuts, with couple of time-lapse videos, shot on DSLR.
    I’ve started to grade before the time-lapses was shot, so in project settings i’ve applied input LUT for Alexa. But now, of course, this lookup also affected the DSLR shots.
    So question is: is it possible to turn off or bypass input LUT for some of the shots on timeline, or the only way is to work without general input LUT, and then apply input LUT to every shot, where one is necessary?

    Andrew Shtern
    Editor/Colorist
    The Coffeepost @Kiev, UA

    Mike Most replied 13 years, 9 months ago 3 Members · 4 Replies
  • 4 Replies
  • Sascha Haber

    July 29, 2011 at 6:20 am

    Or you just go to th Arri site and bake yourself a fine Vodie-LOG C Lut and apply that to the ones you want to exclude.

    A slice of color…

    DaVinci 8.0.1 OSX 10.7
    MacPro 5.1 2×2,4 24GB
    RAID0 8TB eSata 6TB
    GTX 470 / GT 120
    Extreme 3D+ WAVE

    http://www.saschahaber.com

  • Mike Most

    July 30, 2011 at 4:38 pm

    Sorry, but I have to ask the question: why are you applying an Arri LUT as an input LUT? You’re much better off using it as either an output LUT or in a downstream node and thus having access to all of the information in the logC original. By using the LUT on the input, you’re basically defeating the entire purpose of using the LogC format.

  • Sascha Haber

    August 1, 2011 at 2:08 pm

    Well, Does it actually matter when Resolve treats values in floating point ?
    I had bad experiences in Scratch when using the Alexa LUTs as an output or viewing or grading LUT.
    When changing color, it looked like is was squeezed through the Lut and we had funny banding everywhere.
    That also occurred with animated blends and color animations.
    But when using the LUT first, the animations looked smooth.

    A slice of color…

    DaVinci 8.0.1 OSX 10.7
    MacPro 5.1 2×2,4 24GB
    RAID0 8TB eSata 6TB
    GTX 470 / GT 120
    Extreme 3D+ WAVE

    http://www.saschahaber.com

  • Mike Most

    August 1, 2011 at 5:32 pm

    Yes, the order of operations most definitely makes a difference. That is one of the reasons for the node based pipeline, to be able to control that processing path. Placing a LUT, particularly a log to video LUT, at the beginning of the processing path can and does yield a different result than placing it at the end. Not to mention the additional degree of control you gain by being able to grade both prior to and after the LUT transform. Based on my own experiments, the path is not concatenated, but it is applied in the order specified by the node tree. The only way it gets concatenated is if you generate a LUT that represents that entire tree.

    If I’m wrong about this, I would invite either Rohit or Peter to please correct me.

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