546
edits
Avdump: Difference between revisions
Jump to navigation
Jump to search
→Autocreqing
Epoximator (talk | contribs) |
Epoximator (talk | contribs) |
||
| Line 96: | Line 96: | ||
Avdump is now part of a new autocreqing system. Some more or less important notes: | Avdump is now part of a new autocreqing 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 password'' 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 password'' 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. | * 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 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. | |||
* It is possible to run more than one instance of avdump at once, but not more than | * 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 | |||
* 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. | ||
* You may dump files currently not in the db. The data is still stored and will be used later if/after the file is added. It might also be used for ''machine assisted file adding'' at some point. | * You may dump files currently not in the db. The data is still stored and will be used later if/after the file is added. It might also be used for ''machine assisted file adding'' at some point. | ||
| Line 107: | Line 106: | ||
** Audio files are too few and not considered important atm. | ** Audio files are too few and not considered important atm. | ||
** Nothing useful can be extracted from archives and subtitles (that I can think of). | ** Nothing useful can be extracted from archives and subtitles (that I can think of). | ||
===Processing DVD's=== | ===Processing DVD's=== | ||