Which is the point of clip history I guess! I totally understand what you’re saying @GPM. I think for me at least, ever since it stopped defaulting to being on (a long, long time ago), it’s one of those settings I keep forgetting to turn on in the prefs!
Remember that! It wouldn’t switch over the autosave projects for those 3 that you get when Flame crashes when you switched using that way!
1 Like
My Batch Iterations…
v001
v002
v003
v004
v005
v006
v007
v008
v009
v010
v011
v012
v014
v015
v016
…
same
1 Like
HAHA. I do the same on iterations as well although when I reach 13 I just iterate again.
We nailed a v022 shot with insane attention to detail – we call it ‘pelo em ovo’ here OBS: Pelo em ovo’ is a Brazilian expression denoting exceptional refinement and precision, particularly in cinematic contexts where technical and artistic excellence are highlighted
1 Like
Before I render a big batch, even if I’ve saved / iterated, I always quit Flame then restart, I’ve been bitten too many times with a crash that wipes out my last save.
5 Likes
I always save and clean the desktop before quiting flame. Something rots in my soul when I see someone exiting from flame with the desktop full of clips and timelines.
About switch projects, I never had a problem with it, but I remember a studio where they were completely forbidden switching projects. When I saw that flame changed the actual scheme of switching projects, (already commented, now it really does a discrete quit and start), I thought that there must be something problematic about it.
4 Likes
Switching projects can be problematic if your projects have different group privileges, and I sort of remember that some python hook initialization could cause problems.
Personally I’m guilty of just exiting flame, and starting flame with where I left off.
Sort of like browser windows/tabs persisting across restarts.
I archive frequently and usually automatically.
YMMV
and I only have $0.02 - I had to forfeit the other $0.98
2 Likes
Yup, always exit Flame when switching Projects.
3 Likes
I thought that was just my machine. It’s bonkers.
I’ve actually been doing this a little bit recently and working on the desktop. I just couldn’t arsed to work it out in batch.
On my Mac, Flame itself takes care of quitting and having me restart flame when I switch projects whether I like it or not, so I guess it’s superstitious about that too.
1 Like
I genuinely feel like Tracker 2 is just worse at his job than Tracker 1. Every time he’s just bouncing around like an idiot.
5 Likes
Maybe you need to disable the pre tracking option, tighten up the analysis and search boxes and don’t allow the search pattern to update between frames.
I can never remember the names of the tools, my brain just pushes the buttons.
Alternately you can take tracker 2 to the bus station, hand it two bucks, and tell it to go make a name for itself somewhere… anywhere but here…
I always track them separately, tracker 2 always screws up when tracking both together.
2 Likes
Tracker 2 is the second child of the family, neglected and crazy.
2 Likes
And changing the colourspace button from Auto to Other is a must for me,
If you move your shot into a log colour space (eg ACEScct not ACEScg) then Tracker 2 is approximately one million times more reliable, both at sticking to its original target, and continuing when it’s moved to a new ref halfway though a shot.
But if you are already in a log space, then yeah it’s just weird.
You have to hit the snap button 10 times to make Tracker 2 work. I’m sure it was in Flame Learning Channel.
2 Likes
Good stuff to know. I’m curious the kind of uses cases that come up often, where Gmask Tracer isn’t better than the traditional 2 point track?
I think I’ve entered the old tracker like twice in the last year…
(I get the occasional shot where it’s just better — but are people using 2 point regularly as a first choice?)
3 Likes