[MPlayer-DOCS] documenting lavdopts debug=0x4000

[Loren Merritt]

On Fri, 10 Feb 2006, Diego Biurrun wrote:
> On Thu, Feb 02, 2006 at 01:15:31PM +0100, Diego Biurrun wrote:
>> On Thu, Jan 26, 2006 at 10:54:11AM -0600, Jeff Clagg wrote:
>>> Well, there are probably MANY things that could be added to the
>>> documentation of lavdopts, but currently the easiest way to decipher the
>>> meaning of the output of "lavdopts debug=0x4000" is a combination of
>>> rtfs and lavdopts debug=0x4008. However, once we open this can of worms,
>>> the lavdopts section of the man page might become extremely long.
>>
>> Patches most welcome :)
>>
>>> Nevertheless, I'm going to suggest that we add explanations in the man
>>> page of what each block tint/color actually means. One of my questions
>>> is, should we stick to the old vertical listing style, which takes up a
>>> heck of a lot of space, or just list them in sentence form?
>>
>> I'd be tempted to keep the vertical listing, but this is a secondary
>> issue.  Once we have the text it's easy to reformat it.
>>
>>> Other cans of worms: if we document these, why not also document all the
>>> output from debug=8 as well?
>>
>> I'd love to see it documented..
>
> So what's it going to be? :)

Well, here's the text. I'll format it when we decide where to put it

debug=8 prints the type of each macroblock in each frame.
The primary types are:
I	Intra 16x16
i	Intra 4x4 or 8x8
P	Intra PCM
A	Intra with AC prediction
>       Inter forward
<       Inter backward
X       Inter bidirectional
S       Skip
D	Direct
d	Direct, no residual
G       GMC
g	GMC, no residual

This may be followed by a modifier:
(blank)	no partitions
+	8x8 or smaller partitions
|	8x16 partitions
-	16x8 partitions
=	Interlaced

--Loren Merritt