dotBL0t's X264 Stats Analyzer 0.7.1 (build 129)

[dotBL0t]

:: dotBL0t's X264 Stats Analyzer ::

My little tool to analyze X264 stats file. I hope you like it!


SCREENSHOT:

http://img81.imageshack.us/img81/9919/snap3nf6.jpg

http://img301.imageshack.us/img301/2125/snap4wm0.th.jpg (http://img301.imageshack.us/my.php?image=snap4wm0.jpg) http://img100.imageshack.us/img100/1103/snap5gw9.th.jpg (http://img100.imageshack.us/my.php?image=snap5gw9.jpg)

WHAT'S NEW:

Version 0.7.1 (build 129)

CHANGED: Code was completely rewritten from scratch (except some cut and paste).
CHANGED: Brand new graphical interface (I hope you like it).
CHANGED: Graphical report was removed (It will be re-implemented later).
ADDED: You can now analyze a specified range of frame (so you can avoid to analyze start/end movie credits).

LINKS:

X264.nl:
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://mirror01.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://mirror02.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://mirror03.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://mirror04.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://mirror05.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)

SAVEFILE.com:
dotBL0t's.X264.Stats.Analyzer.071b129.rar (http://www.savefile.com/files/357490)

ENJOY! :D

Bug reports and/or suggestions: dotblot[at]rebels.com

[buzzqw]

nice to see here dotBL0t ! (and in DD and DExp) :)

your tool is very nifty ! thanks for sharing !

BHH

[mitsubishi]

Looks pretty cool, cheers, nice work. In the middle of some CQ encoding now, will play later.

Lol, anyone else read BBCode as BBC ode....

[Kurth]

Can you please host the file on another place?

Everytime I try to download something from megaupload it is always slot full for my region even if I wait a lot of hours it is still full.

[buzzqw]

mirror www.64k.it/andres/data/d/dotBL0t's.X264.Stats.Analyzer-034b87.rar

BHH

[Sharktooth]

nice :)

[lexor]

what would be a practical use for this tool? I mean the graph and stats are nice, but what's the use?

[Sharktooth]

to optimize the ratecontrol refinement and obtain a better encoding.

[dotBL0t]

to optimize the ratecontrol refinement and obtain a better encoding.

YEP!!! ;)

[lexor]

how exactly? you mean find a better --crf value? so no use in 2pass?

[Sharktooth]

no... it's useful for Nth pass. you can watch the quants distribution and adjust codec settings to make the RC behave as you want. think of it as you're doing a manual tuning.

[yaz]

it does not work for me; i see only half of the screen (roughly the black screen) and nothing happens on loading any stats file. is there any special system requirements or do i need sg added ?
thx
y

[pasta03]

Hey!
On my PC it is the same.
I see only half of the screen (roughly the black screen) and nothing happens on loading any stats file.

[dotBL0t]

1) Open your stats file through the "File" menu
2) Click the ":: Analyze" button to start the analysis
3) If you want to see the graphic just click on the ">>" at the right side of the program window
4) Click again to hide it.

;)

[pasta03]

I only see this:

http://img370.imageshack.us/img370/4816/untitledxr8.png

I don't see any "Analyze" button

[imcold]

I solved it by resizing the window with Sizer (http://www.brianapps.net/sizer.html). Analyse window is in the right part of the window.

[elguaxo]

Thanks! Great tool.

[mitsubishi]

Yah! This app has just saved the day for the first time. My PC thought it was hilarious to crash 10 hours into an encode. MeGui doesn't seem to save job or log in these circumstances and I forgot the bitrate I put in, but this app shows it so I was at least able to reuse the stats file.

(OK so a hex editor would do, but :p )

[pasta03]

To see all program what I need the resolution on my monitor.

[pasta03]

Hey!

dotBL0t the small request:
1) it is proper that was add to the programme of the reel to re-wrapping of the screen then on monitors with the resolution 1024x768 one can that to see the all programme.

2) On the ground what (how it enumerates) your programme options:
Average Frame Quality is HIGH
Standard Deviation Quality is HIGH
Image Resolution is VERY HIGH

[Caroliano]

Very good! Sure it will be helpfull tweaking the ratecontrol for my own encodes.

Two small requests/suggestions: (shoud I sent them by e-mail?)
- Every time that you analize an new file, reset the zoom, because the quantizer distribution and the number of the frames between them can be very diferent. Or put it as an checkbox that is remembered after.
- Include an option or a continuation in the log that diferentiate I, P and B frames in the "Frame Quality Statistics", but as defaut leve as it is, because it is less confuse.

Thanks!

[galaxy001]

