Thanks! Looking at that file, I notice the stsc refers to some unknown chunks (stsco has no chunk offsets), but this is a non-issue since stts has no samples. Next patch will detect this condition and simply clear out stsc structures since they're not needed and contradict stco.
On Wed, Feb 6, 2019 at 7:57 AM Michael Niedermayer <mich...@niedermayer.cc> wrote: > On Mon, Feb 04, 2019 at 04:30:29PM -0800, chcunningham wrote: > > Bad content may contain stsc boxes with a first_chunk index that > > exceeds stco.entries (chunk_count). This ammends the existing check to > > include cases where chunk_count == 0. > > --- > > libavformat/mov.c | 7 +++++-- > > 1 file changed, 5 insertions(+), 2 deletions(-) > > This seems to break GF9720Repeal20the20Eighth20with20Helen20Linehan.m4a > Thats a sample from chromium issue 822666 > > thx > > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Many things microsoft did are stupid, but not doing something just because > microsoft did it is even more stupid. If everything ms did were stupid they > would be bankrupt already. > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
