Adjust gps track time with gpsbabel1/8/2024 There is, but currently not in plain sight for us.Īnd you are right, that gyro data starts before the actual first frame of the video is saved. And I do join you, other Phil, in thanking Phil Harvey for this incredible tool! I'd be curious to understand Phil Harvey's approach on how he was able to decode this data from scratch. It could be hidden in some of the documents that exiftool can't decode yet: 0x200, 0x400, 0x900 or 0xa00. I am convinced there must be a way to map this side data to the video store somewhere in the file but I can't find where. While the metadata are timestamped with uptime, the video/audio tracks are not and they start at timestamp 0 as you were saying so we can't sync them. Looking at the data, we seem to have a longer track of gyroscope/exposure data than video itself (1-2s more of gyroscope data than video). When opening insta360 Studio, it seems to be able to sync the video and gyroscope data right away despite the offset varying in the multiple the sample videos I looked at. I have been looking at the gyroscope data to provide a different way to stabilize the video other than insta360 own flowstate. Unfortunately due to the way the data is acquired and saved you will face a delay. Guess you already connected the video tracks time code zero with the first accelerator time code. You have to assume that the first appearance of an accelerator time code is at / near the starting point of the video. You wont find an anchor point in the video data to hook up. That time code, as well as the timecode for exposure data, is uptime based. Does anyone know what that timecode is relative to? The video track timecode does start at zero, and I cannot find any tag that resembles that value, to use as a base offset I have tried assuming the first samples correspond to the first frame, but there seems to be a slight offset (the data seems a bit delayed, so maybe some data samples before the first video frame are retained). The timecode is in seconds but it does not start at zero. Those are a kind of helper data for the stitcher, calibration / lens related data. The only tag that I can imagine having that sort of data would be So the usage would be, the greater the number of doubles in the 10 data points /s, the greater the DUP value would be. Those only specify how reliable the data is. There are tags for "Dilution Of Precision" ( (navigation) ) for every data point => īut that's not what you have in mind. There is an element for "extensions" where you could place some own format. That's nothing I would see ExifTool in charge.Ĭoming to "gps accuracy", GPX does not provide a tag for that kind of "accuracy". The best way to deal with it is to use additional tools to to even out the data / to optimize the data to an average. Unfortunately for most mobile devices you have to live with having doubled data points in the 10/s. I've done some tests with different devices => But that strongly depends on the device used to get the data and its GPS lock / signal quality. All three cameras can add GPS data at 10Hz which includes to have 10 different GPS coords per second. The data quality in the insv file of an OneX/R/X2 depends on the GPS signal quality provided by phone / GPS smart remote / Apple or Garmin watch. The file I send you last time is recoreded by mobile phone, and yesterday I bought a remote controller, I find that the data is changing in one second, so you may still promote the time accuracy and gps accuracy(to 0.001''). Hi Phil, the insta360 One X support record GPS from mobile phone, or from a remote controller. Quote from: zengcancan on December 08, 2020, 08:33:32 PM Especially in terms of extracting insta360 data.īecause of that, maybe I can add some additional information. Quote from: Phil_K on January 15, 2021, 03:48:23 AMįirst of all, I would like to express my thanks to Phil Harvey for this great tool.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |