Mask tracking zero progress

I've been having this same issue for weeks now. I've found success if you nest the clip you are trying to do the motion tracking on. It seems to force it to work for some reason.

I was having this same issue. What I did, that seemed to work, is I would save what I had done, closed the project and reopened it. The first thing I did after reopening was hit try to track the mask I made and it worked. It's worked for me so far, maybe not a permanent solution but it gets the job done.

Hope this helps.

Yup - it's not good enough, even if it did work consistently.

The only thing I've been able to do that does work consistently is save, quit Premiere, reopen project. Simply not viable long-term.

Trust me nesting was the first thing I tried - but it doesnt work. However,
even if it did work nesting is not a solution. its a bandaid that ads a
kink into the workflow

[Personal Information removed by moderator]

Edit: Doesn't always work...

Found a very easy solution (M2 Max):

Just nest the clip you want to track, copy the effect with the mask (gaussian blur) from the clip and paste to the nest instead. Tracking works perfectly on the nest. Hope that helps!

Same issue.  M1 Max Macbook Pro - 32 GB Ram, etc.  You guys actually gonna fix this?

same issue

I've tried working backwards – it doesn't solve it, still hangs just as often.

My video should be done by now, I'm spending hours just retrying and retrying mask tracking over hundreds of clips, and it is absolutely destroying my productivity at this point. It works on one clip, then it takes me 10 tries involving selecting other clips, moving the playhead away then back onto the keyframe I need to start from, to get it to work on the next clip. I cannot believe Adobe has let this bug persist for SO long. I cannot work like this. Final Cut is ready and waiting for my next project next week and I can't wait to use it.

Same issue. M1Max, Ventura 13.2.1, PPro 24.1.0

So, the latest version of PPro and this seemingly old bug within a feature that is so present in workflows these days is still happening... Come on, Adobe!?

A possible work-around that seemed to work for me is not to track forward, but backwards. Gives me much less issues.