AlphaGyro Studio Guide

Installation

Get the installer from the download page. It detects your system and highlights the right option. Before installing, check that the file's SHA-256 matches the one published on that page.

macOS

1. Choose Apple Silicon (M1 or newer chips), Intel or Universal (runs on both, larger file). To find out which Mac you have, open Apple menu → About This Mac: "Chip" means Apple Silicon; an Intel "Processor" means Intel.
2. Open the .dmg and drag AlphaGyro Studio into the Applications folder.
3. Launch the app from Applications. If macOS shows a security prompt on first launch, confirm the file came from this site and the SHA-256 matches before continuing.

The .pkg installer performs the same installation without dragging and is handy for deploying to several Macs.

Windows

1. Run AlphaGyro-Studio-Windows-x64-Setup.exe and follow the wizard.
2. If Windows SmartScreen shows a warning, check the file's origin and SHA-256 before continuing.
3. The portable version (.zip) needs no installation: unzip it into a folder you can write to and run the program. It creates no shortcuts and does not update itself.

Updates

The app checks for new versions by sending only the installed version, operating system, architecture and channel (stable, beta or nightly). The downloaded package is verified by SHA-256 and digital signature before installation, and installation waits for any running render to finish.

Import

Drag an MP4 or MOV file recorded by the Air Unit into the app window, or use File → Import. On import, AlphaGyro Studio analyzes the file and shows container, codec, resolution, frame rate, bit depth and camera.

Gyro detected automatically

The DJI O3, O4 and O4 Pro Air Units record gyro data in a metadata track inside the video itself (djmd). The app reads that track on its own, identifies the camera and applies the matching lens profile. No separate log file is needed.

Synchronization

With DJI footage the gyro is already time-aligned with the video, so usually there is nothing to do. If the image seems to "lag" behind the motion, use automatic sync, which computes the offset and shows a confidence score, and fine-tune the offset in milliseconds manually if needed.

External gyro

You can also import gyro data from another source, as .gcsv or a Blackbox log (.csv / .bbl), and attach it to a video. In that case synchronization is essential, since the two devices' clocks differ.

Projects

Each video's settings live in an .agproj project. Save the project to come back later with the same stabilization, sync, lens, crop, horizon, LUT and render settings.

Stabilization

Use the preview with original / stabilized comparison (split mode with a divider) to judge each adjustment. The timeline shows the gyro rotation, applied correction, crop and horizon curves.

Smoothing

Controls how much motion is removed. Low values keep the energy of the flight and only remove vibration; high values give a cable-cam look but require more crop during sharp maneuvers.

Horizon lock (0–100%)

Sets how level the horizon stays. At 0% the video follows the drone's tilt; at 100% the horizon stays locked even through rolls. Values in between, such as 50–80%, level the horizon while still letting you feel the turns. High horizon lock during full rolls requires more crop.

FOV and crop

All stabilization needs margin: the image is rotated and shifted, and the edges are cropped so no empty area shows. Adjust FOV and crop to balance stability and field of view. A more conservative dynamic crop avoids black borders in hard maneuvers; a fixed crop keeps framing constant.

LUT

For D-Log M footage (O4 Pro) you can import a .cube LUT and apply it to preview and render. Imported LUTs are copied to your user LUT folder and remain available for future projects.

Render

Presets

After picking a preset you can adjust codec, bit depth, resolution, frame rate, bitrate, audio (copy, re-encode or remove), video range and metadata preservation.

Codecs

• H.264: maximum compatibility with players and social networks. 8-bit.
• HEVC (H.265): smaller files with more quality; supports 10-bit.
• ProRes: for editing and color grading; large files, keeps 10-bit.

To keep the O4 Pro's 10 bits, export HEVC 10-bit or ProRes.

Encoder

By default the encoder is chosen automatically: the system's native hardware encoder (VideoToolbox on macOS; NVENC, AMF or Quick Sync on Windows) and, if unavailable, slower software encoding. The combination of resolution, frame rate and codec must be accepted by the hardware; if it is not, the app warns you before starting.

Batch render

Add several videos or projects to the render queue. Each item shows its stage (preparing, decoding, processing, encoding), progress, speed in frames per second, time remaining and the decoder and encoder in use. You can pause, resume, cancel and remove items.

Render recovery

If the computer shuts down or the app closes in the middle of a render, AlphaGyro Studio lists the interrupted sessions the next time it opens and offers to recover (continue where it stopped) or discard.

Profiles

Profiles describe the camera and lens: wide-angle distortion, gyro orientation and default parameters. The app ships with profiles for DJI O3, DJI O4 and DJI O4 Pro and picks the right one on import.

• Profiles are updated separately from the app. Every downloaded profile is verified by SHA-256 and digital signature before installation.
• Each profile states the minimum app version it supports; incompatible profiles are not installed.
• If automatic detection gets it wrong (for example, on an edited or re-encoded file that lost its metadata), choose the profile manually in the project's lens settings.

Command line

For automation and render servers, AlphaGyro Studio has a command-line interface.

Stabilize a video:

alphagyro input.mp4 --stabilize --camera dji-o4-pro --output out.mp4

Render every video in a folder:

alphagyro batch ./videos/

For --camera, use your camera's profile identifier, such as dji-o4-pro in the example above. The command line uses the same presets and profiles as the app, and processing stays 100% local.

Troubleshooting

Help → Diagnostics

The Help → Diagnostics screen shows the detected GPU, available decoders and encoders, Metal or DirectX, driver versions, supported codecs and the log file paths. Use Export diagnostics to create a .zip and send it to support with a description of the problem. It contains technical information about the machine and logs; your videos are not included.

Logs

Logs live in the app's data folder:

• macOS: ~/Library/Application Support/AlphaGyro Studio/
• Windows: %LOCALAPPDATA%\AlphaGyro Studio\

The exact path of each log (such as Application.log) is shown in Help → Diagnostics. Every error message in the app includes a code, the likely cause, the suggested fix and a reference to the log.

Common issues

• "Gyro not found": the file is probably not the Air Unit original (it was re-encoded, trimmed in another program or downloaded from social media) or it was recorded with electronic stabilization on. Use the original file from the card.
• Image shakes or "lags" behind the motion: run automatic sync and check the confidence score; if it is low, adjust the offset manually.
• Black borders during maneuvers: increase crop, lower horizon lock or lower smoothing.
• Slow render: check in Help → Diagnostics that the hardware encoder is active; update your GPU driver; use Fast Preview for reviews.
• Cannot export 4K/120: your machine's hardware encoder may not accept that combination. Try HEVC, another frame rate or the software encoder.
• Washed-out colors on the O4 Pro: the footage is in D-Log M; apply a conversion .cube LUT.

Still stuck? Contact support and attach the exported diagnostics.