Can someone shine some light on what exactly is saved in the framestore/ S+W partition?
as we adopted a unmanged workflow, we dont generate any “important” or unique media “inside” of flame.
We only use the local framestores for 1 thing → playback caching! the actual data is on LucidLink.
Ok, so far so good, all works fine but now I want to take this one step further and have a centralized project server, So thats great, its just a headless flame running in a LXD container or a VM , i get that, easy peasy lemon squeezy, its great i can have all my project data there ,snapshot it, great ill that that to go please.
But then, there is this pesky stone/framestore thing that also suddenly has to become centralised as well, so good bye local cache, but I dont care about the data on there.
And I tried it if I open a project from flameA on flameB and they both point to a non-existent shared location , like flameA cannot access flameBs local framestore - everything turns into checkerboards EVEN THOUGH there is nothing in that stone, flame just really WANTS to have it.
What is it looking for, is that some data that I can somehow store somewhere else? is there a way to use LOCAL stones with a shared project server?
HA I NOW KNOW what its looking for, those pesky .MIO clips that get created on your stone!! so its never just pointing to a file from the flame project to the location on the NAS its always just pointint into the framestore which points to those .mio files which points to location on the nas
the other stuff just seems to be preview files
WHY are they there, why do we need them, can we … get rid of them?
I know I could “Just” get 25Gbit infrastructure just for a stone that I dont really need or want…
I just want to cache to a cache directory thats local to each machine … like resole, i dont want shared cache data
Also… what happens if I set my cache to prores422HQ , EXR DWAB (I think there was a way to do that?) and just have my framestore be on the LucidLink partition, is that like EXTREMELY stupid?
Honestly contemplating just pinning the framestore location on each flame and then having one framestore partition inside the project folder?
I dont want any wire , i dont want to have any of that legacy stuff, i just want flame to behave like a tool from 2024