18.0.1 Studio Object Mask Losing Tracking Data

If I try to use this new feature, I am constantly "losing" my tracking data and having to retrack. This can happen even if I am doing nothing to the node that has the tracking data on it. It happens constantly and I feel certain this is a bug in 18. Can someone confirm they are having the same problem?

Erik

It's (apparently) not a bug Erik, just a byproduct of the current design. My understanding is that only the 'strokes' are project data, the generated mask data is cache data. If you invalidate the cache you lose the mask. That said, I only have v18 on my laptop for testing these things, so my experience with Object Mask workflows is minimal. My production machine is still running v17.
viewtopic.php?f=21&t=165470#p874607

I wonder where the mask data was stored in Resolve 17. I would have thought that it would have been equally as volatile but perhaps not?

Thanks Andy,

How does one "invalidate" the data? BTW, I looked in the manual and didn't see anything about this. Which cache are we speaking of? I don't use any timeline caching in my workflow.

Erik

Sorry Erik, I have no arcane knowledge in this regard. How does one "invalidate" the data? By doing a thing that results in Resolve unlinking the previously associated cache file. There are obvious things that would cause that result, like changing an input to the node, and less immediately obvious things (though they also make sense) like changing your timeline resolution. This is not new info, the design drawback was confirmed by BMD when the feature was first rolled out in the public beta phase.

Thanks again Andy. I am looking where to read the specifics or full list of the reasons why one would lose cache on an object mask tracking. Often, I lose the cache very easily even when it seems I am not making any adjustments at all.