Avdump2: Difference between revisions

Jump to navigation Jump to search
2,157 bytes added ,  19 December 2021
{{Avdump-current-version}}
(added ref to avd1 deprecation)
({{Avdump-current-version}})
 
(22 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{TOCright}}
{{eyecatch|Warning|Avdump2 is deprecated; please use {{Avdump-current-version}}.}}
{{eyecatch|Important|Avdump2 fully replaces [[Avdump]], which is now deprecated and should not be used.}}
{{eyecatch|Important|Avdump2 fully replaces [[Avdump]], which is now deprecated and should not be used.}}
{{eyecatch|Important|[[Avdump_GUI|Avdump GUI]] is a GUI version of Avdump2, for command line skeptics.}}
Welcome to the remarkably sparse avdump2 wiki page, lovingly hand created over many minutes + some more.
Welcome to the remarkably sparse avdump2 wiki page, lovingly hand created over many minutes + some more.


We gleefully embrace build 6714, yet another 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.
We gleefully embrace build 7100, yet another public release of avd2. It runs against a new build of MediaInfoLibrary (18.12), 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.


There is no need to reprocess existing files with this build, but do keep an eye out for misbehaviour.
There is no general need to reprocess existing files with this build, but we don't mind if you do it anyway!


==What is it==
==What is it==
Line 20: Line 23:


===Download===
===Download===
  [http://static.anidb.net/client/avdump2/avdump2_6714.rar DOWNLOAD(RAR)] (Build 6714) MD5 = AA24AB7D28B41267D3F56A39909BE4EA
  [https://cdn.anidb.net/client/avdump2/avdump2_7100.zip DOWNLOAD(ZIP)] (Build 7100) MD5 = a1539a6139315a3c0f24113bb2d2853b
[https://cdn.anidb.net/client/avdump2/avdump2_7101.zip DOWNLOAD(ZIP)] (Build 7101) MD5 = 2ba27f6477e8f933b366da65a6a8fdc2


===Usage===
===Usage===
Line 161: Line 165:


{{eyecatch|Note|'''The ''udp_api_key'' is not your user password!!! see [[Avdump#Auto-creqing|Auto-creqing]] .}}
{{eyecatch|Note|'''The ''udp_api_key'' is not your user password!!! see [[Avdump#Auto-creqing|Auto-creqing]] .}}
==Auto-creqing==
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump2 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.
* 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.
* 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.
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer.
* It is possible to run more than one instance of Avdump2 at once, up to a maximum of ten. At the moment, ''only 10 sessions per ip are allowed by the server'', meaning the eleventh instance will terminate the first.
* 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.
==Avdump2 on Linux==
Thanks to Mono, Avdump2 runs natively on Linux as well. However, as most development effort goes into the Windows version and due to the heterogenity of Linux distributions, running Avdump2 on Linux isn’t as straightforward as running it on Windows. All Linux-related usage notes can be found on the [[Avdump2 on Linux]] page.


==Changes From Avdump Classic==
==Changes From Avdump Classic==
Line 197: Line 229:
   </Exceptions>
   </Exceptions>
  </FileExceptions>
  </FileExceptions>
===Avdump2 on Linux===
Thanks to Mono, Avdump2 runs natively on Linux as well. However, as most development effort goes into the Windows version and due to the heterogenity of Linux distributions, running Avdump2 on Linux isn’t as straightforward as running it on Windows. All Linux-related usage notes can be found on the [[Avdump2 on Linux]] page.
==Auto-creqing==
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump2 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 Avdump2 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.


==Known issues==
==Known issues==
Line 233: Line 237:
==Changelog==
==Changelog==
<div style="height: 280px; overflow: auto; padding: 3px; border:1px solid #AAAAAA; font-size: small">
<div style="height: 280px; overflow: auto; padding: 3px; border:1px solid #AAAAAA; font-size: small">
'''1.0.7101.0 : 2020.05.16'''
* Allow compressed dumps of up to 14kb
'''1.0.7100.0 : 2019.04.07'''
* Don't stop execution on big endian systems
* Warn when --ACreqErr is set but not --Auth
* Don't report DisplayBuffer, LC_ALL, ThreadCreation failed and console resize  exceptions
* Removed annoying error message when --Auth is not enabled
* Fixed MIL Versionstring
* MIL Chapter workaround
'''1.0.7080.0 : 2019.01.08'''
* Removed thrownOn Attribute from Exception reports
* Write ACreqErrors to Console
* Filter Exceptions which should be reported
* Donelog search is now case insensitive
* Fix for Matroskafiles when the tracks sections is at the end of the file
* Jaco Subtitle detection is now less trigger happy
'''1.0.7070.0 : 2019.01.02'''
* MIL Updated to Version 18.12
* Removed Client side MIL hash check
* Skip logging/acreqing for files with errors (except for matroska files with header data)
* EBML Parser (Matroska) crash fixed
* Matroska Container Parser Update
* Matroska Chapter Parsing
* Matroska Parser Crash fixed (Missing Track and other corner cases)
* Matroska: extra_size node added (Track overhead)
* 3d flag
* Added Mono Runtime Version to exception metadata
* Display "Hashing failed" instead of nothing if hashing fails for whatever reason
* Accept /? as parameter (same as --help)
* Included MAC MIL library for mostly untested mac support
* Added Dumpable extensions: trp
* Switch --Version also prints MIL Version
* Constrained TTH hash Thread to 4 instead of available corecount
* MIL Info shuffling for consistency
* Wait longer for MIL to return before hard crashing
* Fixed -m Crash
* MP4 Lag fixed / MIL Chapters bug workaround
* Switch --NoMediaInfoProvider (switch is ignored when acreqing)
* Don't eat cmd cursor on soft crash
* Log acreq failure when preconditions aren't met
* Added CodecFeatures node
* Various fileextension provider fixes
'''0.1.6714.0 : 2014.04.24'''
'''0.1.6714.0 : 2014.04.24'''
* Check for invalid usernames (to skip check prepend @)
* Check for invalid usernames (to skip check prepend @)
staff
1,114

edits

Navigation menu

MediaWiki spam blocked by CleanTalk.
MediaWiki spam blocked by CleanTalk.