Hi Steve, It will certainly take extra memory either way. If you do implement your own cache I think you can use the new STLAllocator class which uses the same memory pool as the std cache (although I've just started to use the STLAllocator class and haven't tested yet to see how well it uses the memory pool.)
-jonathan On Apr 16, 2012, at 11:31 AM, Steve3D wrote: > Jonathan, > > I am in nearly that exact situation, actually. I had originally intended to > output separate xxx.L and xxx.R channels and then Join them later, but had > discarded that as less efficient. I shall revisit that decision, and think > more about internal caching. It does seem, however, that regardless of > whether the channel frames are cached inside my own node, or inside Nuke, the > memory still must be allocated and used. > > Steve > _______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev _______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
