Dear Colleagues

I'm trying to update a Nuke plugin which used to work up until version 6.2v3, 
but which fails from 6.3v1 onwards under Linux.

The CameraOp node has been sub-classed to provide camera animation from a 
proprietary file format, using custom interpolation for fractional frames.

It seems that the only place to implement the functionality is in the 
_validate() function, where the file is read, and data controlling both camera 
internal and transform parameters is written to the camera knobs with 
set_values(), and also directly to the CameraOp itself.

If you don't write directly to the CameraOp as well, then the observed 
parameters lag behind the frame number. I assume this is due to Nuke's calling 
order.

But since version 6.3v1, the node causes Nuke to hang whilst gobbling up all 
available system memory.

Moving the knob-setting calls to updateUI() makes everything work fine, but 
ONLY if the node control panel has been opened. The knob values are potentially 
used by expressions on other nodes.

So the question remains:
Is it legal/advisable/verboten to call knob->set_values() from within 
_validate(), and if not, how else could the required functionality be achieved?

It would be good if The Foundry could give a definitive response on this point.

Any feedback would be much appreciated.
Many thanks
Dave.
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev

Reply via email to