[MPlayer-dev-eng] dynamic A/V sync possibility in EDL
D Richard Felker III
dalias at aerifal.cx
Wed Feb 12 17:09:12 CET 2003
On Wed, Feb 12, 2003 at 08:13:46AM -0700, Michael Halcrow wrote:
> On Wed, 2003-02-12 at 05:06, Kövesdi György wrote:
> > Hi,
> >
> > I don't know if the EDL file format is a standard or not (i don't
> > want to violate any standards)
>
> I did not think out the EDL format very carefully. I just needed
> something that worked while I coded the actual functionality. I would
> prefer the format to be XML-based, so you could have a format that looks
> something like this:
>
> <edlentry>
> <action>0</action>
> <start unit=second>34.4</start>
> <end unit=second>35.2</end>
> <category>advertisement</category>
> </edlentry>
>
> or:
>
> <edlentry>
> <action>
> <libmpcodec name="boxblur" params="3:4"/>
> </action>
> <start unit=frame>1002</start>
> <duration unit=second>2.5</duration>
> </edlentry>
>
> or:
>
> <edlentry>
> <action>2</action>
> <start unit=frame>2420</start>
> <!-- Zero length -->
> </edlentry>
>
> >, but i added a feature which can
> > change the A/V sync during playback and encoding too. I think it can
> > (at least temporarily) resolve some A/V sync problems.
>
> I've thought about doing this. Actually, with an XML format, it would
> not be hard to modify EDL to be able to perform *any* operation that
> MPlayer can do. Like change the brightness/contrast, change A/V sync,
> change volume, etc.
What on earth is the point in an XML-based format? It's horribly
verbose and hideous to edit by hand (and somewhat painful to parse
unless you use silly libs), and as far as I can tell it has no
advantages. The same stuff you're talking about could be done with a
nice simple flat text format.
Rich
More information about the MPlayer-dev-eng
mailing list