[FFmpeg-user] Need help; willing to pay

[Matthew Adams]

Andy,

The changes were not due to Google Drive.  They were due to Google Photos.
If you allow Google Photos to store photos & vidoes at their prescribed
fidelity (whatever that is), they'll let you store an unlimited amount of
photos.  If you want to store them unchanged, then they count against your
Google Drive quota.  With video, that can add up quick.

The videos I originally copied over to Google Drive were from Google Photos
with their unlimited-storage processing, which obviously didn't turn out so
well with these videos.  The ones in the zip file are the originals and
those converted perfectly thanks to Steve & Moritz.  I have all of the
originals locally at home (and they're backed up with Backblaze - highly
recommended by me), so after I process all of the videos at home, Google
Photos will pick them up, then we'll see what Google Photos does with them.

-matthew

-matthew

On Wed, Jan 6, 2016 at 5:01 AM, Andy Furniss <adf.lists at gmail.com> wrote:

> Moritz Barsnick 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.
>>
>
> That's just plain out of order. Though as someone who puts samples on
> free drive and hasn't noticed I just did a test.
>
> Copied/renamed Jan22016-150PM-b6cs7K.mov to gtest.mov and uploaded with
> browser.
>
>
> https://drive.google.com/file/d/0BxP5-S1t9VEEd2FacGVJMmdmaHc/view?usp=sharing
>
> At time of writing I am downloading exactly the same file.
>
> I'll keep an eye on it to see if it changes!
>
> I wonder if there is some setting/upload app involved here.
>
>
>
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>



-- 
mailto:matthew at matthewadams.me <matthew at matthewadams.me>
skype:matthewadams12
googletalk:matthew at matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams