Thanks for the replies. Moving the set to validate and adding time to the
hash worked like a charm.
Cheers,
Eric
On Mon, Mar 30, 2015 at 12:08 AM, Ivan Busquets <[email protected]>
wrote:
> If you can resolve all time samples into keyframes at the time you read
> from file, and set all keyframes at once on your knobs, that may be the
> most efficient way to go about this.
>
> Otherwise, I think you'd be better off doing that work inside _validate()
> instead of knobs(). To ensure validate gets called each time you change
> frames, you can add the current frame to the node's hash by implementing
> the hash() method in your op.
>
> Hope that helps.
>
> Cheers,
> Ivan
> On Mar 29, 2015 9:34 PM, "Eric Larsen" <[email protected]>
> wrote:
>
>> I'm writing a plugin derived from CameraOp to read our internal camera
>> files and set the data for a nuke CameraOp. I've been setting the knobs
>> for the camera data from the knobs() callback method to update the data
>> when the frame changes but this is causing the node to continually update
>> when if the camera is connected to a scanline render node.
>>
>> Is the knobs() callback the correct place to update knobs that affect the
>> cacheId calculation of the node or will this cause a loop? What is the
>> correct method to be notified when time changes and update the knobs for a
>> node that won't cause and endless update cycle?
>>
>>
>> Thanks,
>>
>> Eric
>>
>> _______________________________________________
>> Nuke-dev mailing list
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>>
>>
> _______________________________________________
> Nuke-dev mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>
>
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
