If it IS a bug you also need to talk to Foundry. Sometimes you just have to either try picking different reference points or re-track.įinally, Foundry camera tracker isn't FXhome code. There are infinite mathematical solutions to any shot and Foundry is picking one (this is why, sometimes, a track makes everything close to the camera - maybe a hundred units - while, sometimes, everything is a million units away). Foundry is tracking hundreds of 2D points, comparing how they move relative to each other, taking the camera information and making an educated guess. Certain points just track badly and those need to be eliminated before solving.ģD camera solves are all a lot of guesswork.
#HITFILM EXPRESS MOTION TRACKING HOW TO#
Knowing how to refine your track is important. If you know your camera sensor size and the 35mm equivalent focal length of your lens, giving Foundry that information helps. In these situations you need to be using a matte to eliminate those elements.įoundry works a lot better if you feed it proper camera information. Things that reflect - mirrors, windows, water - can throw off your track.
If you have anything moving in your frame - people, cars, water, trees in wind - that throws off the track. You can use an embedded comp shot to define a matte that defines areas Foundry ignores. At least one is a possible user error.įoundry is point tracking on steroids - its tracking hundreds of points to make a cloud, extrapolating from there based on sensor information given.įoundry assumes everything in the frame is static.
This is a tough one to debug sight unseen.
0 kommentar(er)
