Re: [FFmpeg-devel] [PATCH v6] lavf/matroskadec: A_QUICKTIME and fourcc 0x00000000

2016-01-08 Thread Mats Peterson
On 01/08/2016 03:07 PM, Moritz Barsnick wrote: On Fri, Jan 08, 2016 at 14:51:53 +0100, Mats Peterson wrote: I can't see the applied patches at GitHub yet. Is a delay normal? Sorry for a stupid question. Yes, that is normal. videolan.org hosts the "original". There was an explanation in this t

Re: [FFmpeg-devel] [PATCH v6] lavf/matroskadec: A_QUICKTIME and fourcc 0x00000000

2016-01-08 Thread Moritz Barsnick
On Fri, Jan 08, 2016 at 14:51:53 +0100, Mats Peterson wrote: > I can't see the applied patches at GitHub yet. Is a delay normal? Sorry > for a stupid question. Yes, that is normal. videolan.org hosts the "original". There was an explanation in this thread: http://lists.ffmpeg.org/pipermail/ffmpe

Re: [FFmpeg-devel] [PATCH v6] lavf/matroskadec: A_QUICKTIME and fourcc 0x00000000

2016-01-08 Thread Mats Peterson
On 01/08/2016 02:12 PM, Michael Niedermayer wrote: On Fri, Jan 08, 2016 at 01:03:05PM +0100, Mats Peterson wrote: In many older QuickTime files, the audio format, or "fourcc", is 0x. The QuickTime File Format Specification states the following regarding this situation: "This format desc

Re: [FFmpeg-devel] [PATCH v6] lavf/matroskadec: A_QUICKTIME and fourcc 0x00000000

2016-01-08 Thread Michael Niedermayer
On Fri, Jan 08, 2016 at 01:03:05PM +0100, Mats Peterson wrote: > In many older QuickTime files, the audio format, or "fourcc", is > 0x. The QuickTime File Format Specification states the following > regarding this situation: > > "This format descriptor should not be used, but may be found

[FFmpeg-devel] [PATCH v6] lavf/matroskadec: A_QUICKTIME and fourcc 0x00000000

2016-01-08 Thread Mats Peterson
In many older QuickTime files, the audio format, or "fourcc", is 0x. The QuickTime File Format Specification states the following regarding this situation: "This format descriptor should not be used, but may be found in some files. Samples are assumed to be stored in either 'raw ' or 'two