steve, thanks for the suggestion. I guess I am giving up on this but I would like to summarize here some useful information for other newbies like me :) but for the gurus, please do point out my mistakes though.
Viewer Cache (or Disk Cache), VC is practically a separate component from the API. According to the documentation, there is only one situation that your op's output won't be cached by the VC and it is when the engine() call sequence is triggered by "asapUpdate()" and NOT regular outputContext() changes. So plug-ins which serve pixels from external rendering server might use asapUpdate() to trigger the engine() call sequence and the image data will not be cached by Viewer cache. (I don't have actual experience building one though). Other useful calls related to Row Cache: Op::slowness(), helps Nuke to decide how to cache your stuff Op::append() 1. modifies Nuke's proposed Hash, e.g. if your plug-in relies on frame#, then you might to append the outputContext().frame() on it etc. (from Doc) 2. using append(__DATE__), append(__TIME__) practically rejects any chance to use cached data (from older posts) okay, I wish there would be similar call like asapUpdate() but for daily purpose. :)
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
