You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wanted to update on this issue. The way that this can be fixed is:
// how to convert timestamp to millisecond epochconsttimestamp2ms=t=>parseInt(t.split('-'))// get the timestamps for the main camera and another stream// using the main camera as the time reference for the progress barconstmainStartTime=timestamp2ms(recordingData.streams.main['first-entry-id'])constgllStartTime=timestamp2ms(recordingData.streams.gll['first-entry-id'])// then when you want the exact gll time,// you can calculate the exact time offset like this and add it to the time in secondsconstgllCurrentTime=Math.max(0,mainCurrentTime+(mainStartTime-gllStartTime)/1000)
If you have the progress bar feed the absolute timestamp (add mainStartTime to the current time in seconds) and then provide each video player with their stream's start time, then you can just do the math when seeking
Looks at the
coffee-test-2
, as an example. The audio length is 7:19 min. However, the video length is 7:20 minThe text was updated successfully, but these errors were encountered: