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.

DJI 360 cameras file format — .osv

Desk research (2026-10-15); Avata 360 clips examined 2026-11-14 to 11-16. The desk research comes from public specs and Gyroflow's telemetry-parser (src/dji/, MIT OR Apache-2.0), which ships the protobuf schemas the cameras write. The rules in README.md on what may be taken from others' reverse engineering apply here in particular, because telemetry-parser's DJI stitching code partly cites DJI Studio's internals. Markers as in README.md: ✅ is checked on our Avata 360 clips (Modes and sample clips), all from one drone; nothing about the Osmo 360 family has met a real file yet.

Covers the DJI Osmo 360 (2025), Osmo 360 II, Osmo 360 Air and the Avata 360 drone. The app opens the Avata 360's .OSV files, experimentally (camera::DjiReader, orbiscore::DjiMeta): the facts marked ✅ below are read by that code and checked on our clip; the Osmo 360 family isn't opened as measured, only by the Avata 360's reading (logged).

1. Files and streams

1.1 Photos

The app doesn't open DJI photos yet; what the Avata 360 writes (ten November photos, exiftool):

2. Metadata track

2.1 Field map (values from the Avata 360 clip)

Field numbers are paths from ProductMeta, names are telemetry-parser's (dvtm_eagle4_wa530.proto and dvtm_library.proto). Everything listed is ✅ present on our clip; fields the schema has and the clip doesn't write are left out. Serial numbers and positions are not reproduced here.

clip_meta (1), first sample only

