The Foundry Camera Tracker 1.0 V
Danielyan Garay
CameraTracker (NukeX and Nuke Studio only) is designed to provide an integrated camera tracking or matchmoving tool, allowing you to create a virtual camera whose movement matches that of your original camera. Tracking camera movement in a 2D footage enables you to add virtual 3D objects to your 2D footage.
Sets the size of the camera imaging sensor. Specify the units you want to use by selecting either millimeters or inches in the Units dropdown. The units should match the units used for the Length.
Click to display a frame range dialog, allowing you to retrack part of the sequence, such as when you have extended the frame range or used some of the Settings tab Tracking refinement controls.
Click to begin calculating the solve using the controls specified in the Settings tab. Solve calculates the camera path and projection creating a 3D point for each 2D feature track within a minimum projection error, including auto-tracks, User Tracks, and tracks created from imported Trackers.
Displays the RMS (root mean square) error of your solve, in pixels. As a general rule of thumb, if your solve reports an RMS projection rate higher than 1.0 pixel, you may want to consider fine-tuning your solve or tracking data.
Sets the threshold for smooth track generation. Adjusting this value can be useful in preventing poor tracks in complex sequences. Increase the smoothness value to remove tracks that glitch over time.
Controls the separation between keyframes. Use a high separation to spread keyframes out in long sequences with small camera movements. Use a low separation to generate more keyframes for fast camera moves.
When Set reference frame is enabled, specifies the first frame to use as a keyframe in the solve. This should be a frame where there is a large number of tracks distributed over the image with a good variation in depth.
When Undistort Input is enabled, sets the filtering algorithm to used. This allows you to avoid problems with image quality, particularly in high contrast areas of the frame (where highly aliased, or jaggy, edges may appear if pixels are not filtered and retain their original values).
Equivalent value for the a (r^3) control on LensDistortion tab of the Card node. Defines a cubic term that affects the radial distortion of the texture applied to the card, and the edges of the card.
Equivalent value for the b (r^2) control on LensDistortion tab of the Card node. Defines a square term that affects the radial distortion of the texture applied to the card, and the edges of the card.
Equivalent value for the c (r^1) control on LensDistortion tab of the Card node. Defines a linear term that affects the radial distortion of the texture applied to the card, and the edges of the card.
Can't find what you're looking for? Use our feedback widget on the right to request more information.
You must accept cookies from learn.foundry.com and disable any ad-blockers to provide feedback.
1) Tracking the footage was tough as most tracks were in the red until I fiddled with the hue saturation and levels to make it easier which seems to have somehow helped get great green quality tracking markers.
I ad to stop using the Foundry Camera Tracker when I switched from my Mac Pro to my HP Z820. Whenever I would hit solve, AE would hang. I spent 2 weeks troubleshooting this with the Foundry with no resolution. Luckily the AE Camertracker does the job for me.
I also have had no luck from the foundry. But its just odd that there is nothing but praise for the plugin everywhere and the footage I am tracking is very very simple (tripod locked off and High def) no trouble with getting a solve just with the software not recognizing I have gotten one!
I kept getting the same error and i finally got Cameratracker to solve it by trimming my layer that i was tracking. I had a fade on my quicktime in the beginning and i think the lack of information when it went completely black was throwing it off. After that it solved fine and gave me my camera
After I create a 3D Camera Tracker Solve I get no bullseyes target, but I can see all the tracker points. When I right click to create the "Create Text and Camera" I also get nothing no Text or Text field. I've been following several tutorials to the "T" and I still get nothing. What's strange is this was working fine last month when I was using the Creative Cloud trail free for 30 days.
On further trail and error I noticed something very, very weird. I noticed after I made the "Text and Camera" there was a red pixel blinking within the triangulation of the 3 points. I zoomed in all the way to 1600% into the red blinking pixel and noticed it was the Text field's Cursor. When I inspect the Text layer's "Scale" it stated that the Text is already sized at 3000. WTF? Even zoomed in at 1600% it's only the size of my pinky finger nail. If I enter a ridiculous Size amount such as 1,000,000 I can finally see it on the screen and to top it off the 3D orientation is totally off from the plane chosen from the triangulation of the 3 points. The orientation is also totally wrong in a different plane then the 3 tracking points.
Please help I can't follow any tutorials because something is terrible wrong. This is way beyond me. Everytime I watch any tutorials I'm stuck because of this. I'm going to attach some photos to better illustrate these problems.
Ps. I also noticed when zoomed in at 1600% I could finally see the Bullseye which made me realize the connection. so again like the Text Field issue if I max out the Target size to 10000% I can finally see the bullseye target. Even sized at 10000% the target displays only at approx. 2" This is totally wierd.
Your footage is crap for any sort of 3D tracking, that's the simple harsh truth here, at least based on the pic you provided. Sorry to say so, this is loco and cannot work the way you want it. The tracker simply interprets your absence of structural details as a huge scene, possibly compounded by your camera move. That aside, any 3D tracking solution is arbitrary - it is a mathematically plausible reconstruction of the scene, not necessarily a physically exact representation of the real thing, even more so in an uncalibrated track such as this. You can try with other options, but the truth of the matter is it will probably never work. Your only option is to use a solution that supports manual tracker placement to re-construct e.g. the stairs and railing as "reference geometry".
If they don't then either there's too little detail (not enough points to track) or the values for Target and Track Point are wrong. Your shot doesn't have a lot of detail to track but if you pick the right track points you should be able to get something to work.
Once you pick a target by either selecting points or moving around the shot until you find ones you like, click then position the pointer in the center of the target and click and drag to set the position of your layer, then Alt/Option click to scale the target to the right size.
Any new solid created with the 3D camera tracker will be the same size as the Target at 100% scale. Text works a little differently. You need to set the text size in the Character Panel before you create Text or Text and a Camera from 3D Camera Tracker.
I usually set some temporary type in the frame that's a little larger than the the text I want in the scene. I then delete the temporary text layer and create the 3D text layer from 3D Camera Tracker. I then check the scale property, reset it to 100%, then set my final size with the Character Panel.
I'm having the same issue with the bulls eye... i do not see it, yet, i can't even select the tracker points. The only way i can see the tracker points is if the checkbox is selected to render it. Please help get my bulls eyes. Thanks.
i have The Camera Tracker plug-in selected in the Effects Crontrol Panel and the footage selected. i get a nice solve with average error 0.37 pixels. Like i said, i can see and manipulate the Track Point only if Render Track Points is checked. I'm not able to highlight any of the points, yet select them with my mouse. I've watched the above video and it is no help. thanks for the quick reply.
When I do a track then see no evidence of tracking points or targets, in order to get it to work I have to delete the clip, add the clip into the comp again and then reapply the 3D tracker. Then it usually works. This happens in the most recent version of AE CS6. Did not see thie problem in 6.0
Check out this 15 second clip. If you're doing this and the tracking markers don't show up then it's a display, display driver, or open GL problem. OR you may not have Active Camera selected in the Comp Panel.
ok, so i think i found the problem. Since i want to use CS6, i have to get a better graphics card. INSANE! autodesk MAYA works fine but for CS6 my Nvidia card does not have "Shader Model". This is kind of ridiculous, but hey, these companies are all working together to vacuum my bank account!
No, I dont think that is the solution I have the GTX570 which is a real powerful card that works just fine fine with everything and with Camera Tracker up until 6.02. Dont buy that new card just yet.
The success of Camera tracking depends entirely on the shot. This is true for every camera tracking solution I have ever used. Some shots, even with AE's built in solution, track perfectly the first time, others, even with very expensive 3rd party tracking solutions, will NOT track properly.
The biggest thing that screws up camera tracking is the lack of sufficient detail on the fixed geometry in a scene. The second biggest thing that fouls up tracking is lens distortion. AE's and most camera tracking software, assumes no lens distortion. If you have a lens with moderate to severe lens distortion, think cell phone, GoPro and any consumer camera with a wide angle lens, it is highly unlikely that you will get a good track on the footage if you do not remove the distortion first. Without seeing the shot I can't even start to suggest a solution that will work with the footage that is giving you problems. If there is sufficient detail, and you are getting decent tracking marks, and your bullseye is about the size you expect with the default settings and you can't get a good solution then the problem is probably lens distortion. If your tracking marks and bullseye must be scaled way up then the problem could be lack of sufficient detail, a shot not suitable for camera tracking, or lens distortion.
b37509886e