Ask a Question
GoPro Support Hub Ask a question. Share an answer. Find a solution. Stay stoked.
Announcements
Is your GoPro gear up to date? Check to see If it is on our Update page.
Cameras
%3CLINGO-SUB%20id%3D%22lingo-sub-55489%22%20slang%3D%22en-US%22%3EGoPro%20timestamp%20sync%20(milliseconds)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55489%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20your%20help%20with%20a%20data%20sync%20problem...%20I%20m%20currently%20trying%20to%20sync%20my%20video%20%26nbsp%3Bwith%20real%20world%20%26nbsp%3Btime%20(a.k.a%20my%20notebook).%20%26nbsp%3BI%20manage%20to%20sync%20date%20and%20time%20of%20my%20notebook%20and%20my%20GoPro%203%2B%20black%20%26nbsp%3Bperfetcly.%20The%20problem%20is%20that%20when%20the%20GoPro%20save%20the%20files%20in%20disk%20it%20round%20up%20the%20miliseconds%20on%20the%20creation_time%20(the%20milliseconds%20is%20always%20000000)%20.%20Thus%2C%20turning%20the%20perfect%20sync%20impossible.%20In%20attachmente%20is%20a%20picture%20of%20the%20metainformation%20(extracted%20by%20ffprobe)%20%26nbsp%3Bof%20the%20MP4%20video.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%3A%20%26nbsp%3BWhat%20I%20have%20to%20do%2C%20so%20the%20GoPro%20actually%20save%20the%20creation_time%20with%20precision%20of%20miliseconds.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20small%20question%3A%20Looking%20at%20the%20attachment%20figure%2C%20we%20see%20the%20%22timecode%22%20wich%20is%20a%20time%20syncronization%20data%20in%20the%20format%20of%20%26nbsp%3Bhours%3Aminuts%3Aseconds%3Aframe.%20%26nbsp%3BI%20was%20think%20that%20I%20could%20use%20the%20%22frame%22%20value%20to%20calculate%20the%20missing%20milisecond%20values.%20%26nbsp%3B%20If%20we%20take%20this%20attachment%2C%20as%20a%20example%2C%20we%20can%20see%20that%20the%20frames%20value%20is%20%26nbsp%3B%2236%22.%20%26nbsp%3BMeaning%20that%20the%20milisecond%20that%20it%20started%20to%20record%20was%20the%20one%20associated%20with%20the%2036th%20frame%20of%20the%20FPS%3CSPAN%3E%26nbsp%3B(in%20this%20video%20%3A%2060fps)%3C%2FSPAN%3E%26nbsp%3Bvalue%3A%20%26nbsp%3BSome%20thing%20like%201000%2F60%20*%2036%20%26nbsp%3Bwhich%20is%20600%20miliseconds%2C%20thus%20the%20actual%20creation_time%20of%20this%20video%20would%20be%20%3A%26nbsp%3B%3CSTRONG%3E2017-07-19T18%3A10%3A34.600%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20logic%20right%3F%20it%20didn't%20work%20!%20%26nbsp%3BI%20don't%20know%20what%20else%20to%20do.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EP.S%3A%20%26nbsp%3BI%20need%20this%20kind%20of%20time%20precision%20because%20I%20will%20sync%20the%20video%20frames%20with%20a%20external%20sensor%20data%20that%20is%20recorded%20at%2011hz%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20Help%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-55489%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHERO3%2B%20Black%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHERO5%20Black%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94995%22%20slang%3D%22en-US%22%3ERe%3A%20GoPro%20timestamp%20sync%20(milliseconds)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94995%22%20slang%3D%22en-US%22%3EHi%20guys%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20facing%20the%20same%20problem%2C%20were%20you%20able%20to%20solve%20it%3F%3C%2FLINGO-BODY%3E
Reply
Highlighted
Tourist
Posts: 2

GoPro timestamp sync (milliseconds)

Hi Guys,

 

I need your help with a data sync problem... I m currently trying to sync my video  with real world  time (a.k.a my notebook).  I manage to sync date and time of my notebook and my GoPro 3+ black  perfetcly. The problem is that when the GoPro save the files in disk it round up the miliseconds on the creation_time (the milliseconds is always 000000) . Thus, turning the perfect sync impossible. In attachmente is a picture of the metainformation (extracted by ffprobe)  of the MP4 video.

 

My question is:  What I have to do, so the GoPro actually save the creation_time with precision of miliseconds.

 

 

Another small question: Looking at the attachment figure, we see the "timecode" wich is a time syncronization data in the format of  hours:minuts:seconds:frame.  I was think that I could use the "frame" value to calculate the missing milisecond values.   If we take this attachment, as a example, we can see that the frames value is  "36".  Meaning that the milisecond that it started to record was the one associated with the 36th frame of the FPS (in this video : 60fps) value:  Some thing like 1000/60 * 36  which is 600 miliseconds, thus the actual creation_time of this video would be : 2017-07-19T18:10:34.600

 

Is this logic right? it didn't work !  I don't know what else to do.

 

P.S:  I need this kind of time precision because I will sync the video frames with a external sensor data that is recorded at 11hz 

 

Please Help 

Screen Shot 2017-07-20 at 12.59.54 AM.png
Sightseer
Posts: 1

Re: GoPro timestamp sync (milliseconds)

Hi guys,

I am facing the same problem, were you able to solve it?