Stabilisation works on proxy but not when I switch to original media

When I switch to view original media my clips are even more shaky than without the stabilisation. They look fine when viewing proxy media.

Am I missing something?

I'm having the same issue. Has anyone found a solution? I tried deleting all generated event files but no luck. When I "deselect" stabilization and "reselect" it, the system doesn't seem to do any processing. It's like it needs to be "reprocessed" but FCPX doesn't want to for some reason. Anyone?

I found the solution! Optimize the media! If you select the file in question, then "File>Transcode Media>Optimize Media," then stabilize! Should work great. I think the reason why the proxy was working and the original media not, is because proxy is optimized for the system. Hope this helps anyone who has the same problem. Yet another reason to always used optimized media... if only it didn't eat up the hard drive!

Sounds like a bug, fill out the feedback page.

Pierre-Alain wrote: I found the solution! Optimize the media! If you select the file in question, then "File>Transcode Media>Optimize Media," then stabilize! Should work great. I think the reason why the proxy was working and the original media not, is because proxy is optimized for the system...

I just tested this on FCP 10.5.1 and MacOS 10.15.7 on an iMac Pro using Sony A7SIII 4k/23.98 10-bit 4:2:2 All-Intra material, and I don't see the behavior.

Whether I apply stabilization in proxy mode or orig. media mode, the clips are stabilized in both view modes.

However -- there are separate render files for proxy vs original media. If you applied stabilization in proxy mode, then rendered the clip with CTRL+R, only the proxy version is rendered to cache. If you then switched the viewer to orig. media, it has stabilization but will not be rendered. Depending on the codec and hardware, that might not play smoothly and might look jerky but it's not lack of stabilization. If you verify the clip is fully rendered to cache in both proxy and orig. media view modes, it should play smoothly.

If besides stabilization there are other effects applied, there are a few cases whereby render files may not be used properly. But in all cases I've seen, stabilization works, it's just a possible playback performance issue.

I get what you're saying. I had tried that and it still wasn't working until I optimized the media in question. I think it might have to do with the source. I've put a bunch of individual smart-phone videos together (it's at "together at home" type concert video). I think the video in question was shot on Andriod... all I know for sure is it isn't an iPhone.

Rendering didn't solve the problem, but optimizing sorted it out no problem.

So, it might be a rare instance, but I think the issue has to do with the source material.

Thanks for replying and offering insight. I'm glad to be a part of the forum now.

Best,

I can confirm that sometimes FCP can’t properly regenerate stabilising data even if you change the edit or delete all renders. Can happen with proxy or original. I never found a way to reproduce the problem. I think somehow the problem is w the stabilise data created and not the render. Every stabilise action creates a data file and how these linked to the media can be problematic. And because the stabilise data file is connected to the media and not the project it’s hard to reset that data. Anyway anyone who figured out a workaround please let us know

cofe wrote: I can confirm that sometimes FCP can’t properly regenerate stabilising data even if you change the edit or delete all renders...the stabilise data file is connected to the media and not the project it’s hard to reset that data...

The stabilization analysis files are stored in the library in /EventName/Analysis Files/Stabilization. They cannot be deleted by the FCP UI or by using Final Cut Library Manager.

However you can delete them manually from within the library (although we are always told don't do that).

If you assign a cache location using the Library Inspector>Storage Locations>Modify Settings>Cache, the analysis files are moved to that package along with render files. Those all exist in a separate bundle called LibraryName.fcpcache. They can be viewed by right-click>Show Package Contents. In general the entire cache bundle can be deleted using Finder, likely without any adverse effects. However YMMV.

Having the cache in a separate folder decreases the chance of making a mistake when manually deleting the cache bundle. It also may have performance advantages if located on a separate drive.

If experiencing a problem with stabilization, try deleting those analysis files. As always, exercise great care, have backups, etc. 

Thanks Joe, I’m aware of the location they are in. The better workaround I found is to replace the clip in the project with a new instance of itself (if that makes sense). I think fcp creates the stabilise data for the portion of the clip currently in the timeline, not for for the whole length of the original clip. And there I think is also where the problem starts by the way. Sometimes that data file gets misaligned to the part of the clip in the timeline and you can’t force a ‘delete the stabilise data and start again’. Replacing that clip with a new version of itself does that, though it would be nice if there would be a ‘recreate stabilise data’ button in the inspector

Hi Guys,

so I had the same issue and found a workaround, that works fine for me.

I'm also using the sony a7siii with 10 bit 4:2:2 footage and have a problem with vertical video stabilization on original media (proxy is working fine).

I'm not sure if someone in this or another forum where talking about that the problem is the vertical footage.

So all you have to do is:
- Reveal the clip in your finder (rightclick - reveal in browser - then rightclick reveal in finder).
- Rotate the clip in the finder (90deg).
- Go back in final cut
- Take the clip, that is now horizontal and stabilize it.
- After that rotate and scale the clip in final cut pro (most of the times -90deg and +183%)

--> Now it should be stabilized

Since I'm not using it on every clip, that workaround works for me.

Hope that helps!


Greetings,
Wolfi