# Camera analysis crashing **URL:** \ **Category:** Flame Questions\ **Tags:** camera-analysis\ **Created:** [June 6, 2025, 5:16pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994 "2025-06-06T17:16:24Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [June 6, 2025, 5:16pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/1 "2025-06-06T17:16:24Z")
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? ---
**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\ **Post date:** [June 6, 2025, 5:17pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/2 "2025-06-06T17:17:05Z")
outsource it. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [June 6, 2025, 5:17pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/3 "2025-06-06T17:17:34Z")
That would be the sensible option ---
**Author:** ![cristhiancordoba](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@cristhiancordoba](https://forum.logik.tv/u/cristhiancordoba)\ **Post date:** [June 6, 2025, 5:31pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/4 "2025-06-06T17:31:54Z")
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… ---
**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\ **Post date:** [June 6, 2025, 7:19pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/5 "2025-06-06T19:19:29Z")
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. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [June 6, 2025, 7:31pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/6 "2025-06-06T19:31:45Z")
Different place each time ---
**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\ **Post date:** [June 6, 2025, 7:33pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/7 "2025-06-06T19:33:56Z")
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.” ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [June 6, 2025, 8:22pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/8 "2025-06-06T20:22:17Z")
I’ll give that a go on monday ---
**Author:** ![kily](https://avatars.discourse-cdn.com/v4/letter/k/a88e4f/32.png) [@kily](https://forum.logik.tv/u/kily)\ **Post date:** [June 6, 2025, 9:35pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/9 "2025-06-06T21:35:33Z")
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? ---
**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\ **Post date:** [June 7, 2025, 1:23am UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/10 "2025-06-07T01:23:29Z")
What is your hardware? ---
**Author:** ![Ryland](https://avatars.discourse-cdn.com/v4/letter/r/ba8739/32.png) [@Ryland](https://forum.logik.tv/u/Ryland)\ **Post date:** [June 7, 2025, 3:15pm UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/11 "2025-06-07T15:15:36Z")
Use the mono analyzer instead. Way faster and almost always better results. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [June 9, 2025, 8:04am UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/12 "2025-06-09T08:04:45Z")
128G ram, RTX 6000 ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [June 9, 2025, 8:09am UTC](https://forum.logik.tv/t/camera-analysis-crashing/12994/13 "2025-06-09T08:09:31Z")
Resource manager doesn’t show anything untoward