[Ffmpeg-devel] Re: [PATCH] MXF tag parser

Baptiste Coudurier baptiste.coudurier
Wed Aug 2 23:08:19 CEST 2006


Michael Niedermayer wrote:
> Hi
> 
> On Wed, Aug 02, 2006 at 06:46:59PM +0200, Reimar D?ffinger wrote:
> [...]
>>>> Maybe, but if the end result will be really better? And what if one day
>>>> we wanted to add checks if maybe tags are used that the specs do not
>>>> allow in that section?
>>> That would mean non valid files. Specs are specs and SMPTE usually
>>> really consider everything in the specs. Like I said, if we really want
>>> to support broken files, that code needs to be really isolated. Your
>>> file with '0' tag size is broken.
>> 1) I admit coming from MPlayer my goal is in the end to support as many
>> files as possible, broken or not.
> 
> ffmpeg has that goal too, if a file exists in the real world
> (intentionally generated files dont count) then we should support it
> if we would drop everything which isnt spec conformant then <10% of
> the avi files you can find would be playable
> so IMHO if your files are obscure test streams generated by you or
> some smartass who lacks a brain then we shouldnt support them, if
> OTOH they are some normal video downloaded/bought/captured/encoded
> by a unmodified encoder then we should try to support them 
> 
> [...]
>

What about DRM files ? We do not support them. Im thinking about itunes
files which use defined ismacrypt specifications, and standards and
could be supported.

I understand the point, but still IMHO that policy made people do crazy
things with AVI and OGM. That argument is not valid for all format IMHO.
It seems more like both sides broken instead of both sides clean.

I don't see what is bad in saying that file is broken and not playing
it, I'm more flexible concerning MOV/MP4/3GP than with MXF, basically
cause at first sight MOV was a likely proprietary/closed format and not
everything is clearly documented.

MXF format is strictly defined and specs are almost freely downloadable
at SMPTE. It's much documented, every format muxing supported has its
own document, and generic container for all other streams.

-- 
Baptiste COUDURIER                              GnuPG Key Id: 0x5C1ABAAA
SMARTJOG S.A.                                    http://www.smartjog.com
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
Phone: +33 1 49966312





More information about the ffmpeg-devel mailing list