DebugView analyzer for XviD codec v0.1

[MoonWalker]

I have made up a small prog that analyzes the XviD debug output

ReadMe.txt
DebugView analyzer for XviD codec v0.1 by MoonWalker

Usage :

!!!IMPORTANT : Your debug file MUST have the name "dbg.txt"!!!

Just put your dbg.txt and dbg.exe in the same directory and run dbg.exe


What it does:
It analyzes the debug output of the 2-pass of the XviD codec.
It reports :

1)The Quantizers used(for movie and credits separately)
2)The average movie quantizer
3)Total I-Frames, P-Frames and Frames


To-Do

1)Report actual size of the movie
2)Report 1-pass size of the movie
3)Report 2-pass size of the movie
4)write all these to a file
5)You Suggestions here

The sources are free. Just e-mail me to have them.

For any help or modification or suggestion or whatever e-mail me.

e-mail : s_ilias@gmx.net

(c) 2002 by MoonWalker


EDIT : Look further down for v0.2

[primitive]

If you really feel like reimplementing this functionality, check out the perl script begun by myself and extended by canadian_fbi and reimplement that functionality.

Of course, since we have made our sources freely available you might as well just hack on that ;)

-p

[Kyo]

Adding those stuff would be nice!

Thanks MoonWalker for take your time and bring to us some :p

My first test :o
Quantizers Analisis
---------------------
Quantizers Used For Movie :
------------------------------
Quant 2 Used : 23900 Times.
Quant 3 Used : 10236 Times.
Quant 4 Used : 250 Times.
Average Quantizer Used for Movie : 2.312

No credits encoding!!
Frame Analisis
----------------
Number Of Intra-Frames (Key-Frames) : 328
Number Of Inter-Frames (P-Frames) : 34059
Total Number Of Frames : 34386

0.95% of the Movie is Intra-Frames (Key-Frames)
99.05% of the Movie is Inter-Frames (P-Frames)

i know, a movie with few, really few key frames (Lain ep 06)
(this could take down the quality? and how could I raise them?)

/edited and cuted for bad english /:rolleyes:

[MoonWalker]

@primitive

You know at the beging i thought to extend you perl script but I saw that for a newbie it's easier just to run a prog that to download the activeperl and the run it. For me it's the same :)...

@Kyo
Thanks for testing.I'll try to add these the sooner. To raise the keyframes you could lower the Max Keyframe intreval in the XviD config.


MoonWalker

[OUTPinged_]

MoonWalker, can you please extend quantizer distribution line to show percentage?

I mean, from this:

Quant 4 Used : 250 Times.


To this:

Quant 2 Used : 23900 Times. , 65,7%
Quant 4 Used : 250 Times. , 0,75%

[MoonWalker]

MoonWalker, can you please extend quantizer distribution line to show percentage?

Ok. I'll do it..I suppose by tommorow it should be ready...:)

MoonWalker

[canadian_fbi]

now what would be really great (in my opinion anyway) would be if the developers provided the option to automatically log the dbgview output into a file. divx 5 did this i think, if i'm not mistaken (haven't used it since the first day it came out). that way you wouldn't have the extra overhead of dbgview running in the background logging everything, and it would be more difficult to forget to start it before an encode (as i have been prone to do). if you prefer watching the process as it's going, then you could just uncheck the "log analyze data" or something checkbox and do it as usual. is this possible?

[MoonWalker]

I just did some changes at the DebugView analyzer..

v0.2
Added Report 1-pass size of the movie
Added Report 2-pass (scaled) size of the movie
Added Report actual size of the movie
Added Percentages for quantizers at the movie portion(requested by OUTPinged_ :) )

For anything my e-mail : s_ilias@gmx.net

As usual a mod should accept the attachment :)...

MoonWalker

[MoonWalker]

now what would be really great (in my opinion anyway) would be if the developers provided the option to automatically log the dbgview output into a file. divx 5 did this i think, if i'm not mistaken (haven't used it since the first day it came out). that way you wouldn't have the extra overhead of dbgview running in the background logging everything, and it would be more difficult to forget to start it before an encode (as i have been prone to do). if you prefer watching the process as it's going, then you could just uncheck the "log analyze data" or something checkbox and do it as usual. is this possible?

Well this is a job for the developer (-h??) not for me :)..I don't know that much programming. But it would a very very nice feature since sometimes we could forget to open debugview..

MoonWalker

[-h]

Yep this can be done.

-h

[MoonWalker]

-h What exactly is the differnece between scaled and actual at the debug? The scale is the calculated value without the frame-overhead and the actual with?

MoonWalker

[-h]

-h What exactly is the differnece between scaled and actual at the debug? The scale is the calculated value without the frame-overhead and the actual with?

The scaled value is how many bytes the codec wanted to assign to a frame (from calculating overflow, scaling, etc.), whereas the actual value is how many bytes the frame ended up consuming when encoded. The difference between these values is how "wrong" the codec guessed, and is added to the overflow.

-h

[MoonWalker]

So the total overflow should be (Total scaled size - Total actual size)?? Corect?

Thanks,
MoonWalker