[FFmpeg-devel] [PATCH] lavc: remove imx_dump_header bitstream filter

Gaullier Nicolas nicolas.gaullier at arkena.com
Wed Jun 11 10:23:52 CEST 2014

No, I am sorry, I do not know what FCP version or any other software do actually strictly require this header for proper reading, I only know that files are still produced/written today with this header. I agree it is a bit a shame not to know more and be forced to keep something we do not catch why it is there, but anyway...
-----Message d'origine-----
De : ffmpeg-devel-bounces at ffmpeg.org [mailto:ffmpeg-devel-bounces at ffmpeg.org] De la part de Lou Logan
Envoyé : mercredi 11 juin 2014 00:01
À : ffmpeg-devel at ffmpeg.org
Objet : Re: [FFmpeg-devel] [PATCH] lavc: remove imx_dump_header bitstream filter

On Tue, 10 Jun 2014 20:57:18 +0000, Gaullier Nicolas wrote:

> I strongly suggest not to remove this filter. The fact is that FCP, 
> omneon, FFMBC among them or others do handle IMX differently that 
> MPEG2. I am not able to say why, maybe it was some time ago only for 
> FCP compatibility to identify IMX because FCP was indeed not able to 
> decode regular MPEG2. But anyway, at the end, this had become a 
> standard. The fact that some systems today are agile, flexible, robust 
> and are able to read MOV IMX where the "IMX header" is missing in the 
> mdat, is certainly a good thing, but I think they will all continue to 
> write files the same way, without breaking compatibility : there are 
> anyway many legacy systems around, and many archives in MOV IMX that 
> are to stay consistent.
> Nicolas

Thanks for the reply. I didn't actually expect to push this commit, so you can consider it dropped, but I thought I'd throw it out there as an alternative to my imxdump documentation patch and as a probe to see if anyone uses this bitstream filter.

Do you know any versions of FCP that do benefit from this bsf?
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org

More information about the ffmpeg-devel mailing list