1,633
edits
Avdump: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 22: | Line 22: | ||
==Download== | ==Download== | ||
Latest version (18th March 2008) is 0.34. | Latest version (18th March 2008) is 0.34. | ||
Get your copy of | Get your copy of Avdump [http://static.anidb.net/client/avdump.rar HERE]! | ||
md5sum rar=225f2058812f601876fd5960bed95b74, exe=ee85a21848db15dc8bee3dd4180be953 | md5sum rar=225f2058812f601876fd5960bed95b74, exe=ee85a21848db15dc8bee3dd4180be953 | ||
| Line 115: | Line 115: | ||
===Windows Shortcut=== | ===Windows Shortcut=== | ||
#Extract | #Extract Avdump to a folder of choice. | ||
#:Example: <tt>"C:\Program Files\avdump\"</tt> | #:Example: <tt>"C:\Program Files\avdump\"</tt> | ||
#Right-click <tt>avdump.exe</tt>, select ''Create Shortcut''. | #Right-click <tt>avdump.exe</tt>, select ''Create Shortcut''. | ||
| Line 137: | Line 137: | ||
===MS-DOS Batch File=== | ===MS-DOS Batch File=== | ||
#Extract | #Extract Avdump to a folder of choice. | ||
#Create a MS-DOS batch file with the 2 lines below, and save it as ''filename.bat''. | #Create a MS-DOS batch file with the 2 lines below, and save it as ''filename.bat''. | ||
#<tt>@ECHO OFF</tt> | #<tt>@ECHO OFF</tt> | ||
| Line 152: | Line 152: | ||
== Auto-creqing == | == Auto-creqing == | ||
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with | [[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump works]] | ||
Avdump is now part of a new [[auto-creqing]] system. Some more or less important notes: | Avdump is now part of a new [[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 ''api key'' in your [[profile]]. All data sent to the server will be logged with IP and uid. | * To be able to use this feature you’ll need an AniDB account and you have to define the ''api key'' in your [[profile]]. All data sent to the server will be logged with IP and uid. | ||
* Communication between client and server is ''one-way'' (except session init/refresh); the client does not receive any confirmation for sent data. This means that there is no guaranty that all the dumps you send will arrive at the server and stored in the database, and there is no way to check this. ''From version 0.31 it's possible to make | * Communication between client and server is ''one-way'' (except session init/refresh); the client does not receive any confirmation for sent data. This means that there is no guaranty that all the dumps you send will arrive at the server and stored in the database, and there is no way to check this. ''From version 0.31 it's possible to make Avdump wait for confirmation from the server by using the -o switch.'' | ||
* It is possible to run more than one instance of | * 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. | * 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. | * The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | ||
| Line 177: | Line 177: | ||
Even if the file is dumped it doesn't mean it will get auto-creqed (and verified). Here are the reasons: | 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 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 | * The provided data is considered "incoherent". (Indicates a bug in Avdump.) | ||
* The dump was marked unfit for file verification by an AniDB Moderator. | * The dump was marked unfit for file verification by an AniDB Moderator. | ||
* The file type is not included in auto-creqing yet (mov/mpg/rm ATM). | * The file type is not included in auto-creqing yet (mov/mpg/rm ATM). | ||