Ok. Problem solved. Steve, your command served as the best basis. Moritz, your investigation of the Google Photos magic also clarified things for me. In the end, I used the following:
ffmpeg -i $INMOV -c:a copy -c:v libx264 -vf fps=fps=60 -crf 15 -preset slow $OUTMP4 Thanks for all of your help. Since you both took time & helped, is it ok if I send you $15 each? I can send via PayPal, Venmo, or Square Cash to the email addresses your subscribed to this list with. Just respond on this thread with your preferred payment service. -matthew On Wed, Jan 6, 2016 at 3:04 AM, Moritz Barsnick <[email protected]> wrote: > On Tue, Jan 05, 2016 at 22:50:18 -0600, Steve Boyer wrote: > > Matthew, > > One quick sanity-check -- are you running the commands on > > "variable-bitrate-sample.mov" or on the raw > > "Jan22016-150PM-b6cs7K.mov"? > > To be more clear: The variable-bitrate-sample.mov, as found on Google > Drive, is unfixable with a simple ffmpeg command. The files > Jan22016-15*.mov, as delivered in the zip, must be used as input, in > order to not have slow-motion effects. > > > > PS: FWIW, with a 10.7 Mb original video, Steve's command resulted in a > 13.7 > > > Mb video, Moritz's, 9.3 Mb. > > In really simple terms: Use "-crf" to vary the quality of the > re-encoded video (a crf of 23 is default, lower is better, play with it > to see what is okay for you), at the cost of conversion speed and size. > Use presets to trade conversion speed for file size, while maintaining > the selected quality. > > 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 _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