field name Avata 360 value notes
1.1.1 clip_meta_header.proto_file_name dvtm_AVATA360.proto not the schema to parse with (above)
1.1.2 / 1.1.3 library_proto_version / product_proto_version 02.01.20 / 02.00.11
1.1.5 product_sn 20 characters the aircraft's serial
1.1.6 product_firmware_version 01.00.06.00
1.1.9 clip_timestamp 250472750 device µs; equals the first frame's frame_timestamp
1.1.10 product_name DJI Avata360 picks the schema
1.2.1 clip_streams_meta.video_stream_num 1 although the file has two lens tracks
1.3.1 distortion_coefficients.coeffients four zeros not the lens calibration (that's §3)
1.4.1 sensor_readout_time.readout_time 12312719 ❓ units (above)
1.5, 1.6 sensor_read_direction, digital_focal_length empty
1.7.1 eis_status.status 1 EIS_ROCK_STEADY
1.8.1 imu_sampling_rate 4000 Hz; matches the quaternions per frame (§4)
1.9.1 sensor_fps.sensor_frame_rate 100.0188 the container says exactly 100
1.10.1 ITD_value −322 ❓
1.11.1 LRO_value 2443 ns per line, by the schema
1.12.1 / 1.12.2 sensor_res.sensor_width / height 3840 / 3840 = the calibration frame (§3)

stream_meta (2), first sample only

field name Avata 360 value notes
2.1.3 stream_meta_header.stream_name video
2.2.1.4 camera_stream_meta.device_header.device_name DJI FCA188 the camera module
2.2.1.5 / 2.2.1.6 device_frequency / device_timestamp 100.0 / 250472750
2.2.2.1 / 2.2.2.2 device_version.device_hw_version / device_sw_version AC Ver.03 / 10.01.08.95 the camera module's own firmware
2.2.3.1 device_sn.device_sn 14 characters the camera module's serial
2.2.4.1 color_mode.color_mode 19 COLOR_MODE_DLOG_M the colour profile (above)
2.2.5, 2.2.6 sharpness, denoise empty
2.3.1 / 2.3.2 video_stream_meta.resolution_width / height 1920 / 1920 per lens track
2.3.3 framerate 100.0
2.3.4 / 2.3.5 is_bit_depth_valid / bit_depth 1 / 10
2.3.6 bit_format 4 BIT_FORMAT_TYPE_YUV420
2.3.8 video_codec_type 1 VIDEO_CODEC_TYPE_H265
2.4 fov_type empty
2.5.1 … 2.5.24 pano_dewarp_params.* 24 DewarpParams only 2.5.3 / 2.5.4 filled (below, §3)

DewarpParams, the filled pair: native_refine_far_slave (2.5.3) and native_refine_far_master (2.5.4). Field numbers within the record.

field name slave (2.5.3) master (2.5.4) notes
1 / 2 fx / fy 1035.882 / 1036.047 1039.390 / 1039.506 px in the 3840 frame
3 / 4 cx / cy 1907.738 / 1924.519 1933.663 / 1912.346 px in the 3840 frame
5-8, 15 k1 k2 k3 k4 k5 0.09104, −0.04372, 0.02720, −0.01079, 0.00132 0.07275, −0.02460, 0.01725, −0.00826, 0.00108 θ-polynomial (§3); k6-k9 (16-19) not written
9 xi not written not written no such term in this model
10 / 11 width / height 3840 / 3840 3840 / 3840 floats
12 / 13 / 14 yaw / pitch / roll −179.117 / 90.090 / 0.254 −0.073 / 90.084 / 0.861 degrees, camera from rig (§3)
20 p 0.00005, 0.00054 0.00022, −0.00184 the tangential pair p1, p2: needed for the seam (§3)
21 q four zeros four zeros
22 / 23 occlusion_pt_x / _y zeros zeros
24 lens_model 8 8 a float; ❓ the code for this model
25 temperature 23.0 23.0 °C at calibration
26 cam_imu_extri_q (w x y z) 0.0073, −0.0006, −0.0021, −1.0000 0.9999, −0.0075, 0.0024, 0.0111 camera to IMU (§4)
27 tangent_coeff 0, 0 0, 0 not the tangential pair: that's field 20
28 cam_extri_q not written not written the pose is only in 12-14
29 / 30 cam_imu_cali_enable / temp_compen_enable 1 / 1 1 / 1
31 temp_compen_k 6.65e-5 6.65e-5 ❓ by the name, focal change per °C: ~0.04 % at the clip's 29 °C
32 / 33 gimbal_yaw_h1 / _h2 48 / 49 48 / 49 ❓

The native_refine pair (2.5.1 / 2.5.2) holds only temperature (23.0); the other 20 records hold nothing but zeros.

frame_meta (3), every sample

field name Avata 360 value notes
3.1.1 frame_meta_header.frame_seq_num 0, 1, 2 … not written on the first sample (0)
3.1.2 frame_timestamp 250472750, +10000 per frame device µs
3.2.1 camera_frame_meta.camera_dev_header as 2.2.1
3.2.3.1 iso.iso 200.0
3.2.4.1 exposure_time.exposure_time [1, 3252] seconds as a fraction; the .SRT rounds it to 1/3200
3.2.5.1 digital_zoom_ratio 1.0
3.2.6.1 white_balance_cct 5429 K
3.2.8.1 exposure_value 0.15625 EV
3.2.9.1 color_temp_atmosphere 5415 K
3.2.10.1 focal_length [2340, 1000] 2.34 mm
3.2.11.1 absolute_altitude.absolute_altitude_m the take-off altitude m
3.2.12.1 sensor_temperature 29.0 / 28.0 °C; differs between the two djmd tracks
3.2.13.1 / 3.2.13.2 sensor_active_size 4596 / 4596 µm
3.2.14.1 f_number [18, 10] f/1.8; the .SRT says 1.9
3.2.16.1-4 sensor_shift_param.sensor_shift_arr* four packed uint32 arrays ❓ EIS data
3.2.18.1 / .2 / .4 liveview_hfov 1.8151 / 1.8151 / 1.7778 rad (104°) and 16:9: the live view, not the recording
3.2.19 not in the schema 64 bytes, nested ❓
3.3.2.1.1 IMU_attitude_after_fusion.current_frame.timestamp the frame's stamp − 370…400 device µs (§4)
3.3.2.1.2 current_frame.vsync 10428 + frame
3.3.2.1.3 current_frame.attitude (w x y z) 39-41 quaternions 4 kHz (§4)
3.3.2.2 IMU_attitude_after_fusion.prev_frame the previous frame's batch first sample only
3.3.3.1 IMU_vsync_pos.vsync_pos 3, 5 … the IMU's downsampling phase, by the schema
3.4.1.5 drone_frame_meta.drone_dev_header.device_frequency 10.0 the drone part changes at 10 Hz
3.4.2.1 / 3.4.2.2 velocity.velocity_x / _y −0.6 / −1.8 m/s, NED
3.4.3.1-3 attitude.pitch_decidegree / roll_ / yaw_ −5 / 19 / 1781 0.1°, NED
3.4.4.1.2 / .3 gps.gps_coordinates.latitude / longitude the position degrees, doubles
3.4.4.2 / 3.4.4.4 gps_altitude_mm / gps_altitude_type the altitude / 1 GPS_FUSION_ALTITUDE
3.4.5.1 / 3.4.5.2 relative_altitude.relative_altitude_mm / is_relative_altitude_valid 2200.0 / 1 above take-off
3.4.7.1 rc_mode.rc_mode 7 DJI_COMMAND_MODE_GPS_NORMAL
3.4.8.1 / 3.4.8.2 barr_dist.below_tof_state / below_dist_cm 1 TOF_STATE_REFLECTED / 23
3.4.9.1 fai_degree.fai_g_deg −503 0.1°, ❓
3.4.11.2 gimbal_angle_deviation.y_deviation 0.00035 ❓
3.4.13 tracking_info on some frames the subject the drone follows
3.4.14 not in the schema 58 bytes ❓

3. Lens calibration

3.1 The mount (ours)

3.2 The body in the pictures (ours)

4. IMU

Modes and sample clips

All the modes the Avata 360 offers 📖 (DJI's spec page, and its firmware notes for what came later, §6), with the clips we have and whether that is enough. Enough means the file is examined here and what the app reads per mode (lens size, calibration, attitude, readout) is checked on it; one clip means examined, but a second take would check what one clip can't (a moving camera for stabilization, the other colour); wanted means no clip yet.

All our files come from one Avata 360, a contributor's, each take with its .LRF and (but for one) its .SRT; every video is 10-bit HEVC. Short names in this document (0008, 0010) are the October clips; the November ones are written 1115_NNNN. The spec gives the rates as 60 / 30 / 24, which the files write as 59.94 / 29.97 / 23.976 (only 100 is exact); the names below are the spec's, the sizes per lens track.

Mode Spec Files Our clips Status
360 Video 8K (3840² per lens) 60 / 50 / 48 / 30 / 25 / 24 DJI_…_D_….OSV + .LRF + .SRT at 60: Normal 1115_0008; D-Log M 1115_0009, 0010, 0017-0020, near the ground and in flight. At 30 and 24: one Normal clip each (1115_0007, 0006); fw 01.00.08 enough at 60; one clip at 30 / 24; 50 / 48 / 25 wanted (do they write exact rates, and the same readout?)
360 Video 6K (3000² per lens) 60 / 50 / 48 / 30 / 25 / 24 as above at 60: Normal 1115_0004, D-Log M 1115_0005. At 30 and 24: one Normal clip each (1115_0003, 0002); fw 01.00.08 enough at 60 (the 0.78125 scale, §3); one clip at 30 / 24; 50 / 48 / 25 wanted
360 Video 4K (1920² per lens) 100 (added by firmware 01.00.03, 2026-06-23; not on the spec page) as above D-Log M: six October flights, 30 s to 3:40, fw 01.00.06 / .08; Normal: 1115_0001, 10 s enough
Colour: Normal, D-Log M color_mode 0 / 19 (§2) both, at 100 and at 60 in 8K and 6K enough; D-Log M at 30 / 24 not seen (a check, low)
QuickShots, FocusTrack (360 mode) 📖 by remote controller ❓ presumably a normal .OSV FocusTrack: the October subject-following clips (tracking_info, §2.1) FocusTrack enough; a QuickShot wanted (low: its file, any marker in djmd)
Single-lens Video 4K 3840×2160 at 60…24; 3840×2880 (4:3) at 60…24, only with the goggles and a motion / FPV controller ❓ .MP4 (§1) none wanted: a flat video, but does it carry djmd, which FOV (Natural Wide, Standard (Dewarp), Wide) and stabilization (RockSteady, HorizonBalancing) it was taken with
Single-lens Video 2.7K 2688×1512 and 2688×2016 (4:3) at 120 / 100 / 60…24 as above none wanted (low once one single-lens clip is in)
360 Photo 120 MP JPEG 15520×7760, DNG DJI_…_D_….JPG (stitched, §1.1) + _UP / _DOWN .DNG at 7680² seven, each with its DNG pair, at 12-122 m above take-off enough to start photo support
360 Photo 30 MP JPEG 7776×3888, DNG as above, DNG at 3840² two: one with its DNG pair, one JPEG only enough
Single-lens Photo (added by firmware 01.00.03, 2026-06-23; no size stated) .JPG, flat ❓ 1115_0011, 4000×3000, 2.3 mm (28 mm equivalent), no panorama tags: by its size a single-lens photo one; a single-lens DNG wanted (low)
Internal storage (42 GB) or microSD ❓ the same files ❓ which ours came from wanted, low: whether the internal storage writes the same names and fsid path

The spec page lists only Single Shot among the photo modes. Our photos carry XPKeywords single or smart (smart on six of ten, the 4000×3000 one among them; either kind comes with or without DNGs); ❓ what smart stands for. Each photo's SensorFPS is one of the video rates (23.97, 47.95, 59.94, 25), as if the sensor ran in the video mode last set.

The file names no mode beyond its size and rate (no capture-mode name in the metadata); the app names the mode by the lens size, with DJI's names (3840² 8K, 3000² 6K, 1920² 4K).

Wanted beyond the table: clips from a second Avata 360 (for the IMU's turn, §4, and the camera's tilt, §3.1), and anything from the Osmo 360 family.

5. Open questions

  1. The same lens reading and mount on a second Avata 360 (every mode of our drone stitches with it, §3); the camera's tilt against the body (§3.1).
  2. Whether the IMU sits turned against the sphere about the forward axis: the rotation fit says 1.6°, the level picture under a degree (§4); a second Avata 360 would help. What frame cam_imu_extri_q is written in: it doesn't agree with the lens poses (§4), so it can't give the lens-to-body turn until that's known. The other modes of the same drone write the same quaternions, so only a second unit can show whether it follows the picture.
  3. Everything above on the Osmo 360 family: tracks, sizes, codec, the schema per product, the calibration slots and the raw IMU.
  4. D-Log M's transfer curve.
  5. Which calibration slot stitches best, per accessory, where a body fills more than one (measured on our footage).
  6. Whether another product or firmware fills occlusion_pt_x/y, and in what terms: it would give the body's outline (§3.2) from the file.

6. Sources