Hey Dr. Sassi wow i am blown away by your commitment to helping me with this problem! You are an absolute legend! Thank you so much for all the hours you put into this!

I saw your first answer on Friday and was about to thank you and ask you for suggestions on how to combine both partial solves properly (after some more tries today) and that im thankful for you sharing all the infos because it made me understand what i should have kept a very close eye on at the shoot (like having enough parallax or floor in the first half) but i didnt expect you to take your Saturday to solve that beast of a track from a simple mp4!

Im amazed! Thank you!!

I was at the shoot but i didnt receive any infos on the cam so im not sure. I made sure to stress that they shouldnt zoom though, so the focal length should be constant. I also mentioned that i need as much resolution as i they can capture.

Thanks for the fast answer!

Since the original footage is RED Raw, the conversion shouldnt have harmed it too much but i also did one without converting it into linear space (by going from RED wide gamut to Rec709 2.4). I will do another test with a different file format since i have noticed some strange patterns and colors appearing when i display the footage in Tracker View instead of original.

Camera Model and lens data are sadly unknown to me and i have no tracking plate either. No post cropping but i tried unwarping the lens distortion while troubleshooting but that didnt affect the track or result.

The floor is mostly obscured in the beginning so using it wont work.

I didnt mask out the reflections or the skater, instead i selected and removed those unwanted tracks after autotracking.
I didnt try merging the data into one camera move because i couldnt figure out how to do it on the fly.

I have updated the dropbox with requested mp4 ("TrackingShot"). I'll have to delete it soon though.

Hi,

I'm a senior motion designer working on tracking a 518-frame shot for compositing using Cinema 4D's Motion Tracking toolset, but I've encountered an issue. The camera solve starts at frame 218 instead of at frame 0. Frames 0 to 217 lack camera movement and tracking points, despite providing sufficient manual tracks and ensuring the frame range covers the entire clip.

I'm using Cinema 4D 2025.0.2 on macOS Sonoma 14.6.1 with a MacBook Pro M2 Max (96 GB RAM). The footage is a 1920x1080 EXR sequence at 25 fps in ACEScg color space. It's a sideways trucking shot of a subject skateboarding along a building. Its a complicated shot (because of reflections) but im confident that i managed to provide solvable data.

Attempts to resolve the issue include:

• Retracking with different methods, such as using 8-bit Rec.709 footage instead of linear ACES, Increasing contrast for better auto-tracking.
• Trying a fully automatic solve without manual adjustments.
• Lowering track count, raising track count.

There were no errors during tracking or solving, and I didn't adjust any settings that could shorten the solve. The Focal Length is unknown but Constant.

Troubleshooting by solving specific frame ranges:

• Frames 0–200: Correct solve until frame 76, then stops.
• Frames 0–300: Correct solve until frame 137, then stops.
• Frames 138–300: Results start at frame 218 (note that this is the same starting frame as in the full solve).

This suggests an issue occurring between frames 138 and 218. But the incomplete solve in the 0-200 test speaks against that.

This is the first time I've encountered such a problem. Is this a known issue or a potential bug? Any suggestions or workarounds? I need to solve this urgently.

Screenshots: https://www.dropbox.com/scl/fo/rh4wg1hf0i8e2ogpv9v4n/AMz9gWYRK39KmPBJBME8LKc?rlkey=g410wfyt05jxrhphi1vwdkj47&st=4rnk5k34&dl=0

Thank you for your help!