Content:Files: Difference between revisions

→‎Version: https://anidb.net/c15725208
Tags: Mobile edit Mobile web edit
(→‎Version: https://anidb.net/c15725208)
Tags: Mobile edit Mobile web edit
Line 81: Line 81:
Sometimes the group makes mistakes and wants to correct them by releasing a second (third, fourth...) version, usually called ''v2'' (''v3, v4, ...''). This field is usually based on information in the file name (where no information normally means ''version 1'').
Sometimes the group makes mistakes and wants to correct them by releasing a second (third, fourth...) version, usually called ''v2'' (''v3, v4, ...''). This field is usually based on information in the file name (where no information normally means ''version 1'').


'''IMPORTANT''': Even if a group releases two files of the same episode it does not mean that the first has to be marked ''v1'' and the second has to be marked ''v2''. There are other reasons to do something like that other than correcting mistakes, such as: different source (DTV/DVD), different sub languages, dual audio vs single audio releases, high and low quality versions, etc.
'''IMPORTANT''': Even if a group releases two files of the same episode, it does not automatically mean that the first has to be marked ''v1'' and the second has to be marked ''v2''. There are other reasons to do something like that other than correcting mistakes, such as: different source (DTV/DVD), different sub languages, dual audio vs single audio releases, high and low quality versions, etc.


'''Discretion should be applied''' when "other reasons" are the cause of multiple releases. For example, if the group's intent is to release as a final product only a dual audio release, but they release a single audio release as a "v0" or "draft" version, then we should consider this single audio "draft" within the version continuity of any subsequent dual audio releases.  However, if the group's intent is to release as a final product both a single and dual audio release, do not combine the versioning continuity.
'''Discretion should be applied''' when "other reasons" are the cause of multiple releases.


{{eyecatch|Note|We generally do not consider resolution changes and source changes as version bumps. That being said, you are free to add a file comment, indicating a file is marked as v2 and intended to replace a certain file. For example: <pre>Labelled as v2 of https://anidb.net/f2030447</pre>}}
# Example, [Ohys-Raws] released three 720p HDTV rips for an entire 12 episode series: set 1 of rips using the TBS HDTV source, set 2 using the Tokyo MX source, and set 3 using the AT-X source, for a total of 12 × 3 = 36 HDTV 720p files released. All 3 source-based releases are v1 files, they are not v2 and v3 files of each other. Add file notes to distinguish the raw source.
# Example: [HorribleSubs] releases CrunchyRoll rips with 12 files in 480p www and 12 files in 720p www for a series total of 24 files, 2 www per episode. These 480p www and 720p www releases are v1 files, they are not v2 files of each other.
# Example: if the group's intent is to release as a final product only a dual audio release, but they release a single audio release as a "v0" or "draft" version, then we should consider this single audio "draft" within the version continuity of any subsequent dual audio releases.  However, if the group's intent is to release as a final product both a single and dual audio release, do not combine the versioning continuity.
 
{{eyecatch|Note|We generally do not consider different resolution releases and source changes as version bumps. That being said, you are free to add a file comment, indicating a file is marked as v2 and intended to replace a certain file. For example: <pre>Labelled as v2 of https://anidb.net/f2030447</pre>}}


===Other information===
===Other information===
staff
1,111

edits

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