I have a 476 fr shot, 4K that keeps crashing my flame whilst camera tracking. I have just tracked 20 shots of various lengths, but I’ve now had 5 crashes with this shot. It’s ACES, but have tried converting to REC and ACEScc, but no change. The shot is mainly red with red fluro lights.
Any suggestion’s?
outsource it.
That would be the sensible option
Two things come to my mind:
1 - Cache motion vectors prior doing the cam analysis then run the analysis.
2 - Prerender motion vectors using motion vectors node in batch then use that prerender for cam track…
One thing comes to mind. There’s a corrupted frame. Does it always crash in the same place? Jog through and look for a checkerboard.
Different place each time
Every once in a while I have a clip that is uncooperative. I run it through the desktop colour corrector with no changes and it fixes whatever ailed it. I use the CC because it renders fastest. I think in the early days we called it “stonifying.”
I’ll give that a go on monday
I guess it could be a typical vram problem. Camera tracking is resolution independent. I don’t know much about flame’s motion vector camera tracking, because I use pftrack all time. Couldn’t the analysis be done in 2K and then copy the camera setup analized to an action with the original 4K footage?
What is your hardware?
Use the mono analyzer instead. Way faster and almost always better results.