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

[Doom9 Feedback Hotline]

Hi
>
> 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.

Well.. I'm dealing with 99% Windows users so I guess my expectations are
lower than yours ;)
>
> 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?
Well, you're thinking way ahead. Adding all the extra zone features
available in XviD VfW increases the complexity of the parser to an
unreasonable amount for the current patch. If somebody feels the need to
add all the other options xvid zones offer (that nobody uses anyway), the
parser will have to be changed, and the documentation will have to be
adapted as well, so I think it's a moot point to think about that
possibility now. And adding the additional features will require a lot of
work besides the parsing, as you have to hook into the encoder, and apply
zone modifiers to each frame before it's sent off for encoding (see
codec.c in the vfw/src directory from the XviD source tree).

Plus, I don't really agree with option=value for booleans. XviD, x264 and
lavc codecs use the (no)option notation for boolean options so it would
not be a good thing to introduce a new notation.

Cheers
Doom9