358
edits
Avdump2: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* avi, mkv, ogm, mp4, asf/wmv, mpg, rm, mov | * avi, mkv, ogm, mp4, asf/wmv, mpg, rm, mov | ||
==Changes== | [http://static.anidb.net/client/avdump2/avdump2_3804.rar DOWNLOAD(RAR)] MD5 = EBD9AEA4ED6E415D436D1B7DF6F308A4 | ||
==Changes From Avdump Classic== | |||
* 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. | * 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. | ||
| Line 18: | Line 20: | ||
** The "-n" parameter is no longer available in avd2. | ** The "-n" parameter is no longer available in avd2. | ||
** The meaning of the numeric parameters has changed. | ** 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. | * In the event of an internal error, AVD2 ''will'' submit an error report back to AniDB. The error report contains no user-details (see sample), 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. | ||
====Sample Exception Report==== | |||
==Sample Exception Report== | |||
<FileExceptions> | <FileExceptions> | ||
<Information> | <Information> | ||
| Line 46: | Line 46: | ||
</Exceptions> | </Exceptions> | ||
</FileExceptions> | </FileExceptions> | ||
== Auto-creqing == | |||
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump works]] | |||
Avdump2 is the AniDB [[auto-creqing]] system. Some more or less important notes: | |||
* To be able to use this feature you’ll need an AniDB account '''and you have to define the ''UDP API Key'' in your [[profile]]'''. All data sent to the server will be logged with IP and uid. | |||
* It is possible to run more than one instance of Avdump at once, but not more than ten will work OK. At the moment ''only 10 sessions per ip are allowed by the server'', meaning the eleventh instance will terminate the first. | |||
* There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 24 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time. | |||
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | |||
* You may dump files currently not in the database. The data is still stored and will be used later if/after the file has been registered. | |||
* Files creqed by the new system will be locked, meaning some fields will not be possible to change. Notify a moderator if you are '''sure''' that some of the data locked for a specific file is wrong. | |||
===Why didn't this file get dumped?=== | |||
* The file in AniDB is registered with wrong size and/or ED2K hash. | |||
* The package never reached the server. | |||
* The decryption or decompression failed at server side (rare). | |||
* The dump is not valid XML (rare). | |||
===Why isn't this file verified?=== | |||
Even if the file is dumped it doesn't mean it will get auto-creqed (and verified). Here are the reasons: | |||
* The file is corrupt/invalid ([http://anidb.net/perl-bin/animedb.pl?show=avmf&do=xml&avid=76226 example]). | |||
* The provided data is considered "incoherent". (Indicates a bug in Avdump.) | |||
* The dump was marked unfit for file verification by an AniDB Moderator. | |||