Lev Kolobov wrote:
I'm actually surprised too, because you can drag select area in viewer and
will give you an average instantly. How does it work? Why the average tool
is so complicated to do.
The way I ended up doing it involved some work with thread locking and
switching between single- and multi-threaded engine calls, but it was still
fairly basic to implement. I'm sure The Foundry have their reasons for not
adding one before now though, and I'd be curious to hear them. It could
always be something as simple as no one really asking for it, though I
suspect that's not the case.
Oliver Jezequel wrote:
doesn't it what the curveTool node is doing already ??? have you tried
that ?
it return you the average of your ROI in the pict.
As far as my plugin goes, I believe it will output the same values as the
CurveTool (thanks for reminding me though; I'll test that when I get in this
morning). However, instead of outputting them to a knob, they end up in the
image channels. The main reason I wrote it is to avoid having to execute a
node every time I wanted the values recalculated. We were doing some tests
of 2D HDR lighting of facial capture scans and needed a way to dynamically
average the different HDR lookup samples to be multiplied against other
color data.
-Nathan
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
