Caching optimization.

1. I have cached the shot because it is heavy. When I make a change, it starts caching again, which is OK. But when I UNDO, the program starts caching the already cached file again. (Other programs like AE can revert to the original cached file)

2. When I make a duplicate timeline for alternate changes, the program starts caching the complete everything again. When you have a full feature film, it takes 1 TB and takes hours to render.

+1
Final Cut Pro X is also very optimised about "render"

+1

Caching seems to be not very intelligent, efficient, or kind about disk space.

+1

Caching seems to be not very intelligent, efficient, or kind about disk space.

Yes, I want to point that out. I hope the creators read it. As well as my other observations. I'm not trying to criticize, I'm trying to improve a program I love, same as many others.

I like the first idea.

But I see a potential problem with the second. I would favor the following to be implemented.

viewtopic.php?f=33&t=124820

As each timeline gets it's own Cache folder, item two on this list could be implemented only with a Copy operation, so it would still take up space.