# Camera Analysis fails badly

**URL:** <https://forum.logik.tv/t/camera-analysis-fails-badly/10533>\
**Category:** Flame Questions\
**Tags:** 3d-tracking\
**Created:** [April 27, 2024, 1:35am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533 "2024-04-27T01:35:08Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [April 27, 2024, 1:35am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/1 "2024-04-27T01:35:08Z")

</div>

Hi,

I’m going to be inserting some graphic elements into various shots. I shot a test with my phone and tried camera analysis on it but for the life of me cannot get a good result. Why is Flame so bad at this shot?

[https://f.io/mkTq\_ss6](https://f.io/mkTq_ss6)

---

<div class="post-metadata">

**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:** [April 27, 2024, 2:06am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/2 "2024-04-27T02:06:27Z")

</div>

Equally, why is Syntheyes astonishingly fast and accurate?

---

<div class="post-metadata">

**Author:** ![ALan](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@ALan](https://forum.logik.tv/u/ALan)\
**Post date:** [April 27, 2024, 3:41am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/3 "2024-04-27T03:41:51Z")

</div>

We gave up on 3d tracking in flame a very long time ago.

---

<div class="post-metadata">

**Author:** ![stu](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@stu](https://forum.logik.tv/u/stu)\
**Post date:** [April 27, 2024, 4:45am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/4 "2024-04-27T04:45:10Z")

</div>

@johnag Yes it’s tricky, I had a look while I was waiting for Rocky 9.3 to download.

I couldn’t get Camera Analysis to work either, maybe because the footage is compressed so the features are aliasing.

I got the best results half rezzing and using the old Mono Analyzer, got the error rate to 0.81 so it’s not perfect. Probably if I had undistorted the plate it would have been better.

---

<div class="post-metadata">

**Author:** ![Ryland](https://avatars.discourse-cdn.com/v4/letter/r/ba8739/32.png) [@Ryland](https://forum.logik.tv/u/Ryland)\
**Post date:** [April 27, 2024, 6:56am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/5 "2024-04-27T06:56:22Z")

</div>

There isn’t any reason to use camera analysis on a shot like this. As mentioned above mono analyzer is more appropriately suited to this shot.

If this is the level of difficulty you’re expecting for the shots you need to track then there is no reason to leave Flame. Everything should be easily tracked with the mono analyzer.

---

<div class="post-metadata">

**Author:** ![cristhiancordoba](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@cristhiancordoba](https://forum.logik.tv/u/cristhiancordoba)\
**Post date:** [April 27, 2024, 4:42pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/6 "2024-04-27T16:42:45Z")

</div>

I dont know… I use a lot the new camera analysis tracker and when i say a lot i mean a lot. Almost left pftrack…you just need to know how to use properly and in which cases will not work and better go with contrasted points camera tracker.

I’m one of those who find the new camera analysis reallly useful and im really happy with it, but you know…at the end not everyone is pleased with same things.

---

<div class="post-metadata">

**Author:** ![Ben](https://avatars.discourse-cdn.com/v4/letter/b/df788c/32.png) [@Ben](https://forum.logik.tv/u/Ben)\
**Post date:** [April 27, 2024, 6:30pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/7 "2024-04-27T18:30:30Z")

</div>

I use it often but find it so hit and miss for reasons i just cant phathom

---

<div class="post-metadata">

**Author:** ![Ryland](https://avatars.discourse-cdn.com/v4/letter/r/ba8739/32.png) [@Ryland](https://forum.logik.tv/u/Ryland)\
**Post date:** [April 28, 2024, 4:21am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/8 "2024-04-28T04:21:00Z")

</div>

Yeah this. It’s just a little too flaky.

Don’t get me wrong, I definitely think the camera analysis has its place but it’s more niche. I used to pull it out fairly often but as time has gone on I just find there are very few shots I can’t solve faster with the mono analyzer.

---

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [April 29, 2024, 1:00am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/9 "2024-04-29T01:00:41Z")

</div>

Thanks guys.

I fired up Syntheyes for the first time and in a few minutes got a great result. I will also re-visit the mono analyser (havent touch in in years)

---

<div class="post-metadata">

**Author:** ![BrittCiampa](https://avatars.discourse-cdn.com/v4/letter/b/ec9cab/32.png) [@BrittCiampa](https://forum.logik.tv/u/BrittCiampa)\
**Post date:** [April 29, 2024, 1:17am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/10 "2024-04-29T01:17:54Z")

</div>

Syntheyes! It’s the best!

---

<div class="post-metadata">

**Author:** ![TimC](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/timc/32/11881_2.png) [@TimC](https://forum.logik.tv/u/TimC)\
**Post date:** [April 29, 2024, 10:56am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/11 "2024-04-29T10:56:01Z")

</div>

FWIW i do shots like this all the time with Mono Analyzer. still works great for simple stuff like this. surprised to hear the new camera tracker cannot hack this!

---

<div class="post-metadata">

**Author:** ![johnt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnt/32/14040_2.png) [@johnt](https://forum.logik.tv/u/johnt)\
**Post date:** [April 29, 2024, 12:24pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/12 "2024-04-29T12:24:09Z")

</div>

![image](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/9/914756123f8e92c77d1af880b170c0d6dd100515.png)  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/5/5810a77a7b185863aaae18b2955f38967d2562a9.jpeg)  
Just for the challenge, I had a go - it’s not perfect but I got it to work - obviously, the scale on the bottle is wrong unless you’re WC Fields.

---

<div class="post-metadata">

**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\
**Post date:** [April 29, 2024, 1:27pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/13 "2024-04-29T13:27:36Z")

</div>

Treating the source image before the track works wonders sometimes. I go at it with Lumps for frequency seperation, Seperate for individual channels and color correction…

---

<div class="post-metadata">

**Author:** ![luke](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/luke/32/8705_2.png) [@luke](https://forum.logik.tv/u/luke)\
**Post date:** [April 29, 2024, 2:22pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/14 "2024-04-29T14:22:07Z")

</div>

It’s probably having trouble because there’s nothing to track in the top left corner. If you have time for a reshoot then put a tracker there and see if your steadicam operator can get something similar. If the production can’t make a reshoot happen try grading the upper left to see if you can bring out any detail. It’s either that and/or maybe image stabilization on the iphone. Also just bump your # of trackers way up and delete the obvious wrong ones.

---

<div class="post-metadata">

**Author:** ![MLandon](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@MLandon](https://forum.logik.tv/u/MLandon)\
**Post date:** [April 30, 2024, 6:07pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/15 "2024-04-30T18:07:55Z")

</div>

Hey John,  
I just loaded up your shot, denoised it, and ran it through Mocha’s new camera analyzer (baby Syntheyes) and got a great result quickly. I made some nulls and exported it as an FBX and I can now do whatever I want on the image. I know you said you used “big” Syntheyes to get your track, but in case someone (like me) doesn’t have it, Mocha 2024 is a nice substitute.

---

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [May 1, 2024, 3:30am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/16 "2024-05-01T03:30:14Z")

</div>

Thanks. I’ll take a look at mocha too

---

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [May 1, 2024, 4:09am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/17 "2024-05-01T04:09:36Z")

</div>

Hey @MLandon

I didn’t realise that Mocha pro is now using the syntheyes engine. Works a treat and you saved me $50 month.

---

<div class="post-metadata">

**Author:** ![Ton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ton/32/5542_2.png) [@Ton](https://forum.logik.tv/u/Ton)\
**Post date:** [May 1, 2024, 7:36am UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/18 "2024-05-01T07:36:50Z")

</div>

In my experience the camera analysis doesn’t do a great job at ‘easy, straighforward’ shots that should be a breeze to track… dunno why… however… it quite often does track the weirdest shots which my cg guys couldn’t track if their lives depended on it in synth/ pftrack… like an open sea with 0 static elements recently… I usually get one or the other to work with a shot.

---

<div class="post-metadata">

**Author:** ![RT\_FA](https://avatars.discourse-cdn.com/v4/letter/r/65b543/32.png) [@RT\_FA](https://forum.logik.tv/u/RT_FA)\
**Post date:** [May 9, 2024, 9:00pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/19 "2024-05-09T21:00:26Z")

</div>

Glad its not just me…i finally got around to messing with the camera analysis six month(ish) ago. I grabbed a bunch of random footage, most shots thinking they would be easy tracks just to ease into it…and it failed on most all of them. I watched and rewatched the tutorials (which if you look close some of those have issues) I did the track(s) over and over and still couldn’t get a decent result. I then tracked the same shots with the Analyzer and it nailed them. But like others have said, i did try one shot that i would consider dicey and the Analysis crushed it. So end result is i’m kind of indifferent towards it…which is a shame.

---

<div class="post-metadata">

**Author:** ![maxim344](https://avatars.discourse-cdn.com/v4/letter/m/67e7ee/32.png) [@maxim344](https://forum.logik.tv/u/maxim344)\
**Post date:** [May 11, 2024, 6:09pm UTC](https://forum.logik.tv/t/camera-analysis-fails-badly/10533/20 "2024-05-11T18:09:47Z")

</div>

If the Analyzer came to the rescue on some tricky shots, that’s a win in my book
