Don't forget that these videos were created by Coach's Eye <https://www.coachseye.com/> for iOS. I don't know anything about their internals WRT recording videos.
On Tue, Jan 5, 2016 at 2:50 PM, Matthew Adams <[email protected]> wrote: > Here is a link to zipped copies of originals placed on my dropbox > account. I zipped them in order to reduce the likelihood that they're > changed by the file hosting service. > > > https://www.dropbox.com/s/31civbxpe1utote/2016-01-02%2C%20Tour%20Warm%20Up.zip?dl=0 > > > > On Tue, Jan 5, 2016 at 2:08 PM, Moritz Barsnick <[email protected]> wrote: > >> On Tue, Jan 05, 2016 at 13:30:07 -0600, Matthew Adams wrote: >> > I pulled the files off of the iPhone using iExplorer, a nice little >> tool to >> > get at the iOS filesystem. >> >> Hmm. Something tells me this isn't the raw video as it comes from your >> device, but it was manipulated by Google (Drive) after your upload: >> >> $ sha1sum variable-bitrate-sample.mov >> 3820bb93784835f2257299008fed2fafeaacd5c5 variable-bitrate-sample.mov >> $ ffmpeg -i variable-bitrate-sample.mov >> ffmpeg version 2.6.5 Copyright (c) 2000-2015 the FFmpeg developers >> [...] >> Metadata: >> creation_time : 2016-01-03 05:53:31 >> handler_name : IsoMedia File Produced by Google, 5-11-2011 >> >> I don't think any Apple product inserts such metadata. ;-) >> >> Googl(ouch!)ing a bit, it does seem iOS creates variable frame rate >> videos. But usually, they are detected as such, or in other words, the >> headers and timestamps properly reflect that. >> >> So I think Google Drive ruined your video by doing some bad CFR magic >> to it. >> >> The video as *I* get it from your Google drive is not fixable without >> manual analysis of the timeline. Likely the original video which is (or >> has remained) on your iPhone is different. If it doesn't play fine >> there either, the video recording software fooled you, or did this >> effect on purpose due to some configuration. If it does play correctly >> on the iPhone though, you may need to find a different way to get that >> file to us. You probably wouldn't even need to fix it if Google Drive >> (your way to share the videos with others?) didn't mess it up. >> >> ffmpeg *can* convert VFR to CFR if need be (for the sake of players >> which can't handle the former). >> >> Moritz >> _______________________________________________ >> ffmpeg-user mailing list >> [email protected] >> http://ffmpeg.org/mailman/listinfo/ffmpeg-user >> > > > > -- > mailto:[email protected] <[email protected]> > skype:matthewadams12 > googletalk:[email protected] > http://matthewadams.me > http://www.linkedin.com/in/matthewadams > -- mailto:[email protected] <[email protected]> skype:matthewadams12 googletalk:[email protected] http://matthewadams.me http://www.linkedin.com/in/matthewadams _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
