Hey again, I get to it :
I got around a tricky remove recently, and found out - after hours of investigations and tests - that just tiny drifts in the BG track due to a crazy jumping surface messed the remove (which also drifted consequently), I decided to link the remove layer track to the BG layer track and this helped finding the solution. I tried this again and it worked on every other test…
Layer track obligation : In this case, tracking one layer is enough since we link the second layer track to this very first one, BUT… it seems that Mocha needs a real track of every layer, doesn’t it ? Therefore I can track the first, track the second and then link one track to the other, meaning that one of this tracking actions is useless… Is there a way to avoid tracking a layer when you know that it’s going to be linked afterward anyway ?
Remove spline feather : When the goal is an insert, Mocha provides a “feather” tab inside the Insert options… Regardless to the fact I still have to check how it works there, I’m looking for a way to have the same but for a Remove action and I must have missed the way to achieve it.
Is setting a negative (or positive) edge width to the spline and clicking to set a certain amount of blur the way to reach the goal ? I doubt it…
What do you think (my ideal way, being able to deal with the spline the way I would with Resolve power windows : adding inner and outer boundaries to the spline to soften it), can I do this ?
Congrats here : I just tested 3 minutes of Mocha 2019 (Remove, obviously ) and I was smashed by the speed of the remove rendering (moreover on the same project which was so painful) ! Congratulations, it’s a huge upgrade.
I just found weird that I had to “allow unsupported GPU” in the preferences though I have 2 x gtx 980 ti in my legacy macpro (works well when done btw). I checked the logfile as suggeste and found:
Oct 15 13:17:26 (mochapro) Name: GeForce GTX 980 Ti
Oct 15 13:17:26 (mochapro) Vendor: NVIDIA
Oct 15 13:17:26 (mochapro) Version: OpenCL 1.2
Oct 15 13:17:26 (mochapro) Driver version: 10.11.14 346.03.15f16
Oct 15 13:17:26 (mochapro) Global memory size: 6.0 GiB
Oct 15 13:17:26 (mochapro) Local memory size: 48.0 KiB
Oct 15 13:17:26 (mochapro) Number of computing units: 22
Oct 15 13:17:26 (mochapro) Maximum work group size: 1024
Oct 15 13:17:26 (mochapro) Maximum work item dimension: 3
Oct 15 13:17:26 (mochapro) Maximum work item sizes: (1024, 1024, 64)
Oct 15 13:17:26 (mochapro) Maximum clock frequency: 1190 MHz
Oct 15 13:17:26 (mochapro) Available: no (Device is not supported due to crashes in the Nvidia driver.)
But since it works great, it’s just FYI…