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.

Insta360 ONE X2 file format

Examined on two clips (2026-10-20). Written as differences from the X5 (insta360-x5.md, "X5 §n" below). Markers as in README.md. The ONE X2 facts come from the clips below, read with ffprobe, insv_trailer_dump and a throw-away trailer / protobuf walker; field names are telemetry-parser's (X5 §13). The app reads the 5.7K two-file take since 2026-10-21 (the calibration from offset_v3, the lens-1 file found beside the _00_ one, telemetry in ms); what's still open is in §11 and §12.

The older, two-file generation: one file per lens at 5.7K. The X3 works the same way and has its own document, insta360-x3.md.

Reference clips (sample_footage/insta-one-x2/, gitignored), one camera, firmware v1.0.92_build1, recorded 2025-08-16 with the camera on a stick:

take files length notes
103807_…_001 VID_…_00_001.insv, VID_…_10_001.insv, LRV_…_11_001.insv 309.4 s, 7736 frames
105108_…_003 VID_…_00_003.insv, VID_…_10_003.insv, LRV_…_11_003.insv 188.2 s, 4704 frames

Twelve more takes from the same day and camera (added 2026-10-21, the same three files each): _002, _005, _006, _008–_012 walking around a bike meet on the stick (16–215 s), _004, _007, _013, _014 riding (1323, 731, 419, 230 s). All are the same mode: 5.7K (2880² per lens) at 25 fps, H.264, the same offset_v3 and firmware, and every _10_ file is one frame shorter than its _00_ (§3.1).

And one take from 2025-08-04 on older firmware (v1.0.62_build2, same calibration): VID_20250804_152938_00_003 + _10_ + LRV, 5.7K at 29.97 fps (30000/1001), 1740.9 s (29 min), 52176 frames, 10.96 GB and 10.91 GB -- the longest clip here. Here the two files have the same frame count.

Seven more takes from that day and firmware (added 2026-11-08, the same three files each), all 5.7K 29.97 fps: 152306_…_001 (6.9 s), 152716_…_002 (29.1 s), and five 1.7 s takes _005-_009 and one 0.97 s take _010 -- edge cases for very short clips. Their _10_ files are one frame shorter, as on the 25 fps takes (871 / 872, 50 / 51, 28 / 29), except _001 (206 / 206).

Beside them are five flat videos exported from Insta360's software from the same day (1.MP4, 2.MP4, 3.MP4, CKDH4299.MP4, EXAM7155.MP4): 3840×2160 30 fps HEVC Main 10, HLG (arib-std-b67, BT.2020) with a Dolby Vision configuration record, tagged make Insta360, model ONER.FixFrame, muxed by Lavf60.3.100. Edited (reframed, a tiny planet, a title), so they show Insta360's look and HDR export, not a reference frame for the stitch.

1. Files

2. MP4 container ✅

ftyp  (32 B)    major_brand "avc1", compatible "avc1isom"
mdat            the A/V samples of this one lens
moov            two tracks; udta holds only an Ambarella "AMBA" box (107 B)
free            padding up to the next 1 MiB boundary of the file
trailer         _00_ and LRV only: the inst records, raw, to EOF

3. Streams

3.1 VID_…_00_ / _10_ (one lens each) ✅

index what details
0 the lens's fisheye video H.264 Main, avc1, level 5.2, 2880×2880, 25 fps, ~45 Mb/s, no B-frames (has_b_frames=2 in the header, but only I and P frames), GOP 16 (0.64 s)
1 audio AAC-LC, 48 kHz stereo, 128 kb/s

3.2 LRV_…_11_ (proxy) ✅

index what details
0 video H.264 Main, 736×368, 25 fps, ~14 Mb/s, GOP 15, no B-frames
1 audio AAC-LC 48 kHz stereo, the same samples as the masters

3.3 Every mode, and our clips of it

All the ONE X2's modes 📖 (Insta360's shooting specs, Sources), with our clips and whether they're enough to build and check the reader on. The status words are the X5's (X5 §3.4): enough, one clip, wanted.

