XviD Analyzer v0.14

[MoonWalker]

Jumped to v0.14 (Call me superstitious :) )

v0.14
Corrected all the bug concerning the 2-pass log-file
Added a very basic 1-pass analyzer
Added help within the program if you just execute xda
Corrected some minor bugs (can't remember)

Now the prog should work with all the logfiles. Please report if any bug is found

You can download the program following the link at my signature.If for some reason you can't access my page and/or download the file please PM me with you e-mail to send it to you

MoonWalker

[Kyo]

Great Job Guys!

And ...I like more the old design of the page :D

Thanks for your bits

[Marc FD]

me too.
i like ftps,
but it's forbidden by my host.

[drizztcanrender]

Well i still have problems!When i rename the log file to Xvid.log and double click on xda.exe it says that "xda.exe has created a problem with XDA.EXE.The program needs to close".But it creates a ccintra and a graph txt files,both of them are empty though.

[iago]

@MoonWalker

I can confirm the problem drizztcanrender encounters. I have the same problem here. xda.exe works without any problem on .stats files, but it crashes with .log files [both in command-line (xda.exe -s filename.log)] and when double-clicking on it with the log file renamed as XviD.log. And yes, only two blank files are created: ccintra.txt and graph.txt. (OS: Windows XP)

regards,
iago

[MoonWalker]

@iago

These days I am not home to look at it..I will be from monday..But can you post some lines of the log file? In the log file, have you got 1-pass and 2-pass logged??

MoonWalker

[iago]

@MoonWalker

Well, I'd used the 2ndPass log files. But now, I've detected the problem and found a cure for it ;). It's not xda.exe related actually; the problem is the first line of some log files. If there's an extra first line at the beginning of the log file (that's what debugview does on some computers), xda.exe crashes. When you delete the unnecessary first line, everything is OK ;).


For example:

------------------------------------------------------------------
[//MOS]
00000000 0.00000000 [232] middle frame size for asymmetric curve compression: 4319
00000001 0.00328645 [232] 2nd-pass: quant:2 H.263 intra stats1:1949 scaled:1515 actual:1515 overflow:0 movie
00000002 0.02812871 [232] 2nd-pass: quant:3 H.263 inter stats1:1381 scaled:742 actual:88 overflow:654 movie
00000003 0.03431470 [232] 2nd-pass: quant:4 MPEG inter stats1:928 scaled:499 actual:360 overflow:793 movie
00000004 0.05709580 [232] 2nd-pass: quant:4 MPEG inter stats1:1058 scaled:569 actual:369 overflow:993 movie

crashes.

---------------------------------------------------------------

However,

00000000 0.00000000 [232] middle frame size for asymmetric curve compression: 4319
00000001 0.00328645 [232] 2nd-pass: quant:2 H.263 intra stats1:1949 scaled:1515 actual:1515 overflow:0 movie
00000002 0.02812871 [232] 2nd-pass: quant:3 H.263 inter stats1:1381 scaled:742 actual:88 overflow:654 movie
00000003 0.03431470 [232] 2nd-pass: quant:4 MPEG inter stats1:928 scaled:499 actual:360 overflow:793 movie
00000004 0.05709580 [232] 2nd-pass: quant:4 MPEG inter stats1:1058 scaled:569 actual:369 overflow:993 movie

doesn't crash.


Best regards,
iago

[MoonWalker]

You are right iago...

The [//MOS] line cause xda to crash..I haven't seen this in any logfile I have analyzed, so I didn't know it..I wonder why this is printed in the debugview.Possible from XviD itself..Well, as you said you have to delete this line for xda to work..I will fix it(or maybe MarcFD :) )

Thanks for reporting iago

MoonWalker

[Acaila]

That first line is the name of the computer whose input you're capturing with debugview. So it will be different for everyone.

[MoonWalker]

Originally posted by Acaila
That first line is the name of the computer whose input you're capturing with debugview. So it will be different for everyone.

Hmm..I haven't seen it so far..Mayve it's something new..I will fix it as soon as I return to my pc..

MoonWalker

[Marc FD]

all other lines begin with "0", right ? so it's easy to get rid of it.
in fact, it shouldn't crash at all.

i'll fix it ASAP.

[MoonWalker]

Originally posted by Marc FD
all other lines begin with "0", right ? so it's easy to get rid of it.
in fact, it shouldn't crash at all.

i'll fix it ASAP.

You are correct MarcFD..It's very easy, but I am not in my pc to fix it.And since you are faster..:D :D ...

MoonWalker

[iago]

Hello MoonWalker,

Regarding the lost frames/frame count issue with xda.exe, here are the results from an encode I have just finished. (Total no. of frames in the movie: 172401 and no special credits treatment.) The debugview and the XviD Analyzer v0.14 results are (different again and) as follows:

debugview:
----------
Quantizer distribution for 2nd pass:
Q:2:1
Q:3:4821
Q:4:107718
Q:5:57553
Q:6:2282
Q:7:26


XviD Analyzer v0.14 (full report)
---------------------------------
XviD Analyzer v0.14 by MoonWalker & MarcFD
e-mails : s_ilias@gmx.net & marc.fd@libertysurf.fr


Quantizers Analisis
---------------------

Quantizers Used For Movie :
------------------------------
Quant 2 Used : 1 Times, Percentage Used : 0.00%
Quant 3 Used : 4820 Times, Percentage Used : 2.80%
Quant 4 Used : 107712 Times, Percentage Used : 62.48%
Quant 5 Used : 57549 Times, Percentage Used : 33.38%
Quant 6 Used : 2282 Times, Percentage Used : 1.32%
Quant 7 Used : 26 Times, Percentage Used : 0.02%

Average Quantizer Used for Movie : 4.333

No credits encoding!!

MPEG Quantization Type Used 172390 timed, Percentage Used : 100.00%

No prevention happened


Intra-Frame (Key-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 1 Times, Percentage Used : 0.12%
Quant 5 Used : 839 Times, Percentage Used : 99.06%
Quant 6 Used : 7 Times, Percentage Used : 0.83%

No credits encoding!!

Inter-Frame (P-Frame) Quantizers
------------------------------------

Movie
-------
Quant 3 Used : 4820 Times, Percentage Used : 2.81%
Quant 4 Used : 107712 Times, Percentage Used : 62.79%
Quant 5 Used : 56710 Times, Percentage Used : 33.06%
Quant 6 Used : 2275 Times, Percentage Used : 1.33%
Quant 7 Used : 26 Times, Percentage Used : 0.02%

No credits encoding!!



Frame Analisis
----------------

Number Of Intra-Frames (Key-Frames) : 847
Number Of Inter-Frames (P-Frames) : 171543
Total Number Of Frames : 172390

0.49% of the Movie is Intra-Frames (Key-Frames)
99.51% of the Movie is Inter-Frames (P-Frames)



Size Analysis
----------------

1-Pass Size : 1887958648 Bytes or 1843709 KBytes or 1800 MBytes
Scaled Size : 676793263 Bytes or 660930 KBytes or 645 MBytes
Actual Size : 676798546 Bytes or 660936 KBytes or 645 MBytes

Usefull Statistics
------------------
Compressibility : 35.85%
Relative Quality of XviD avi : 46.16%
Absolute Quality of XviD avi : 93.00%


11 frames seem to be discarded by xda.exe ;)...

best regards,
iago

[Marc FD]

can you check howmany frames are in the log file ??

because xda can't report frame who aren't in the log.
maybe that's the problem...

whatever, 1.1/1.72e5 is a acceptable error ratio :D

[iago]

Hi Marc,

I agree with you that it's a negligible error actually ;).

Still here is the information you ask:

First pass and second pass are captured altogether in the log file:

This is the line where the second pass begins:
----------------------------------------------
00172401 3937.20270844 [540] middle frame size for asymmetric curve compression: 3889

This is the line where the second pass ends:
--------------------------------------------
00344795 7998.70175763 [540] Quantizer distribution for 2nd pass:


and then comes the list of quantizers which I had already posted above:

Q:2:1
Q:3:4821
Q:4:107718
Q:5:57553
Q:6:2282
Q:7:26
---------
total -> 172401 (which is the correct number of frames)


regards,
iago

[MoonWalker]

Hmm,the pattern the xda analyzes is this
00000003 0.03431470 [232] 2nd-pass: quant:4 MPEG inter stats1:928 scaled:499 actual:360 overflow:793 movie

Can you see in you log a line that doesn't begin with a digit and has "quant:" in? Or do you see a line where there isn't the "2nd-pass:" string but it has "quant:"(excuding the "1st-pass:")??

Hope you didn't get confused :)

MoonWalker

[iago]

@MoonWalker,

Are you serious pal? ;) It's a torture to look for such lines in a full log file! ;) But I can say that, with only a quick review of the log, I haven't seen such broken lines.

And yes, the pattern is exactly the way xda.exe analyzes.

1st pass seems OK. 172400 (including frame 0) -> 172401
2nd pass is confusing -> 344795 - 172401 = 172394 (?)

I guess it might be a problem due to debugview capturing in the second pass (or sth else?)... But the total of the quantizer distribution that it spits out for the second pass is still correct!? :confused:

regards,
iago

[MoonWalker]

hi iago,

I didn't mean to check every line in the log :). Just throw a glance to it.Hmmm, you said at another post that you have a Cel900? When you encoding, are you doing something else simultationly? Maybe debugview doesn't catch all the lines.

But the total of the quantizer distribution that it spits out for the second pass is still correct!?

The quantizer distribution in the end, it's from inside XviD and it's not calculated by debugview.So it's irellevant if debugview missed some lines.

MoonWalker

[iago]

@MoonWalker

-> ...you have a Cel900? When you encoding, are you doing something else simultationly? Maybe debugview doesn't catch all the lines. (MoonWalker)

Yes, most of the time I do other things while encoding. It seems that the problem actually results from debugview capturing and possibly not related with xda.exe. Thanks for taking the time to look into the issue and clearing it up.

best regards,
iago

(Guess I have to upgrade right away! ;))

[iago]

@MoonWalker

I got your both mails and replied to you to give the good news ;), but my both replies returned an "undeliverable message" notification :(. So I'm writing to you here. Yes, it is OK, without any problems :).

Thanks,
iago