Detects illegal pixels, like NAN and INF, in images.
Shaders and renderers can generate illegal floating point values every once in a while. This operation detects bad pixels, specifically NAN and INF, and either highlights them or fixes them. It can also notify you through a warning or an error which frame and plane have bad pixels.
Because the data is missing from that pixel, it can be zeroed out or replaced by blending together surrounding pixels. When zeroing pixels, the entire pixel is zeroed even if only one component is bad (to avoid color shifting).
If pixels are replaced, and only a part of the pixel’s components is bad, only that component will be replaced. If a large block of bad pixels is present, it will attempt to iterate up to 16 times to break down the block. Large blocks will look like blurry spots in the image, so you may want to limit the number of bad pixels to replace.
Bad pixels are only detectable in floating point formats (16 and 32 bit floating point). Integer formats will have already been quantized to a valid (but possibly random) color in the renderer, making them impossible to detect.
Bad pixels will not be detected in planes or areas of the image that are not used during the cook.
Illegal pixels can be flagged or fixed. Often, flagging is used to debug the shader, while fixing is used to attempt to continue with the image as-is.
If a bad pixel is found, this operation can raise a warning or an error.
|“Bad Pixel Limit”|
The number of acceptable bad pixels. If more than this number are in the image, the cook will halt.
Start of sequence
End of sequence
Input sequence length
Sequence frame rate
Number of planes in sequence
Width and height of image
Image index (0 at start frame)
Image time (0 at start frame)
Current plane array index
Current plane index
Num of channels in current plane
Composite Project X resolution
Composite Project Y resolution
Composite Project pixel aspect ratio
Composite Project raster depth
Composite Project black point
Composite Project white point