This is a fascinating bug, and as has been the case with many PD head-scratchers over the years, it involves a binary number. This time, the magic (cursed) number is 4096 (i.e. 2^12).
If the maximum number of Motion Tracker frames exceeds this amount, the tracker no longer works properly. With this 25fps clip, the problem will occur if the tracker goes beyond 2m 43s (163 seconds * 25fps = 4075).
Once that boundary is crossed, two things happen: First is that the tracking object (title, pic or FX) will remain stuck at its inital location and will not move at all; second is that the MT timeline track will extend the entire length of the source clip, even when the actual tracker's duration is much shorter.
In this screenshot, you can see that the actual tracker length is 2:47 (4175 tracking fames), while the MT clip on track 2 of the timeline runs for the full 7 minutes of the source clip:
I've created 2 packed projects in this OneDrive
folder, and it should be very easy to verify that they each behave as I've described.
One other thing to keep in mind is that once a clip has been motion tracked, the tracker will
always follow that clip and will appear in completely unrelated PD projects if you ever use that clip again. See this
thread for all the gory details
, and that's why I used two copies of the source clip in the two packed projects.
VanSolo, please include the URL of this post in your next correspondence with Tech Support so they'll see what's going on here.
As a workaround, please use this table for determining the maximum duration of a single motion tracker for each type of clip:
Clip FPS |
Max MT Duration |
24 |
2m 50s |
25 |
2m 43s |
30 |
2m 16s |
50 |
1m 21s |
60 |
1m 8s |
This message was edited 1 time. Last update was at Jan 04. 2020 15:35
YouTube/optodata
DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors
Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°