Mode Spec Files Our clips Status
360 Video 5.7K 30 / 25 / 24 _00_ + _10_ + LRV_…_11_ 14 takes at 25 (walking and riding), one 29 min take and seven short ones (0.97-29 s) at 29.97, H.264, gamma_mode linear enough at 25 and 30 H.264; 24 wanted
360 Video 4K 50 / 30 one VID file (+ LRV at 30 only) none wanted: the one-file layout
360 Video 3K 100 one VID file, no LRV none wanted
HDR Video 5.7K 25 / 24 ❓ none wanted
H.265 encoding none wanted
Filters Vivid / LOG none LOG wanted: Insta360 publishes a LUT for it (ONE-X2-LUT-Final-V1.0.0.cube, 65³, the same file as the X3's); Vivid low
Timelapse 5.7K 30 no LRV none wanted
TimeShift 5.7K 30 / 25 / 24 no LRV none wanted
Bullet Time 3K 100 no LRV none wanted
Steady Cam (Ultra Wide Stabilization, 150°) 1440p 50 / 30, 1080p 120 / 50 / 30; HDR, Timelapse, TimeShift at 1440p .mp4 none wanted: a flat clip, may open as one already
Split recording ❓ (§12 question 3) none split: _004 (1323 s, 7.5 GB per lens file) and 152938_…_003 (1741 s, 11 GB per lens file) are one file per lens each wanted if longer ones split
360 Photo (Burst, Interval, Night Shot, HDR) 18 MP .insp, .dng (RAW) none wanted, low
InstaPano (270°), 150° wide-angle photo 4320×1440; 1440p / 1080p ❓ none wanted, low
Audio: Wind Reduction, Stereo, 360 Direction Focus ❓ which ours used one clip of each wanted
Lens guards ❓ whether ours had them one clip with, one without wanted
IMU axes the two takes (stick swing) a clip with deliberate turns about each axis wanted

4. The inst trailer — framing ✅

hdr id type name size contents
0x0101 1 Metadata (protobuf) 1 843 §6
0x0200 2 Thumbnail 2 343 322 one H.264 keyframe, 2880×2880: the _00_ lens's first frame (Annex B, an 18-byte NAL of type 26 before the SPS). LRV: 736×368, both lenses
0x0300 3 Gyro (IMU) 8 725 080 56-byte samples, 500 Hz (§8)
0x0400 4 Exposure 124 144 16-byte samples, one per frame (§9)
0x0500 5 ThumbnailExt 2 000 058 the same, for the _10_ lens: its first frame, 2880×2880 H.264. LRV: identical to its type 2
0x0900 9 AAAData? 94 608 48-byte records, ~6.4 Hz (§10)
0x0a00 10 Anchors 35 as on the X5: 7 types, all count 0

5. Thumbnails

Types 2 and 5 are each a single H.264 IDR frame that FFmpeg decodes as a raw h264 stream ✅: the _00_ and _10_ lens's first frame at full size (X5: one stitched 1280×640 NV12 frame). The app's preview for a ONE X2 clip (since 2026-10-21) decodes both, scaled to 720², and stitches them on the CPU with the clip's calibration into a 1024×512 frame of the X5's form: ~0.27 s per clip on the sample takes, once (the media card caches it).

6. Type 1 — Metadata (protobuf) ✅

Values from _00_001; _00_003 differs only where noted.

# name (telemetry-parser) ONE X2 value notes
1 serial_number IXSE… (14 characters)
2 camera_type Insta360 ONE X2
3 fw_version v1.0.92_build1
5 / 17 offset / original_offset 16-token short calibration §7
9 file_size trailer start offset
10 total_time 309 (188) seconds
14 gyro 56 bytes the IMU sample at the first frame: its timestamp is field 24, then the 6 doubles of that type-3 sample
18 trigger_source 1 = CameraButton
19 / 44 dimension / resolution_size {2880, 2880} per-lens stream size
20 frame_rate 25
22 gamma_mode linear X5: standard / I_Log. ❓ which colour profile writes linear
24 first_frame_timestamp 4407 (4378) milliseconds on the device clock (X5: µs) (§9)
25 rolling_shutter_time 36.94 readout, ms: nearly the whole 40 ms frame (X5: 11.8–21.2)
26 file_group_info {type 6, index 0, identify ""} type 6 = VideoHdr in telemetry-parser's enum ⚠️; index 1 on the LRV
27 window_crop_info {src 3040×3040, dst 2880×2880} sensor 3040² per lens; dst = the stream size, so the focal scale dimension/dst is 1
28 gyro_timestamp −12.0 ms; negative (X5: +1.6)
29 is_has_gyro_timestamp true
31 gyro_calib 6 × f64 + u64 (−0.0034, −0.0090, +0.0090, 0.034, 0.038, −0.0053), then Unix time 1700149542 (2023-11-16; the X5 has 0 there)
36 first_gps_timestamp = field 24 not a Unix time without GPS
41 is_selfie 0
43 is_dewarp 1
45 battery_type 1
46 cam_posture 0
47 / 48 / 49 fov_type / distance / fov 3 = Ultrawide / 1.0 / 0 default reframe view
50 gyro_filter_type 2
51 gyro_type 1 = InsdevImuType40609 the same IMU part as the X5 ⚠️ (enum value only)
52 media_data_rotate_angel 1
53 / 55 offset_v2 / original_offset_v2 34 tokens §7
54 / 56 offset_v3 / original_offset_v3 40-token MEI §7
57 focus_sensor 3 = All
58 expect_output_type 0
60 photo_rot 9 floats an exact rotation matrix (orthonormal, det 1), different per clip (167° and 170° from identity). ❓ Probably the camera's orientation at the start
61 audio_mode 2 = Stereo

7. Calibration ✅

The ONE X2 carries the 40-token offset_v3 (X5 §5.3) but not the 56-token string (fields 111 / 112) the app's stitch requires. (The desk research guessed it had no offset_v3; it has.) All strings are stated in a 6080 × 3040 side-by-side frame (2 × 3040²), lens type 41.

offset_v3 (field 54), per lens xi fx fy cx cy yaw pitch roll tx ty tz k1 k2 k3 p1 p2 w h lensType (X5 §5.3), trailing flag 199680 (0x30C00):

xi fx fy cx cy yaw pitch roll tx ty tz k1 k2 k3 p1 p2
lens 0 1.72859 2322.61 2322.41 1528.43 1521.45 0.799 −0.157 178.977 0 0 0 0.2279 −0.1489 −0.9684 −0.00185 0.00116
lens 1 1.72859 2318.48 2318.72 4554.65 1542.81 −0.848 −0.368 1.421 0.00017 −0.00195 −0.0211 0.2436 −0.2279 −0.8443 0.00129 −0.00042

8. Type 3 — IMU ✅

9. Type 4 — Exposure and sync ✅

10. Type 9 ❓

11. What the app reads, and what it still needs

Read (2026-10-21):

Still needed:

12. Open questions

Answered 2026-10-21: the two files are frame-locked (§3.1); the frame's time is field 24 + field 28 (§9); the axis map is z,x,y and the gyro is in rad/s (§8).

  1. Which instant field 24 marks relative to the exposure record (5 ms apart) -- the sync doesn't need it (§9).
  2. What gamma_mode linear and file_group_info.type 6 mean for the mode set on the camera; the other modes and the lens guards are untested (§3.3).
  3. How a long recording is split into files: not by 4 GB or by 22 min (_004, §1), nor at 29 min / 11 GB (152938_…_003, §1).
  4. Type 9's layout; the AMBA box; field 60.
  5. Whether a frame is taken half its exposure before its time, as on the X5 and the A1 (X5 §7.1). The per-clip sync measurement on 45 windows of the 14 sample clips scatters by ±0.9 ms whatever the exposure (mostly 0.2-1.4 ms, its timestamps whole ms), so it doesn't tell; the app keeps one lag, field 24 + field 28 − 2.3 ms, and the per-clip fine-tune.

Sources