orbis-reframe Manual Camera formats Download Source code

What orbis-reframe knows about the cameras' recorded files, kept up to date with its development. On GitHub.

Antigravity A1 file format

Desk research (2026-10-15); measured on clips 2026-10-29: three contributed 8K H.265 flights, then a second set from the same drone: one H.264 clip in each of nine video modes (8K, 5.2K, 4K 100) and two photos; a third set (2026-11-01, measured 2026-11-02): a take-off and a landing, 5.2K 60 in H.265, 4K Slow Motion, a timelapse, a 14 MP photo and AEB DNGs, and Antigravity Studio's 360 exports of one clip (Modes and sample clips). What's marked ✅ below is checked on them; the modes we have no clips of are still desk research, from reviews and Gyroflow's telemetry-parser. The app supports the A1 experimentally from 2026-10-29: 8K clips open, stitch, stabilize (leveled by the drone's own attitude) and export; 5.2K and 4K 100 clips open and stitch (below). The A1 is a 360 drone from Antigravity, a brand incubated by Insta360, and writes the same .insv family; written as differences from the X5 (insta360-x5.md, "X5 §n" below). Markers as in README.md.

Streams

Trailer

Slow motion and timelapse

✅ One clip of each (2026-11-01, measured 2026-11-02). In both, the video's time is not the drone's clock: the motion and exposure records run in real time while the video plays slower or faster. The app turns video time into the drone's clock by a capture scale, seconds of the clock per second of video (orbiscore::CaptureScale): field 196 over field 195 in slow motion (0.2997), a timelapse's frame interval times the stored rate (60), from its frames' own times (type 6) where it has them, else from field 30. Sync, stabilization (its smoothing windows stay in video time), the GPS and the motion overlays all go through it (2026-11-04).

Photos

✅ Two 55 MP single shots (2026-10-29, the same drone), then two more and a 14 MP shot (2026-11-01):

The app doesn't open 360 photos yet (roadmap, 360 photos); the trailer holds all the stitch needs.

Modes and sample clips

All the A1's modes 📖 (Antigravity's spec table as retailers and reviews reprint it, and the spring 2026 update for timelapse; Sources). Our clips, from one contributor and one drone (firmware 10.0.397.3_5.5): three 8K H.265 flights (2026-10-28), and a set of nine H.264 clips, one per mode, plus two photos (2026-10-29), flown low over a field. The second set came renamed by mode but is otherwise straight from the drone (field 9, Streams); the videos have their names back (Streams): _013 8K 25, _014 8K 24, _015 5.2K 60, _016 5.2K 50, _017 5.2K 30, _018 5.2K 25, _019 5.2K 24, _020 4K 100, _021 8K 30. The photos keep the contributor's names. A third set (2026-11-01), with the drone's own names, over a park: _024 8K 30 H.264, take-off from a pad, then a hover with turns (43 s); _025 the same, a low hover and landing (10 s); _026 its proxy only (67 s, on the pad); _027 5.2K 60 H.265 (32 s); _028 4K Slow Motion; _029 a timelapse; photos _030 / _032 55 MP, _031 14 MP; _033-_035 AEB DNGs. All our files come from the microSD card.

Studio references for _021 (8K 30, H.264): Antigravity Studio's exports as 360 equirect, 7680×3840 H.265, ~200 Mb/s, at exactly 30 fps (2113 frames; the clip has 2111 at 29.97), so frames are matched by time, not by number. Unstabilized: AI Stitching, FlowState off, Chromatic Calibration off, no adjustments -- the reference for the stitch's geometry, seam and colour. Stabilized: the same with FlowState on, level. Each has a silent AAC track. The unstabilized one is still in the drone's body frame and lines up with the clip from its first frame (Trailer above has the rotation). Studio's earlier flat 3840×2160 exports of the same take (AI Stitching and Chromatic Calibration on) show the raw body frame without FlowState (horizon on end). The status words are the X5's (X5 §3.4).

Mode Spec Files Our clips Status
360 Video 8K 7680×3840, 30 / 25 / 24 ✅ one .insv with both lenses (two 3840² streams), and a PRX_….prx proxy 3 at 29.97 fps, H.265; 5 at 29.97 / 25 / 24, H.264 (with a take-off and a landing); standard colour experimental: opens, stitches, stabilizes and exports; GPS lined up by its speed
360 Video 5.2K 5248×2624, 60 / 50 / 30 / 25 / 24 ✅ as above, two 2624² streams 5, one at each rate, H.264; 1 at 60, H.265 experimental, as 8K: plays in real time (60 fps: 4.0 ms a frame on an RTX 5070), Horizon lock level within 0.2°, sync within 5 ms, exports (5.2K 60, _015)
360 Video 4K 3840×1920, 100 / 30 / 25 / 24 ✅ as above, two 1920² streams; 100 fps stored at 100 1 at 100 fps, H.264 as 5.2K: plays at 100 fps (3.3 ms a frame), level within 0.5°, exports (_020); wanted: 30 / 25 / 24
4K Slow Motion 3840×1920, 30 / 25 / 24 ✅ as 4K, stored at 29.97, captured at 100 (field 195; Slow motion and timelapse) 1 at 29.97, H.265 experimental: plays as stored (3.34× slowed, as the drone means it); sync, stabilization and GPS on the capture time (by the tools); Media information shows Slow motion
H.264 encoding up to 170 Mb/s, as H.265 ✅ as above, H.264 High; field 132 = 1 11 as its mode in H.265
Timelapse added by the spring 2026 update; ❓ other sizes and intervals ✅ as 8K, one frame every 2 s, IMU kept, no proxy (Slow motion and timelapse) 1 at 8K, 2 s, H.265 (a hover) experimental: stabilization on the flight time (by the tools); Media information shows Timelapse; wanted, low: another interval, one in flight (for the GPS)
360 Photo: Standard, HDR, Burst, AEB 55 MP 10496×5248, 14 MP 5248×2624 ✅ .insp, ✅ .dng per AEB bracket (Photos) 4 at 55 MP, 1 at 14 MP, 1 AEB set (3 DNGs) not supported (no photos in the app yet); wanted, low: HDR
Internal storage (20 GB) vs microSD ✅ microSD; internal ❓ all from microSD wanted, low: a clip from the internal storage
Audio not in the spec table ✅ no audio track in our clips 17 done: opens and exports as picture only
Drone in the picture (props, arms, landing gear) 3 in flight; _024 take-off, _025 landing done in flight: a part at lens 0's rim only, outside the stitched picture; on the ground the landing legs are in lens 0 (Streams), ❓ in the stitch
Replaceable lenses none wanted, low: whether the calibration in the file follows a lens swap
IMU axes _010 (flight turns) done (-x,y,-z)

Cinematic, Normal and Sport are flight modes, not recording modes; they change how the drone moves, which matters only for the stabilization check.

Still wanted, 10–30 s each, straight from the card with the whole folder and with the drone's own file names, as in "Sample clips wanted" (README.md):

  1. The .insv of the third set's _026 (only its proxy came).
  2. 4K at 30, 25 or 24 (not Slow Motion).
  3. An HDR photo, low.
  4. A clip recorded to the internal storage, low.

Sources