App: Gyroflow Toolbox
Developer: LateNite Films Pty Ltd
Genres: Foto und Video, Dienst­programme

Gyroflow Toolbox allows you to import Gyroflow Projects into Final Cut Pro. 

Advanced gyro-based video stabilisation without the round-tripping!

Gyroflow is a free and open source third-party application that can stabilise your video by using motion data from a gyroscope and optionally an accelerometer. Modern cameras record that data internally (such as Blackmagic, GoPro, Sony, Insta360 etc), and Gyroflow stabilises the captured footage precisely by using that data. It can also use gyro data from an external source, such as Betaflight Blackbox.

Gyroflow Toolbox allows you to take the stabilised data from Gyroflow and use it within Final Cut Pro as an effect, so you don't have to export a ProRes from Gyroflow!

You can even use this in conjunction with BRAW Toolbox (also on the App Store), to stabilise Blackmagic RAW files!

To get started, simply drop your video clip from the Final Cut Pro Browser or Finder to the drop zone in the Final Cut Pro Inspector. You can also drop a Gyroflow Project.

Sony, GoPro (Hero 8+), DJI, BRAW and Insta360 will be automatically synced when imported. Other cameras, such as RED, will require launching Gyroflow to synchronise.

GoPro, DJI and Insta360 will automatically select a Lens Profile. For all other cameras, you may need to manually select a Lens Profile, however, we'll try and GUESS a good match.

None of this would be possible without the incredible Gyroflow project and the incredibly help and support from their main developer, AdrianEddy.

The Gyroflow Toolbox icon was designed by the amazing Matthew Skiles.

Release notes:
BUG FIXES:
- Fixed a bug where the stabilisation wouldn't load correctly after importing a clip or Gyroflow Project into Final Cut Pro until after you modified a parameter or toggled the Stabilisation Overview. Thanks for reporting JoneyMacaroney and JLPG!
- Fixed a bug where the Gyroflow Toolbox version information at the top of the Final Cut Pro Inspector was incorrect. Thanks for reporting JoneyMacaroney and JLPG!