Has Stabilization turned into a shaker?

Since 1.7, Stabilization is not only not working anymore, I just realized it makes the videos even more shaky, I check out this “mysterious” options in the Model Manager, downloaded at lot of thinks, but no change.

Please advice.

Find my logs attached.

logsForSupport.zip (1.3 MB)

Short Example for the new shaking feature: https://youtu.be/RAf2iH7016Y?si=lK4i4ClFNYJoaYJD :grin:

Can you share the original sample with the support team for testing?

You can securely submit your file(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something and include the file name.

Submit File to Dropbox

Wow. Totally forgot how slow Dropbox is :slight_smile:

I uploaded several versions. And also attached a small text file with explanations.

Got the files and will look into this situation.

Looks like the interlaced step is causing some odd distortions when being applied in the same process as stabilization.

Have not seen that occur before, but would recommend running the deinterlace first and then stabilizing in a second stage. I’m sending a note to the team about this for further investigation.

Hi Kyle,

(De)interlaced is not the problem.

I just tried it with a XAVC Intra UHD 50p S-Log3 file that could hardly be further away from being interlaced.. You can find the original MXF and the Topaz ProRes file along with the longs here:

https://www.swisstransfer.com/d/5c125bed-4912-4034-b01a-dd45bed31a66 (deletes Sep. 21st)

Thorsten

Interesting, Ill take a look and run a test on it to see if I can replicate.

I had a test run earlier with just Dione TV on the original file that came back messed up without even applying stabilization.

Hello,

I just quickly produced a slightly shaky video. XAVC Long 422/10 50Mbps. Stabilization works successfully directly in Final Cut. It fails in Topaz, however—both with Full Frame and Auto Crop. The source and output files can be downloaded here:

https://www.swisstransfer.com/d/f39a109c-10b9-4a96-9601-378e283142c3

Thor

I have encountered the same, but on just a single file so far. Unrelated to deinterlacing.