I always create projects with Cache & Renders as Uncompressed/RAW. I’m beginning to rethink this… Flame archives are always huge, then I compress them. But tonight I noticed something. When I look at my media (the grade folder, for instance) on the desktop, it’s 22GB. When I look at that same folde…

Hi, There are a few points that might help you out. Firstly, my advice is generally to work with the intermediates that match the resolution. Working at a much higher resolution when not needed only eats at your storage. For example if you have 10-bit ProRes, there is no reason to cache it as …

If you have the original media local, there’s an archiving option that excludes caches and renders that could save you a bunch of space. You’d have to archive the original media along with your flame project, but that could probably go on the same LTO, no?

I find that’s the best option for me too. Just archive with cache off and you will see that the flame archive size will drop dramatically.

I’m not sure if it’s still prevalent with the new software, but if you delete hard commits, it used to clear up space. The hard commits added an additional render/hard caching of the elements/data stored inside the segments. ie just take the hard commits of your timeline and it should bring the comp…

Grant, this detailed explanation was a huge help and I very much appreciate you taking the time to write it out this way. I try to keep updating my workflow and this helps a lot! I’m concerned about creating a project too small for my source files, but it sounds like I don’t need to be? What is you…

[image] La_Flame: On the other hand, Batch renders are very different to TimelineFX renders. The rendered Batch clips have no connection to their Batch setup or the originating source media. You cannot un-link, un-render or flush processed Batch clip. It is considered as generated media and noth…

Hi Renee, The meaning of Preferred format is that Flame will first try use this format as your intermediates for source caching, renders, etc. If you are caching/rendering to a resolution greater then the preferred format, Flame will switch to the alternatives which can (EXR/RAW/etc) My rule of …

If all the media is cached the same and it works for you than thats great! The real piece of mind for me, is if the source media is lost for whatever reason, you have a cached version in Flame and you can carry on working. Thanks Grant

archive size can also be greatly reduced if u manage your clips once built. ie consolidating handles for each clip. another huge space hog when archiving is your batch iterations. if you throw away all your old iterations and only keep the latest this can bring down the archive size dramatically

This also seems to be another vote for not caching the media for working, at least for my workflow (home, one machine, Mac Pro). I don’t cache for my jobs but I would cache the media on Archive so it was all contained in the Flame archive. I see now that was a huge waste of time (waiting for the cac…

if you absolutely need to send an archive and depending on how complex it all is , just hard commit everything so it doesn’t have handles, unlink it all and archive with unlinked media, this will lower it down to sometime manageable and sendable, send the original files that are small in size and re…

Flame project and HUGE ARCHIVES

Flame Flame Questions

randy Split this topic September 17, 2020, 5:05pm 7

A post was split to a new topic: Reading Flame archives in older versions

Topic		Replies	Views
Archive not respecting options Flame Questions archive	18	961	May 24, 2024
Archive - with no pics is 2TB Flame Questions archive	31	1381	October 25, 2022
Why are Flame archives still so ridulously bloated? Flame Questions	55	2850	February 18, 2022
Workflow discussion: Best practices for reducing massive Flame archive sizes Flame Questions archive , workflow	51	711	March 13, 2026
ARCHIVE TRICKS (For Massive Archives!) Flame Questions archive	17	1341	December 20, 2024

Flame project and HUGE ARCHIVES

Related topics