development discussions and patches
> > Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> >
> > fails on mingw64 + wine
> >
> > make fate-mov-faststart-4gb-overflow V=2
> > --- - 2018-06-12 23:23:10.487549933 +0200
> > +++ tests/data/fate/mov-
development discussions and patches
> > Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> >
> >
> > this is not mandatory but trying with some basic fuzzer seems like a good
> > idea look at the examples in the manpage of zzuf for example, its very easy
> >
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Wednesday, June 13, 2018 12:26 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] qt-faststart bug n
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Wednesday, June 13, 2018 1:41 AM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] qt-faststart bug near 4G
; > > Behalf Of Michael Niedermayer
> > > > Sent: Saturday, June 9, 2018 9:17 PM
> > > > To: FFmpeg development discussions and patches
> > > >
> > > > Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> > > >
> > > &
; > > Behalf Of Michael Niedermayer
> > > > Sent: Saturday, June 9, 2018 9:17 PM
> > > > To: FFmpeg development discussions and patches
> > > >
> > > > Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> > > >
> > > &
PM
> > > To: FFmpeg development discussions and patches
> > >
> > > Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> > >
> > > > +
> > > > +if (atom.size < atom.header_size) {
> > >
> > > > +
development discussions and patches
> > Subject: Re: [FFmpeg-devel] qt-faststart bug near 4GB
> >
> > > +
> > > +if (atom.size < atom.header_size) {
> >
> > > +printf("atom size %"PRIu64" too small\n", atom.siz
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Saturday, June 9, 2018 9:17 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] qt-f
> > Behalf Of Eran Kornblau
> > > > Sent: Friday, May 25, 2018 4:40 PM
> > > > To: FFmpeg development discussions and patches
> > > >
> > > > Subject: [FFmpeg-devel] qt-faststart bug near 4GB
> > > >
> > > > Hi all,
>
Ping
-Original Message-
From: Eran Kornblau
Sent: Friday, June 1, 2018 10:00 AM
To: FFmpeg development discussions and patches
Subject: RE: [FFmpeg-devel] qt-faststart bug near 4GB
> On Thu, May 31, 2018 at 10:11:38AM +, Eran Kornblau wrote:
> > >
> > >
> > To: FFmpeg development discussions and patches
> > >
> > > Subject: [FFmpeg-devel] qt-faststart bug near 4GB
> > >
> > > Hi all,
> > >
> > > We encountered a rather extreme edge case with qt-faststart - we
> > > transcod
discussions and patches
> > Subject: [FFmpeg-devel] qt-faststart bug near 4GB
> >
> > Hi all,
> >
> > We encountered a rather extreme edge case with qt-faststart - we transcoded
> > some video with ffmpeg, and the offset of the last video frame in the
>
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Eran
> Kornblau
> Sent: Friday, May 25, 2018 4:40 PM
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] qt-faststart bug near 4GB
>
> Hi
Hi all,
We encountered a rather extreme edge case with qt-faststart - we transcoded
some video with ffmpeg,
and the offset of the last video frame in the resulting mp4 was slightly less
than 4GB.
Since it was less than 4GB, ffmpeg used an 'stco' atom and not a 'co64' atom.
When we ran qt-faststa
15 matches
Mail list logo
