-
stabilisation
Hi all…I have a shot that’s pretty steady but now I’ve applied some text you can see the slight camera shake. I thought it would be pretty easy to stabilize…there’s a reasonably contrasty bit of a tree to stick the cross-hairs on and I’ve read the Meyers tips pages but still get a poor track…when I hit the button right from the start the cross-hairs are jumping around even when there is no movement in the shot…sureley they should stay rock steady at that point…I’ve tried changing the comp settings to 50 fps…this is getting embarrasing ’cause one of the guys in the office could do it in 5 minutes in Combustion….I don’t want to give him the pleasure…many thanks for your time…Roger
-
6 Replies
-
If you want to make the search area bigger and even the track area bigger it might be a bit more accurate although it may take a little more time.
In this tutorial around 2 minutes it shows how to get a good track.
https://www.videocopilot.net/videotutorials/sky_replacement/Good Luck
Andrew -
Part of the problem is that Combustions tracker is far better than AEs. If you own a copy of Commotion, use that, it has a smokin’ tracker that is very smooth and has easy tools to help you do multiple tracks and average them.
Search the archives for ‘averaging tracks expression’. A few weeks ago a poster posted his expression for averaging AE tracks to get smoother results.
Chris Smith
https://www.sugarfilmproduction.com -
Thanks Andrew and Chris…I’ll try both before I ask a favour of the Combuster…Roger
-
is your footage film or video. for example are you tring to stabilize out gate weave or just camera shake. If it’s film try to track on either the red or the green channel where there is less grain. afx tracker is not that good and may be tring to track the grain. secondly look for nice corners to track. increase search distance.
-
Geesh, if it’s gate weave then make a note not to use that camera house or telecin
-
I recently had a problem tracking: The tracker was all over the place despite any motion. Turns out the problem was due to the video being compressed with h264 and there’s no intermediate frames to track(?).
The solution was exporting to a ..lossless format and track that.
I know this reply is way to late (but I don’t know if there’s a rule against it) but maybe it will help someone in the future!
Reply to this Discussion! Login or Sign Up