546
edits
Release: Difference between revisions
m
→Possible tables
Epoximator (talk | contribs) |
Epoximator (talk | contribs) |
||
| Line 47: | Line 47: | ||
: I am not sure about that assumption of one file per ep. I.e. what happens with releases which have external subtitles? (We could of course use the file-file relations for that info.) How would you handle a case where a release contains files from multiple groups and one or more eps were actually subbed by more than one group? I.e. group A released 1-10 and group B released 1-3 and A&B released 11-12. That cached ep map mentioned earlier is not the status int2, right? Would releases need a name? Or would there be different "types" of releases? | : I am not sure about that assumption of one file per ep. I.e. what happens with releases which have external subtitles? (We could of course use the file-file relations for that info.) How would you handle a case where a release contains files from multiple groups and one or more eps were actually subbed by more than one group? I.e. group A released 1-10 and group B released 1-3 and A&B released 11-12. That cached ep map mentioned earlier is not the status int2, right? Would releases need a name? Or would there be different "types" of releases? | ||
: [[User:Exp|Exp]] 18:56, 8 July 2007 (UTC) | : [[User:Exp|Exp]] 18:56, 8 July 2007 (UTC) | ||
:# a release is supposed to represent one possible "pack" of files that covers an anime (to assist you when you're wondering what to get) and in that regard only one file per ep is needed. you usually don't watch several files of the same ep unless you want to compare (or is rewatching). so, using your example, we'd have to choose whether we want 1-3 from A or B in the "release". this could (and probably will) lead to some political issues, but in worst case two relases can be added; one with 1-3 A and one with 1-3 (as one file can be part of several releases). allowing several files per ep (disregarding subtitles and split files for now) breaks the initial idea of releases, although it would still solve most of the issues it was supposed to address. (on a side note; new versions of files would "push out" the old versions in a release. complete reencodes would be added as new releases). | :# a release is supposed to represent one possible "pack" of files that covers an anime (to assist you when you're wondering what to get) and in that regard only one file per ep is needed. you usually don't watch several files of the same ep unless you want to compare (or is rewatching). so, using your example, we'd have to choose whether we want 1-3 from A or B in the "release". this could (and probably will) lead to some political issues, but in worst case two relases can be added; one with 1-3 from A and one with 1-3 from B (as one file can be part of several releases). allowing several files per ep (disregarding subtitles and split files for now) breaks the initial idea of releases, although it would still solve most of the issues it was supposed to address. (on a side note; new versions of files would "push out" the old versions in a release. complete reencodes would be added as new releases). | ||
:#the cached ep map = eprange in animegrouptb, meaning eprange was based on that idea. | :#the cached ep map = eprange in animegrouptb, meaning eprange was based on that idea. | ||
:#releases would usually be addressed by group names, but could have both name and type too. the "other" bit is the alternative, meaning if a release needs some additional explaining it would go there. --[[User:Epoximator|Epoximator]] 13:11, 10 July 2007 (UTC) | :#releases would usually be addressed by group names, but could have both name and type too. the "other" bit is the alternative, meaning if a release needs some additional explaining it would go there. --[[User:Epoximator|Epoximator]] 13:11, 10 July 2007 (UTC) | ||