stabilize a long panning shot

hi all,

I am trying to stabilize a long panning shot with planar tracker but the initial polygon track area goes out of shot about half way through.

I read something about offsetting the pattern centre but don't quite understand how to do this.

It is a very simple handheld pan shot following a car - panning from left to right. It is just a bit too wobbly and needs to be smoothed out.

But frame A on the left has no similar data to frame B on the right.

Screenshot 2024-01-25 at 12.59.32.png (623.71 KiB) Viewed 1879 times

Screenshot 2024-01-25 at 12.59.43.png (600.71 KiB) Viewed 1879 times

What settings are you using for the planar tracker? Perspective or TRS?

I think you can just stop tracking wherever you need to stop and then adjust the spline of your tracked pattern to the new pattern you want to follow and then calculate the stabilization.

But depending on the shot, you might be better off using the traditional tracker instead of the planar tracker.

Can you share the shot, so we can see what approach would be best for this specific shot?

What settings are you using for the planar tracker? Perspective or TRS?

I think you can just stop tracking wherever you need to stop and then adjust the spline of your tracked pattern to the new pattern you want to follow and then calculate the stabilization.

But depending on the shot, you might be better off using the traditional tracker instead of the planar tracker.

Can you share the shot, so we can see what approach would be best for this specific shot?

Hey, thanks for replying!

I am using Translation/Rotation so as not to give any image distortion. I am just not sure how to set up another polygon area that can overlap on the timeline.

I kind of need a relay tracking. I will upload the shot in a bit. Just having to do an export now.

You don't need another polygon. Just change the one you have at the time you need to change it.

You don't need another polygon. Just change the one you have at the time you need to change it.

Here it is - download enabled.
https://vimeo.com/906394619/16dd5e5280

would really love to know how to do overlapping stabilisation!

You can stop the track when the pattern is about to go off-screen, then box select the polygon you drew and move it to the other side so it will stay in frame. You can keep stopping and moving it to keep it in frame.

You can stop the track when the pattern is about to go off-screen, then box select the polygon you drew and move it to the other side so it will stay in frame. You can keep stopping and moving it to keep it in frame.

I get this when the left polygon goes out of shot.

Hi Niko,

I just did a track within about 5 minutes. The footage is very easy to track.
Can I use this shot as an example in a short tutorial video?
That way more people can learn from my explanation.

In about 20 minutes you will see a realtime walkthrough at this link:

I hope this helps!

In about 20 minutes you will see a realtime walkthrough at this link:

I hope this helps!

That is incredibly kind. Thank you!

Hi Niko,

I just did a track within about 5 minutes. The footage is very easy to track.
Can I use this shot as an example in a short tutorial video?
That way more people can learn from my explanation.

Absolutely. A great tutorial.

I am just trying it now.

I still get slippage.

The polygon box works froma. few frames then the tracking stops but the footage continues to play, and all the green dots vanish

In about 20 minutes you will see a realtime walkthrough at this link:

I hope this helps!

https://vimeo.com/906431308/d53e211493?share=copy

here is the issue. I have tried multiple times and contiunue to get the slippage of the tracking on the end

Just a thought, what's the codec/file format of the original footage? Some formats are more difficult to decode and thus track than others. You could try converting to an image sequence and see if it helps.

Does it still slip if you only track position?

Does it still slip if you only track position?

I am using prores Proxy file for the 'original' The master file is xf-avc 10 bit canon .mkv
The one i sent you was a much smaller h264 for web.

I am wondering if it is tapping out the system RAM. It seems like the only explanation.It refuses to track past frame 2301 from first frame 1812.

Does it still slip if you only track position?

I tried only position too.

Same issue.

Just a thought, what's the codec/file format of the original footage? Some formats are more difficult to decode and thus track than others. You could try converting to an image sequence and see if it helps.

I have transcoded all my rushes to Prores Proxy as i need to keep it progressive frame based. That should be the best way.

Should could and would. hehe

Just a thought, what's the codec/file format of the original footage? Some formats are more difficult to decode and thus track than others. You could try converting to an image sequence and see if it helps.

I have transcoded all my rushes to Prores Proxy as i need to keep it progressive frame based. That should be the best way.

Should could and would. hehe

Yep. it seems to top out at 2301

If it is anything like After Effects, it may mean the cache size is not big enough.

Does it still slip if you only track position?

Ok. tested it with the clip i sent you and it works fine. it seems that Prores proxy is too heavy to handle for this system.

Im going to see if I can copy the tracking data from the node and apply it to the Prores footage.

What would mean duplication nodes and then shuffling them into the keyframe graph?

That's really strange. Your memory indicator doesn't show it being full at all.
And it's the exact same frame as the first time it didn't track.
Since you're using MediaIn nodes, I almost suspect it's something in the Edit page or the way it's transferred to the Fusion page that is causing this. Does the console show any errors, that might be helpful?

As long as you match the frame numbers, transferring tracker data should be as easy as tracking it one shot, copying the planar tracker tool and pasting it in the shot you want to use it on.
I don't know how good Prores proxy is, but if it's heavily compressed it will be more difficult to track because of artefacts.

That's really strange. Your memory indicator doesn't show it being full at all.
And it's the exact same frame as the first time it didn't track.
Since you're using MediaIn nodes, I almost suspect it's something in the Edit page or the way it's transferred to the Fusion page that is causing this. Does the console show any errors, that might be helpful?

As long as you match the frame numbers, transferring tracker data should be as easy as tracking it one shot, copying the planar tracker tool and pasting it in the shot you want to use it on.
I don't know how good Prores proxy is, but if it's heavily compressed it will be more difficult to track because of artefacts.

Hey,

so first of all, thank you so much for showing me how to track properly. It saved the day. Edit delivered. Secondly, I am sure it was a RAM issue. I think the Prores Proxy was too heavy a computation per frame. h264 was great and copying node data worked great.


Thanks for working this through with me.