[MPlayer-DOCS] [PATCH] xvid zones patch doc(was [MPlayer-dev-eng] xvid zones patch)

[Guillaume POIRIER]

Hi,

On 6/2/05, Doom9 Feedback Hotline <feedback123 at doom9.org> wrote:
> >
> > IMO it's hard to have too many examples and easy to have too few.
> >
> > Tricky stuff is often easily explained with a good example or two that
> > cover the corner cases.
> 
> That's why I put two examples. One outlines the most common case (end
> credits), and the second one another realistic scenario with a modifier at
> the beginning and end. The second example also outlines an important
> limitation of xvid zones: they last from the start frame to the start of the
> next zone, or the end of the movie. Hence, you need to put a weight 1 zone
> in between your start and end credits and I think it's quite crucial to
> outline that.

> And if you can also put the example usage of the weight based
> mode into that example, why not?

I don't know. Other than the fact it only use in 2-pass mode, it just
works as quant mode, so to me, it doesn't seem necessary. I don't mean
to say it's useless, but I think be can expect the used to be clever
enough to adapt the first example.

Other than that, I've been thinking about the syntax of zones.
I think it would be better if it could be something like:
<start-frame>,<option=value>,[[<option=value>],<option=value>]/
for instance: zones=30000,q=22,grey=1,bsens=10,chromaopt=0,key=0
which would make the zone start at frame 30000, with quant 22, in
greyscale, with a b-frame sensibility of 10, no chroma optimisation,
and no keyframe to start the zone.

The problem is that this would require to add a complete parser to
support this, won't it?

Guillaume
-- 
Jazz music and Open Source development looks like chaos to an
untrained eye, but end-up producing masterpieces like "Kind of Blue"
and "MPlayer".
That's why I love them both...
  -- John Coltrane