Avdump2

Welcome to the remarkably sparse avdump2 wiki page, lovingly hand created over many minutes.

Build 3800 represents an initial public release of avd2. It represents a complete rewrite of the original avd1 code, runs against a new build of MediaInfoLibrary, contains a number of custom solutions for a number of formats, represents a significant investment of time and energy by Arokh, and is just generally nifty.

What is it

Avdump2 is a video codec identification utility - identifies which video codec and audio compression method is used on video files. Furthermore it calculates the used bit rates, the length, identifies the number of used audio channels and more.
It, like its predecessor, is mainly based on mediainfo, but significantly enhanced and changed to fit AniDB's needs by arokh.

Supported formats

• Most major file formats are supported to some degree. While hashes are created for all file types, stream details remain shakey for others (notably 'swf'.)
• avi, mkv, ogm, mp4, asf/wmv, mpg, rm, mov

Changes

• AVD2 now runs on the managed .net platform. This will not affect most, as .net comes pre-installed with current versions of windows. XP or older may have to install the platform manually. While it has been tested on mono, such testing has not been exhaustive. We would be very interested in hearing how it behaves in such an environment.
• While most command line parameters remain the same, there are some exceptions.
  • The "-o" parameter is no longer available in avd2.
  • The "-n" parameter is no longer available in avd2.
  • The meaning of the numeric parameters has changed.
• In the event of an internal error, AVD2 will submit an error report back to AniDB. The error report contains no user-details, but is attached to the user name supplied with the -ac parameter. While error reports are only submitted if -ac is specified, they can be disabled by the addition of the -noerr parameter. That said, for the purposes of initial testing, we respectfully request that error reports not be disabled, so bugs can be found and fixed.

( linky   MD5 = 952DEC4B1F4E7C28D5C3624A98C6110B   )

Sample Exception Report

<FileExceptions>

<Information>

<AVDump2CLVersion>0.1.3734.0</AVDump2CLVersion>

</Information>

<Exceptions>

<AVDump2CL.Exceptions.AVD2Exception thrownOn="20110303 05.27.26.9254">

<Message>Error in DisplayBuffer</Message>

<System.ArgumentOutOfRangeException>

<Message>

Non-negative number required.

Parameter name: totalWidth

</Message>

<StackTrace>

<Frame>

at System.String.PadHelper(Int32 totalWidth, Char paddingChar, Boolean isRightPadded)

</Frame>

<Frame>at l.a(f A_0, Progress A_1)</Frame>

<Frame>at l.a(f A_0, Dictionary`2& A_1)</Frame>

</StackTrace>

</System.ArgumentOutOfRangeException>

</AVDump2CL.Exceptions.AVD2Exception>

</Exceptions>

</FileExceptions>