Sun Mar 31, 2024 11:08 am
Hey
Imho, it's a cache issue (yes, another one), though I couldn't tell you how to fix it ...
Obviously, starting the track a few frames before it's needed appears to be a troubleshooting solution for you. And btw, what if you start a reverse tracking from a couple of frames after to cover the missing one, does it fail the same way ?
*MacMini M1 16 Go - Ext nvme SSDs on TB3 - 14 To HD in 2 x 4 disks USB3 towers
*Legacy MacPro 8core Xeons, 32 Go ram, 2 x gtx 980 ti, 3SSDs including RAID
*Resolve Studio everywhere, Fusion Studio too
*https://www.buymeacoffee.com/videorhin