Frequently Asked Questions

AlphaGyro Studio is desktop software for macOS and Windows that stabilizes FPV footage using the gyroscope data recorded by the camera itself. It is built for the DJI O3, DJI O4 and DJI O4 Pro Air Units: import the MP4 or MOV, tune smoothing and horizon, and export H.264, HEVC or ProRes, all locally on your computer.

DJI O3 Air Unit, DJI O4 Air Unit (O4 Lite) and DJI O4 Air Unit Pro, with gyro and lens calibration read from the file itself. RunCam Thumb/Thumb Pro, RunCam 5 Orange, iFlight GOCam GR and Mobius Maxi 4K through the gyro CSV the camera writes next to the video. HDZero and Walksnail do not record gyro in the video: import the Blackbox log (Betaflight/INAV) of the same flight and AlphaGyro synchronises it automatically from the image motion. Gyroflow .gcsv files are accepted too.

Yes. The DJI O3 Air Unit records gyro data inside the video file and AlphaGyro Studio reads it automatically. For the best result, record with electronic stabilization (RockSteady/HorizonSteady) turned off in the goggles and at the widest FOV.

Yes, including the O4 Lite (DJI O4 Air Unit). The camera is detected automatically and the lens calibration and sensor readout come from each clip. Record with electronic stabilisation (EIS) off: with it on the camera does not store gyro data.

Yes. The DJI O4 Air Unit Pro is supported, including 10-bit HEVC recordings with D-Log M. The app keeps all 10 bits when you export HEVC 10-bit or ProRes, and you can apply a .cube LUT to convert D-Log M.

Yes. RunCam (Thumb, Thumb Pro, RunCam 5 Orange) and compatible cameras write a gyro CSV next to the video, which AlphaGyro finds on its own. HDZero and Walksnail do not record gyro: import the flight's Blackbox log; automatic sync aligns time and detects the axis orientation. These cameras need a lens profile (importable) — without one the app uses an estimate and warns you.

AlphaGyro already reads the gyro in DJI .OSV files. 360 stabilisation (re-orienting the sphere to remove shakes, no crop) arrives in version 1.0.1. Insta360 follows once its gyro format is validated with real files.

A GPU with up-to-date drivers is recommended: preview and rendering are much faster and the hardware encoder (VideoToolbox, NVENC, AMF or Quick Sync) is used when available. It is not mandatory, though: if the GPU or hardware encoder is unavailable, AlphaGyro Studio falls back to CPU processing, which works, just slower.

Yes, on macOS 12 or newer, on Intel and Apple Silicon (M1, M2, M3, M4…), always native: the app is Universal and uses each machine's Metal GPU and VideoToolbox. On an Intel i5 MacBook with Iris Plus we measured 4K 10-bit HEVC at ~21 fps end to end; Apple Silicon is faster.

Yes, on Windows 10 21H2 or later and Windows 11, 64-bit (x64), with DirectX 11 or 12. There is an installer and a portable version.

Yes. The app reads 10-bit footage (such as the O4 Pro's 10-bit HEVC with D-Log M) and exports HEVC 10-bit or ProRes keeping the color depth. If you export H.264, the result is 8-bit, since that is what the codec supports in practice.

Yes, but speed, and whether 4K at 120 fps can be exported at all, depends on your machine's hardware encoder: not every encoder accepts 4K/120 in every codec. When the hardware cannot do it, the app tells you and offers alternatives, such as another codec or the slower software encoder. Help → Diagnostics shows what your computer supports.