Hello,
I can see that you are kindly supporting Insta360 video format .insv
I think it would be great if you can support their picture format as well .insp
Thank you very much
L
Could you send me a sample? philharvey66 at gmail.com
- Phil
I got the sample, thanks. (Wow, that took a long time!)
I will add INSP to the list of recognized file extensions.
This is a JPEG-format file with an additional trailer. The trailer contains 3 sections:
1. A table of floating point values, probably accelerometer readings:
22503 0 0.148193 -0.966797 -0.0844727 0.00639159 0.00745685 -0.0255663
22505 0 0.145264 -0.966553 -0.0852051 0.00639159 0.00639159 -0.0234358
22507 0 0.142822 -0.967773 -0.0837402 0.00426106 0.00745685 -0.0213053
22509 0 0.144043 -0.964844 -0.0820312 0.00426106 0.00639159 -0.0213053
22511 0 0.14209 -0.966064 -0.083252 0.00426106 0.00639159 -0.0213053
22513 0 0.142334 -0.969727 -0.0869141 0.00426106 0.00639159 -0.0213053
22515 0 0.142334 -0.968262 -0.0866699 0.00639159 0.00745685 -0.0223706
22517 0 0.140137 -0.967773 -0.0825195 0.00852212 0.00852212 -0.0223706
22519 0 0.143555 -0.967285 -0.0830078 0.00852212 0.00958738 -0.02024
22522 0 0.145508 -0.968994 -0.0739746 0.00852212 0.00852212 -0.0213053
22524 0 0.143066 -0.970703 -0.0732422 0.00852212 0.00852212 -0.0213053
22526 0 0.143311 -0.971436 -0.0773926 0.00852212 0.00852212 -0.0223706
22528 0 0.14209 -0.970703 -0.0786133 0.00852212 0.00852212 -0.0223706
22530 0 0.140381 -0.970215 -0.0810547 0.0106526 0.00852212 -0.0223706
22532 0 0.142578 -0.966553 -0.0805664 0.0106526 0.00958738 -0.0223706
22534 0 0.14209 -0.966797 -0.078125 0.0127832 0.00958738 -0.0223706
22536 0 0.141357 -0.966553 -0.0800781 0.0127832 0.00852212 -0.0213053
22538 0 0.143799 -0.968994 -0.0839844 0.0149137 0.00745685 -0.0213053
22540 0 0.143311 -0.966797 -0.0834961 0.0170442 0.00639159 -0.02024
22542 0 0.142334 -0.966309 -0.0856934 0.0149137 0.00639159 -0.02024
22544 0 0.144287 -0.965332 -0.0859375 0.0170442 0.00639159 -0.02024
22546 0 0.142578 -0.964111 -0.0844727 0.0170442 0.00639159 -0.0213053
22548 0 0.144775 -0.96167 -0.0842285 0.0170442 0.00532632 -0.02024
22550 0 0.144287 -0.962646 -0.0837402 0.0170442 0.00532632 -0.0181095
22552 0 0.142578 -0.96167 -0.0830078 0.0149137 0.00532632 -0.0181095
22554 0 0.143311 -0.95752 -0.0808105 0.0127832 0.00745685 -0.0191748
22556 0 0.144287 -0.956543 -0.0830078 0.0127832 0.00745685 -0.02024
22558 0 0.144287 -0.960693 -0.0830078 0.0106526 0.00639159 -0.0191748
22560 0 0.144043 -0.958008 -0.083252 0.00852212 0.00639159 -0.0170442
22562 0 0.141846 -0.960449 -0.0827637 0.00639159 0.00639159 -0.015979
22564 0 0.142822 -0.962158 -0.0847168 0.00639159 0.00532632 -0.0170442
22566 0 0.142334 -0.959229 -0.0805664 0.00639159 0.00532632 -0.0170442
22568 0 0.141113 -0.958008 -0.0808105 0.00639159 0.00745685 -0.0170442
22570 0 0.141846 -0.960449 -0.0822754 0.00639159 0.00745685 -0.015979
22572 0 0.142822 -0.95874 -0.0808105 0.00639159 0.00745685 -0.015979
...
2. A 1920x960 JPEG preview
3. A 394-byte trailer record, possibly ending in a 32-byte UUID (although I only have one sample, so I can't tell if the UUID can be used as an identifier):
34242: 00 02 54 a2 02 00 0a 0e 49 58 45 32 31 31 39 4e [..T.....IXE2119N]
34252: 4b 33 35 47 43 45 12 0d 49 6e 73 74 61 33 36 30 [K35GCE..Insta360]
34262: 20 4f 6e 65 32 1a 0f 76 31 2e 31 38 2e 32 37 5f [ One2..v1.18.27_]
34272: 62 75 69 6c 64 31 2a 6e 32 5f 31 34 38 30 2e 37 [build1*n2_1480.7]
34282: 36 35 5f 31 35 31 39 2e 31 38 34 5f 31 35 32 33 [65_1519.184_1523]
34292: 2e 39 36 32 5f 30 2e 30 30 30 5f 30 2e 30 30 30 [.962_0.000_0.000]
342a2: 5f 30 2e 30 30 30 5f 31 34 37 38 2e 30 34 33 5f [_0.000_1478.043_]
342b2: 34 35 35 34 2e 38 37 36 5f 31 35 31 33 2e 37 34 [4554.876_1513.74]
342c2: 37 5f 2d 30 2e 30 37 39 5f 2d 30 2e 31 36 30 5f [7_-0.079_-0.160_]
342d2: 31 37 39 2e 38 37 32 5f 36 30 38 30 5f 33 30 34 [179.872_6080_304]
342e2: 30 5f 32 33 32 33 48 dd e8 68 50 00 90 01 01 9a [0_2323H..hP.....]
342f2: 01 06 08 c0 2f 10 e0 17 c0 01 fd b6 01 c9 01 00 [..../...........]
34302: 00 00 40 1d 84 37 40 d2 01 34 08 05 10 01 1a 2e [..@..7@..4......]
34312: 2f 44 43 49 4d 2f 43 61 6d 65 72 61 30 33 2f 49 [/DCIM/Camera03/I]
34322: 4d 47 5f 32 30 31 38 30 31 30 31 5f 30 30 34 38 [MG_20180101_0048]
34332: 30 34 5f 30 30 5f 34 31 34 2e 69 6e 73 70 fa 01 [04_00_414.insp..]
34342: 38 00 00 00 00 00 40 95 3f 00 00 00 00 00 80 95 [8.....@.?.......]
34352: bf 00 00 00 00 00 80 92 bf 85 ad 84 fa 0a 74 81 [..............t.]
34362: bf 5d f8 2c aa 4b 8b 92 bf 47 04 c7 77 10 2e 6a [.].,.K...G..w..j]
34372: 3f d6 8c f8 5c 00 00 00 00 a0 02 00 01 01 36 01 [?...\.........6.]
34382: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [................]
34392: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [................]
343a2: 00 00 cc 43 03 00 03 00 00 00 38 64 62 34 32 64 [...C......8db42d]
343b2: 36 39 34 63 63 63 34 31 38 37 39 30 65 64 66 66 [694ccc418790edff]
343c2: 34 33 39 66 65 30 32 36 62 66 [439fe026bf]
Unless there is interest, I won't decode information from this trailer for now. To do this, I would need a few more samples.
- Phil
Edit: It seems the trailer may be similar to the one used in INSV files, in which case it would be easier to decode. I'll look into this.
Edit2: ExifTool 11.85 (to be released in a couple of weeks) will decode this trailer.
Hello.
I have .insp files from insta360 x3 camera. Is it supported? All gps tags have zero coordinate (with --ee -G3 keys), but it correctly placed at Google Maps.
Also when .insp converted to .jpg by "Insta360 Studio 2023" app, photos have gps coordinates, but all of them the same.
If you are interested, here is the source file and the jpg file
https://drive.google.com/drive/folders/1BuZ6-X-vri1GnlLbbro8DZD63r6BDA9l?usp=sharing
I don't understand why you say "All gps tags have zero coordinate", because I get this:
> exiftool IMG_20230117_143103_00_315.insp -ee "-gps*"
GPS Version ID : 2.2.0.0
GPS Latitude Ref : North
GPS Latitude : 51.782302
GPS Longitude Ref : East
GPS Longitude : 55.119853
GPS Altitude Ref : Above Sea Level
GPS Altitude : 18.71294062 m
GPS Altitude : 18.7 m Above Sea Level
GPS Latitude : 51.782302 N
GPS Longitude : 55.119853 E
GPS Position : 51.782302 N, 55.119853 E
So no timed GPS, but ExifTool does extract other timed metadata from this file (accelerometers).
I don't see the Insta360 timed GPS record (0x700) in this file. There are two records (0x900 and 0xb00) that ExifTool isn't yet decoding, but they don't look like GPS to me. So I can't find any timed GPS in this file.
What is the file VID_20230117_142150_00_312.mp4 you uploaded? I don't see timed GPS in this either.
- Phil
Quote from: Phil Harvey on January 19, 2023, 08:27:39 AMI don't understand why you say "All gps tags have zero coordinate", because I get this:
Sorry, my bad. As it turned out 95% of my .insp files have 0 00 00 coordinates. And I accidentally sent the one where the coordinates are.) I think it's about the connection between the camera and the smartphone.
Quote from: Phil Harvey on January 19, 2023, 08:27:39 AMWhat is the file VID_20230117_142150_00_312.mp4 you uploaded? I don't see timed GPS in this either.
I accidentally sent the converted video. I replaced it with the original.