Nobody can tell you anything without any info about your footage and things like system info, AE version and so on. That said, 90% of the time this simply happens, because the footage is not suitable for 3D tracking. People always expect miracles of this stuff...
Solving the camera depends on the shot. Many shots will not solve because there is not enough fixed geometry in the shot to be used to extrapolate date. Not too long ago someone sent me a shot of a jet ski rider surfing that was taken from another jet ski that they could not camera track. The only fixed geometry in the entire shot was the jet ski, but that was moving so there is nothing to analyze. The shot is always a fail and you have to use other techniques to do a composite.
If you are going to do camera tracking you have to plan hour shot in advance and make sure you set things up so you get enough information in the frame that you can use to solve for the camera move.
Show is the shot and we can tell you if it is going to work. The more experience you gain the better you will be at solving these kinds of problems.
This is the clip
I did not add anything else to it, only camera tracker.
It does this with every clip that "detailed analysis" is checked
if you need more information, just ask.
That looks like screen capture from a game or a render from a 3D app. There is also almost nothing to track in the first few seconds when the camera pulls back from the thing on the wall. Just a little heads up on Screen cap, game footage and 3D renders. They are difficult if not impossible to camera track. If you can get anything from the track without enabling detailed analysis that would be a miracle from that footage.
The crash could also be caused because the footage is an MP4. Highly compressed mpeg footage doesn't have every frame so the CPU has to decode the in-between frames and make them up by guessing where the pixels move. All of that work, and especially if there are any errors in the file could easily crash AE. You may have better luck adding the MP4 to the Adobe Media Encoder and rendering an image sequence and then use that footage from a track.
Even if you solve the crashing problem you may not be able to get a usable track from that footage because from a little before here:
there's not much to track.
1 person found this helpful
What Rick said. Not enough details in the initial state, so the tracker doesn't even know where to begin. that aside, captured games footage tends to be spatially inconsistent since in games 90% is cheap hacks that allow illogical object placment and weird camera moves, so it might not solve at all even if the shot was visually better.
1 person found this helpful
Looks like this would be a much better candidate for a planer tracker like Mocha. Start at the end, select the screen and track backwards - at least if you are trying to solve for the screen. If not, it should give you enough data to fake the rest.