Hi, I think you're confusing two different caching mechanisms here.
The local file cache is designed to make loading of your source files faster. Essentially this just makes a local copy of the file you're reading. This has some overhead the first time you use it (the progress bar you see when you hit update all), but from then on, whenever you work on that script it will always load from the local file cache, hence avoiding network traffic, resulting in faster file loads.
The playback caching is actually caching the output from the Viewer. This is different from the local file cache, since you may have ops downstream of your read node which affect the output. When you play back the first time, the viewer output (ie the output image resulting from every op in your tree) is cached to disk every frame. The second time you play back, the viewer output is read from disk, avoiding potentially expensive re-calculation of the image every frame. This cache will be used until you change something in your tree, in which case the output will need to be recalculated and re-cached.
Hope that makes things a little clearer, Peter. On 10/05/2012 14:57, chrissowa wrote:
but why is the viewer caching a second time on disk? thats a strange behaviour: 1. copy files from network to disk (Cache->Update All) 2. playing back once (disk to disk transfer?) 3. playback is okay _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
