Blender Git Loki
Git Commits -> Revision 6b39a47
Revision 6b39a47 by Dalai Felinto (tile) January 31, 2012, 19:57 (GMT) |
Normalize Node - Tile The implementation is simple. Fancy alternatives to gather the minimum and maximum through recursive loop in the tiles proved inefficient (Jeroen Bakker's tests) I'm also using the generic NodeTwoFloats to store the temporary values calculated in the loop. And different from Blender trunk I'm not checking to see if the value is between the accepted Z range (e.g. (*val <= BLENDER_ZMAX)). I can't see why that would be necessary. To avoid overflow? If so this be handled (aka clamped) outside the nodes in a generic way. Credits to Jeroen Bakker for the solution in using mutex (copy pasted from his ToneMap code) and review |
Commit Details:
Full Hash: 6b39a476cbe83febfe67daa31be6fade83194c7a
SVN Revision: 43800
Parent Commit: ed4ea07
Lines Changed: +262, -4
4 Added Paths:
/source/blender/compositor/nodes/COM_NormalizeNode.cpp (+36, -0) (View)
/source/blender/compositor/nodes/COM_NormalizeNode.h (+37, -0) (View)
/source/blender/compositor/operations/COM_NormalizeOperation.cpp (+108, -0) (View)
/source/blender/compositor/operations/COM_NormalizeOperation.h (+69, -0) (View)
/source/blender/compositor/nodes/COM_NormalizeNode.h (+37, -0) (View)
/source/blender/compositor/operations/COM_NormalizeOperation.cpp (+108, -0) (View)
/source/blender/compositor/operations/COM_NormalizeOperation.h (+69, -0) (View)