Version 0.3.4 (build 87)
------------------------
FIXED: No more "is not an integer value" errors when you try to analyze x264 stats files
??
I still get that error. Why ?
WinXP SP2 CHS
.Net Framework 1,2,3

Is it just because .Net Framework 3 ?

[dotBL0t]

Version 0.3.4 (build 87)
------------------------
FIXED: No more "is not an integer value" errors when you try to analyze x264 stats files
??
I still get that error. Why ?
WinXP SP2 CHS
.Net Framework 1,2,3

Is it just because .Net Framework 3 ?

Just send me the stat file that cause this error (or upload it to a free file hosting site) and i'll try to fix it.
Thank you!

[Inventive Software]

Any chance of something similar for XviD or DivX generated stats files dotBL0t?

[dotBL0t]

Any chance of something similar for XviD or DivX generated stats files dotBL0t?
Well, I never thought about it because there's "DivX DRF Analyzer" that's able to analyze XviD/DivX encoded files directly and give a similar report as the one used in my x264 stats analyzer. However, I can improve my program with the analysis of XviD stats files but I want to complete the x264 section first.

[dotBL0t]

Program updated!

[Sagittaire]

Possible to check vbv compliance ... ???

[dotBL0t]

mirror01 (http://mirror01.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
mirror02 (http://mirror02.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
mirror03 (http://mirror03.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
mirror04 (http://mirror04.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
mirror05 (http://mirror05.x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)
mirror06 (http://x264.nl/x264/dotBL0t_s_X264_Stats_Analyzer_071b128.rar)

May put in inital post

Done. Thanks!
Possible to check vbv compliance ... ???

Well, first just let me know what vbv is :D

[Sharktooth]

Video Buffer Verifier

[elguaxo]

dotBL0t, I'm using your Stats Analyzer for the first time. I think pasta03's question is very interesting. When does your app decide that the 'Quality is HIGH'?

With Xvid an Avg. Quant of 3 is considered high quality and my eyes usually agree. Since I started with x264 my only quality reference was the Final Ratefactor and I am pleased with something around 20.

I haven't kept the statfiles of my encodes, but I will keep them now, or at least the report of your app. At some point I will see what I consider to be high quality, but I wonder if you can tell us more about the relation of the Final Ratefactor and Avg. Quantizer, or even if there is an Avg. Quant for x264 equivalent to Avg. Quant 3 for Xvid.

Thanks!

Edit: I searched and found a good explanation of ratefactor/avg. quant :p
So my only question is now. Has x264 an Avg. Quant that is considered to be equivalent to an Avg. Quant of 3 for Xvid?

[galaxy001]

Just send me the stat file that cause this error (or upload it to a free file hosting site) and i'll try to fix it.
Thank you!
Sorry for the long delay. Here is the cutted stat file which leads to the same error.

#options: 640x360 fps=24/1 cabac=1 ref=9 deblock=1:-2:-1 analyse=0x3:0x133 me=umh subme=7 brdo=1 mixed_ref=1 me_range=32 chroma_me=1 trellis=2 8x8dct=1 cqm=0 deadzone=21,11 chroma_qp_offset=0 slices=1 nr=0 decimate=1 mbaff=0 bframes=16 b_pyramid=1 b_adapt=1 b_bias=0 direct=3 wpredb=1 bime=1 keyint=250 keyint_min=25 scenecut=40 rc=2pass bitrate=1250 ratetol=1.0 rceq='blurCplx^(1-qComp)' qcomp=0.60 qpmin=8 qpmax=27 qpstep=4 cplxblur=20.0 qblur=0.5 ip_ratio=1.40 pb_ratio=1.30 zones
in:0 out:0 type:I q:9.00 itex:195 ptex:0 mv:391 misc:5046 imb:920 pmb:0 smb:0 d:-;
in:17 out:1 type:P q:9.00 itex:0 ptex:0 mv:0 misc:168 imb:0 pmb:0 smb:920 d:-;
in:9 out:2 type:B q:10.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:1 out:3 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:2 out:4 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:3 out:5 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:4 out:6 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:5 out:7 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:6 out:8 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:7 out:9 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:8 out:10 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:10 out:11 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:11 out:12 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;
in:12 out:13 type:b q:11.00 itex:0 ptex:0 mv:0 misc:144 imb:0 pmb:0 smb:920 d:-;

[dotBL0t]

Sorry for the long delay. Here is the cutted stat file which leads to the same error.


I found the bug, I'll try to fix it in the next release!
Thanks a lot! :D

dotBL0t, I'm using your Stats Analyzer for the first time. I think pasta03's question is very interesting. When does your app decide that the 'Quality is HIGH'?

With Xvid an Avg. Quant of 3 is considered high quality and my eyes usually agree. Since I started with x264 my only quality reference was the Final Ratefactor and I am pleased with something around 20.

I haven't kept the statfiles of my encodes, but I will keep them now, or at least the report of your app. At some point I will see what I consider to be high quality, but I wonder if you can tell us more about the relation of the Final Ratefactor and Avg. Quantizer, or even if there is an Avg. Quant for x264 equivalent to Avg. Quant 3 for Xvid.

Thanks!

Edit: I searched and found a good explanation of ratefactor/avg. quant :p
So my only question is now. Has x264 an Avg. Quant that is considered to be equivalent to an Avg. Quant of 3 for Xvid?

I think it could be around 26.

Hey!

dotBL0t the small request:

On the ground what (how it enumerates) your programme options:
Average Frame Quality is HIGH
Standard Deviation Quality is HIGH
Image Resolution is VERY HIGH

These parameters are estimated this way:

if RESOLUTION * AR is >= (720*384*1.85) then it's considered to be VERY HIGH
if it is >= (624*336*1.85) then it's considered to be
HIGH
if it is >= (544*288*1.85) then it's considered to be
MEDIUM
if it is >= (480*256*1.85) then it's considered to be
LOW
else it's considered to be VERY LOW;

if STD.DEVIATION is < 4 then it's HIGH
if it's < 8 then it's MEDIUM
else it's LOW

if AVG. QUANTIZER is < 26 then it's HIGH
if it's < 36 then it's MEDIUM
else it's LOW

[elguaxo]

Thanks for your answer dotBL0t!

Now I have for example this report:
Frame Quality Statistics:

Q = 10: 177 (0,10%)
Q = 11: 206 (0,11%)
Q = 12: 436 (0,24%)
Q = 13: 440 (0,24%)
Q = 14: 1262 (0,69%)
Q = 15: 4458 (2,44%)
Q = 16: 9483 (5,19%)
Q = 17: 14860 (8,13%)
Q = 18: 20627 (11,29%)
Q = 19: 23459 (12,84%)
Q = 20: 25371 (13,89%)
Q = 21: 25881 (14,17%)
Q = 22: 22660 (12,40%)
Q = 23: 15590 (8,53%)
Q = 24: 10209 (5,59%)
Q = 25: 4053 (2,22%)
Q = 26: 2514 (1,38%)
Q = 27: 685 (0,37%)
Q = 28: 170 (0,09%)
Q = 29: 63 (0,03%)
Q = 30: 88 (0,05%)
Q = 31: 3 (0,00%)

I would like to see the frames with Q=10-15 to see how good they are and the Q=26-31 to see how bad they are. How can I find where those frames are?

[bob0r]

b129 is a typ0 right? It is still version b128 that is latest?

[munnasunna]

thanks for the tool dotBL0t, was looking for something like this :thanks:

[dotBL0t]

thanks for the tool dotBL0t, was looking for something like this :thanks:

:D

b129 is a typ0 right? It is still version b128 that is latest?

I just mistyped the filename. The right version number is b129.

Thanks for your answer dotBL0t!

Now I have for example this report:
Frame Quality Statistics:

Q = 10: 177 (0,10%)
Q = 11: 206 (0,11%)
Q = 12: 436 (0,24%)
Q = 13: 440 (0,24%)
Q = 14: 1262 (0,69%)
Q = 15: 4458 (2,44%)
Q = 16: 9483 (5,19%)
Q = 17: 14860 (8,13%)
Q = 18: 20627 (11,29%)
Q = 19: 23459 (12,84%)
Q = 20: 25371 (13,89%)
Q = 21: 25881 (14,17%)
Q = 22: 22660 (12,40%)
Q = 23: 15590 (8,53%)
Q = 24: 10209 (5,59%)
Q = 25: 4053 (2,22%)
Q = 26: 2514 (1,38%)
Q = 27: 685 (0,37%)
Q = 28: 170 (0,09%)
Q = 29: 63 (0,03%)
Q = 30: 88 (0,05%)
Q = 31: 3 (0,00%)

I would like to see the frames with Q=10-15 to see how good they are and the Q=26-31 to see how bad they are. How can I find where those frames are?

Well...at this stage you're not be able to do this using my program. I could try to implement it in the next release. Unfortunately i'm migrating definitely to linux so the development of the analyzer has slowed down. :(

[Jabroni]

Hey thanks for this great program.. im using this to generate the QP values from the stats of x264farm....

But i have just a lil' problem with this stats files, was wondering if you could take a look at it, the program crashes when I try to analyize it.. working_stats1.rar - 5.57MB (http://www.zshare.net/download/5114217caa5978/)

thanks

[survivant001]

there is a new release planned ?

I got lot of error when opening .stats with the latest x264 build