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. 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? While you argue that, here's my (hopefully correct and complete) list of what all the colors mean: Red: intra Purple: 4x4 intra (H.264) Green: forward-predicted Blue: backward-predicted Cyan: bidirectionally predicted Orange: direct Black and white (untinted): skip or direct-skip Other things: lines are drawn across macroblocks to indicate partitions in inter mb's (H.264) or the use of interlacing. Also, I don't understand the colorspace used here so I'm not sure what color to report for the following block types: GMC (mpeg4 asp); PCM (H.264). I'm pretty sure intra 8x8 blocks (H.264) are colored red, but not quite positive. Other cans of worms: if we document these, why not also document all the output from debug=8 as well? Now you see how things start getting long, especially with vertical listing. And clearly even much of the output of debug=1 isn't always obvious, and some of it is codec-specific, some of it is broken afaict,...
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.. Diego
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.
I suggest some seperate docs, xml or something, man page is big enough and this information isn't critical for mplayer usage... - ods15
Oded Shimon wrote: ...
I suggest some seperate docs, xml or something, man page is big enough and this information isn't critical for mplayer usage...
- ods15
Maybe it's time for some separation of the man pages. Actually, after the initial setup of my mplayer, I look at the man pages to see how a lavcopt is written os something like this, so a 'man mencoder_lavc' or 'man mencoder_xvid' may be a great feature. Obviously there should be the possibility of make, like now, a big page and there must not be duplicate man page (only some cat of the partial pages). Also for the translator will be, IMHO, better. My 2 cents Daniele Forghieri
On Thursday 02 February 2006 15:19, Danny - liste wrote:
Maybe it's time for some separation of the man pages.
I've often given the command "man lavcopts" myself :)
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? :) Diego
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
participants (6)
-
Danny - liste -
Diego Biurrun -
Jan Knutar -
Jeff Clagg -
Loren Merritt -
Oded Shimon