Try using a isnan() or isinf() on a colour expression node to set those
down to zero or some other value.
set cut_paste_input [stack 0]
version 8.0 v5
push $cut_paste_input
Group {
name dBadPixels
help "Sets NAN and INF pixels to a specified value.\n\nDiogo Girondi"
tile_color 0x31c9b2ff
selected true
xpos -57
ypos -99
addUserKnob {20 dBadPixels}
addUserKnob {6 replace_nans l "Replace NaNs in " +STARTLINE}
addUserKnob {6 nR l R -STARTLINE}
nR true
addUserKnob {6 nG l G -STARTLINE}
nG true
addUserKnob {6 nB l B -STARTLINE}
nB true
addUserKnob {6 nA l A -STARTLINE}
nA true
addUserKnob {19 nan_color l Color}
nan_color {0 0 0 0}
addUserKnob {6 nan_color_panelDropped l "panel dropped state" -STARTLINE
+HIDDEN}
addUserKnob {26 ""}
addUserKnob {6 replace_infs l "Replace INFs in " -STARTLINE}
addUserKnob {6 iR l R -STARTLINE}
iR true
addUserKnob {6 iG l G -STARTLINE}
iG true
addUserKnob {6 iB l B -STARTLINE}
iB true
addUserKnob {6 iA l A -STARTLINE}
iA true
addUserKnob {19 inf_color l Color}
inf_color {0 0 0 0}
addUserKnob {6 inf_color_panelDropped l "panel dropped state" -STARTLINE
+HIDDEN}
addUserKnob {26 ""}
}
Input {
inputs 0
name Input
xpos -313
ypos -272
}
Expression {
temp_name0 nanR
temp_expr0 parent.nan_color.r
temp_name1 nanG
temp_expr1 parent.nan_color.g
temp_name2 nanB
temp_expr2 parent.nan_color.b
temp_name3 nanA
temp_expr3 parent.nan_color.a
expr0 parent.nR?isnan(r)?nanR:r:r
expr1 parent.nG?isnan(g)?nanG:g:g
expr2 parent.nB?isnan(b)?nanB:b:b
expr3 parent.nA?isnan(a)?nanA:a:a
name ReplaceNaNs
xpos -313
ypos -238
disable {{!parent.replace_nans}}
}
Expression {
temp_name0 infR
temp_expr0 parent.inf_color.r
temp_name1 infG
temp_expr1 parent.inf_color.g
temp_name2 infB
temp_expr2 parent.inf_color.b
temp_name3 infA
temp_expr3 parent.inf_color.a
expr0 parent.iR?isinf(r)?infR:r:r
expr1 parent.iG?isinf(g)?infG:g:g
expr2 parent.iB?isinf(b)?infB:b:b
expr3 parent.iA?isnan(a)?infA:a:a
name ReplaceINFs
xpos -313
ypos -214
disable {{!parent.replace_infs i}}
}
Output {
name Output1
xpos -313
ypos -185
}
end_group
On Mon, Jun 23, 2014 at 1:57 PM, Michael Garrett <michaeld...@gmail.com>
wrote:
> I would set an expression based on anything above a very large number
> going to zero. As long as that large number doesn't encompass any actual
> valid scene values. Then you can run your MaxLuma curve tool.
>
> depth.Z>1000000?0:depth.Z
>
>
>
> On 23 June 2014 12:24, HSK <charhar...@gmail.com> wrote:
>
>> Hi there,
>>
>> On a current project I'm working on, our depth passes are spitting out a
>> colour of
>>
>> 3.4e+38 on empty areas. There's nothing I can do about the way the
>> AOV's(passes) are spit out.
>>
>> Does anyone here have a handy and quick way of selecting those empty
>> areas?
>>
>> I want to apply a curve tool for max luma pixel in an automated way, and
>> cant because of these empty areas...and I don't know how to tell the curve
>> tool to ignore that colour.
>>
>> I tried using keylight and typing in that number, and it read as
>> nan,nan,nan
>>
>> Any ideas?
>>
>> Thanks!
>>
>> Steve
>>
>> _______________________________________________
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>
>
> _______________________________________________
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
