Degraining step involve more data on the server and quality loss at some point
Might be acceptable on some project, but with some project where the vfx sup won't even watch the comp in dailies if there is a difference with the original plate (figurely speaking) it won't do it -- Hugo Leveille Compositing TD Vision Globale [email protected] Sent from my iPhone On Apr 21, 2011, at 10:08 PM, "Brad Friedman" <[email protected]> wrote: > Proper grain management includes a degraining step and a regrain step. > > On Apr 21, 2011, at 10:05 PM, chris <[email protected]> wrote: > >> On 4/21/11 at 3:18 AM, [email protected] (Brad Friedman) wrote: >>> You probably should not even be applying a grade node >>> before grain management. No sense color correcting values >>> that are chemical noise. The question is: what is your >>> d-min value after proper degraining? >> >> actually in this case we want to keep the grain, that's why >> it's shot on film ;) >> >> and i don't want to color correct it, i just want to keep it >> unaffected through the pipeline. obviously if the sub 95 >> values are clamped by the filmrecorder in the end, then this >> is a moot point (guess the only way to be sure is to ask the >> guys who are operating the recorder) ... but there are still >> situations where we want to keep the unclipped data, even if >> it's only grain texture (like adding a lens flare, which >> would bring up the sub 95 values to something visible). >> >> ++ chris >> >> ps: tried to build the pdx formulas in nuke if anybody is >> interested in playing around.. hope i didnt mess things up: >> >> set cut_paste_input [stack 0] >> push $cut_paste_input >> Expression { >> temp_name0 pdxLogReference >> temp_expr0 455 >> temp_name1 pdxDensityPerCodeValue >> temp_expr1 0.002 >> temp_name2 pdxNegativeGamma >> temp_expr2 0.6 >> temp_name3 pdxLinReference >> temp_expr3 0.18 >> expr0 "pow(10, ((red * 1023 - pdxLogReference) * >> pdxDensityPerCodeValue/pdxNegativeGamma)) * pdxLinReference" >> expr1 "pow(10, ((green * 1023 - pdxLogReference) * >> pdxDensityPerCodeValue/pdxNegativeGamma)) * pdxLinReference" >> expr2 "pow(10, ((blue * 1023 - pdxLogReference) * >> pdxDensityPerCodeValue/pdxNegativeGamma)) * pdxLinReference" >> name pdxLog2Lin >> selected true >> xpos -430 >> ypos -118 >> } >> Expression { >> temp_name0 pdxLogReference >> temp_expr0 455 >> temp_name1 pdxDensityPerCodeValue >> temp_expr1 0.002 >> temp_name2 pdxNegativeGamma >> temp_expr2 0.6 >> temp_name3 pdxLinReference >> temp_expr3 0.18 >> expr0 "(pdxLogReference + log10( max( red, 0.00000001 ) / pdxLinReference >> )*pdxNegativeGamma/pdxDensityPerCodeValue) / 1023" >> expr1 "(pdxLogReference + log10( max( green, 0.00000001 ) / pdxLinReference >> )*pdxNegativeGamma/pdxDensityPerCodeValue) / 1023" >> expr2 "(pdxLogReference + log10( max( blue, 0.00000001 ) / pdxLinReference >> )*pdxNegativeGamma/pdxDensityPerCodeValue) / 1023" >> name pdxLin2Log >> selected true >> xpos -430 >> ypos -74 >> } >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected] >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > _______________________________________________ > Nuke-users mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users _______________________________________________ Nuke-users mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
