canadian_fbi
1st August 2002, 21:08
well it's been a while since i did anything with the old perl script started by primitive and continued by me for analyzing debugview output of xvid encodes. so i've updated it a bit to basically duplicate the functionality of the newer, better analyzers such as the one moonwalker has developed. i found myself using his version specifically to analyze how many i-frames were in the credits now, since that seems to be kind of erratic sometimes.
so why would you want to use this analyzer when there's a lot of newer (better) ones out there? well, i use it because it supports multiple movies in one debugview log file. in other words, i encode a couple of things (order: 1st pass, 2nd pass, 1st, 2nd, etc) and then i run this script and it dumps out a text file for each movie with its own info in it. also, it runs a good deal faster than moonwalker's .exe version (3.5x faster for me). however, you need perl installed on your system, which you can get at http://www.activestate.com/Products/ActivePerl/ and it won't give you a pretty graph like marcfd's alt-dbg analyzer. but i still like it :)
here it is: http://www.disconnect.net/temp/dbg_analyze.pl
to use it, once you have perl installed just run the script if your debugview log file is the now-standard dbg.log. or if it's named differently, you can type the input/output filenames as command-line arguments. but i just save the debugview file as dbg.log and then double-click on the .pl file in windows explorer and a couple seconds later i have my analysis file.
and this is much too much chatter for a 200-line perl script that most people won't use, except maybe me and primitive :)
so why would you want to use this analyzer when there's a lot of newer (better) ones out there? well, i use it because it supports multiple movies in one debugview log file. in other words, i encode a couple of things (order: 1st pass, 2nd pass, 1st, 2nd, etc) and then i run this script and it dumps out a text file for each movie with its own info in it. also, it runs a good deal faster than moonwalker's .exe version (3.5x faster for me). however, you need perl installed on your system, which you can get at http://www.activestate.com/Products/ActivePerl/ and it won't give you a pretty graph like marcfd's alt-dbg analyzer. but i still like it :)
here it is: http://www.disconnect.net/temp/dbg_analyze.pl
to use it, once you have perl installed just run the script if your debugview log file is the now-standard dbg.log. or if it's named differently, you can type the input/output filenames as command-line arguments. but i just save the debugview file as dbg.log and then double-click on the .pl file in windows explorer and a couple seconds later i have my analysis file.
and this is much too much chatter for a 200-line perl script that most people won't use, except maybe me and primitive :)