mirror of
https://github.com/WhatCD/Gazelle.git
synced 2024-12-13 19:06:27 +00:00
Empty commit
This commit is contained in:
Git
parent
df412204f2
commit
7526a46c47
@ -62,12 +62,6 @@ class TEXT {
|
|||||||
* @var int $InQuotes
|
* @var int $InQuotes
|
||||||
*/
|
*/
|
||||||
private $InQuotes = 0;
|
private $InQuotes = 0;
|
||||||
|
|
||||||
/**
|
|
||||||
* Used to [hide] quote trains beyond the specified depth
|
|
||||||
* @var int $QuoteHideDepth
|
|
||||||
*/
|
|
||||||
private $QuoteHideDepth = 5;
|
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* Array of headlines for Table Of Contents (TOC)
|
* Array of headlines for Table Of Contents (TOC)
|
||||||
@ -690,24 +684,17 @@ private function to_html ($Array) {
|
|||||||
case 'quote':
|
case 'quote':
|
||||||
$this->NoImg++; // No images inside quote tags
|
$this->NoImg++; // No images inside quote tags
|
||||||
$this->InQuotes++;
|
$this->InQuotes++;
|
||||||
if($this->InQuotes == $this->QuoteHideDepth) { //Put quotes that are nested beyond the specified limit in [hide] tags.
|
|
||||||
$Str.='<strong>Older quotes</strong>: <a href="javascript:void(0);" onclick="BBCode.spoiler(this);">Show</a>';
|
|
||||||
$Str.='<blockquote class="hidden spoiler">';
|
|
||||||
}
|
|
||||||
if(!empty($Block['Attr'])) {
|
if(!empty($Block['Attr'])) {
|
||||||
$Exploded = explode("|", $this->to_html($Block['Attr']));
|
$Exploded = explode("|", $this->to_html($Block['Attr']));
|
||||||
if(isset($Exploded[1]) && is_numeric($Exploded[1])) {
|
if(isset($Exploded[1]) && is_numeric($Exploded[1])) {
|
||||||
$PostID = trim($Exploded[1]);
|
$PostID = trim($Exploded[1]);
|
||||||
$Str.= '<a href="#" onclick="QuoteJump('.$PostID.'); return false;"><strong class="quoteheader">'.$Exploded[0].'</strong> wrote: </a>';
|
$Str.= '<a href="#" onclick="QuoteJump('.$PostID.'); return false;"><strong class="quoteheader">'.$Exploded[0].'</strong> wrote: </a>';
|
||||||
}
|
}
|
||||||
else {
|
else {
|
||||||
$Str.= '<strong class="quoteheader">'.$Exploded[0].'</strong> wrote: ';
|
$Str.= '<strong class="quoteheader">'.$Exploded[0].'</strong> wrote: ';
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
$Str.='<blockquote>'.$this->to_html($Block['Val']).'</blockquote>';
|
$Str.='<blockquote>'.$this->to_html($Block['Val']).'</blockquote>';
|
||||||
if($this->InQuotes == $this->QuoteHideDepth) { //Close quote the deeply nested quote [hide].
|
|
||||||
$Str.='</blockquote><br />'; // Ensure new line after quote train hiding
|
|
||||||
}
|
|
||||||
$this->NoImg--;
|
$this->NoImg--;
|
||||||
$this->InQuotes--;
|
$this->InQuotes--;
|
||||||
break;
|
break;
|
||||||
|
|||||||
@ -153,6 +153,7 @@
|
|||||||
}
|
}
|
||||||
*/
|
*/
|
||||||
|
|
||||||
|
// Start printing
|
||||||
View::show_header($ThreadInfo['Title'] . ' < '.$Forums[$ForumID]['Name'].' < '. 'Forums','comments,subscriptions,bbcode,jquery');
|
View::show_header($ThreadInfo['Title'] . ' < '.$Forums[$ForumID]['Name'].' < '. 'Forums','comments,subscriptions,bbcode,jquery');
|
||||||
?>
|
?>
|
||||||
<div class="thin">
|
<div class="thin">
|
||||||
|
|||||||
@ -230,8 +230,8 @@
|
|||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li id="r2.1.24"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.24">2.1.24.</a> <strong>Lossy AAC torrents may only be uploaded when they represent exclusive content not currently available in any other format (e.g., an iTunes WEB exclusive release).</strong> </li>
|
<li id="r2.1.24"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.24">2.1.24.</a> <strong>Lossy AAC torrents may only be uploaded when they represent exclusive content not currently available in any other format (e.g., an iTunes WEB exclusive release).</strong> </li>
|
||||||
<li id="r2.1.25"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.25">2.1.25.</a> <strong>No HDCD content may be uploaded to the site.</strong> There are inherent problems with ripping this format, and other forms of high-resolution audio are both more prevalent and preferred at this time (e.g., vinyl, SACD, Blu-ray, etc.). Any CD bearing the HDCD logo can still be ripped using the usual methods for ripping normal audio CDs. See <a href="wiki.php?action=article&id=875">this wiki</a> for more details on the media format.</li>
|
<li id="r2.1.25"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.25">2.1.25.</a> <strong>No HDCD content may be uploaded to the site.</strong> There are inherent problems with ripping this format, and other forms of high-resolution audio are both more prevalent and preferred at this time (e.g., vinyl, SACD, Blu-ray, etc.). Any CD bearing the HDCD logo can still be ripped using the usual methods for ripping normal audio CDs. See <a href="wiki.php?action=article&id=875">this wiki</a> for more details on the media format.</li>
|
||||||
<li id="r2.1.26"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.26">2.1.26.</a> <strong> Downsampling of digital sources is allowed for certain media types.</strong> Downsampling of CD sources is strictly prohibited. Downsampling of WEB sources is allowed for audio files sampled at 88.2 kHz and above. If the WEB source is already sampled at a rate of either 44.1 kHz or 48 kHz you may not downsample the audio files any further. Downsampling of SACD, DVD, or Blu-ray sources is allowed in certain cases. See <a href="#r2.8.5">2.8.5</a>, <a href="#r2.7.3">2.7.3</a>, and <a href="#r2.9.5">2.9.5</a> for more information.</li>
|
<li id="r2.1.26"><a href="#h2.1"><strong>↑_</strong></a> <a href="#r2.1.26">2.1.26.</a> <strong> Downsampling of digital sources is allowed for certain media types.</strong> Downsampling of CD sources is strictly prohibited. Downsampling of WEB sources is allowed for audio files sampled at 88.2 kHz and above. If the WEB source is already sampled at a rate of either 44.1 kHz or 48 kHz you may not downsample the audio files any further. Downsampling of SACD, DVD, or Blu-ray sources is allowed in certain cases. See <a href="#r2.8.5">2.8.5</a>, <a href="#r2.7.3">2.7.3</a>, and <a href="#r2.9.5">2.9.5</a> for more information.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
<h5 id="h2.2"><a href="#h2.2k"><strong>↑</strong></a> <a href="#h2.2">2.2.</a> Duplicates & Trumping</h5>
|
<h5 id="h2.2"><a href="#h2.2k"><strong>↑</strong></a> <a href="#h2.2">2.2.</a> Duplicates & Trumping</h5>
|
||||||
@ -287,7 +287,7 @@
|
|||||||
<li id="r2.2.10.6.3"><a href="#r2.2.10.6"><strong>↑_</strong></a> <a href="#r2.2.10.6.3">2.2.10.6.3.</a> <strong>The CD image rip must be split with <a href="http://www.cuetools.net/wiki/CUETools">CUETools</a>, <a href="http://tmkk.pv.land.to/xld/index_e.html">XLD</a>, or <a href="http://www.exactaudiocopy.de/">EAC</a>.</strong> No other splitter is acceptable for a score adjustment. You will not receive a score adjustment for copy-only range rips approved with AccurateRip, nor for range rips done with test and copy without AccurateRip enabled. See <a href="wiki.php?action=article&id=111">this wiki</a> for information on splitting image rips with <a href="http://www.exactaudiocopy.de/">EAC</a>.</li>
|
<li id="r2.2.10.6.3"><a href="#r2.2.10.6"><strong>↑_</strong></a> <a href="#r2.2.10.6.3">2.2.10.6.3.</a> <strong>The CD image rip must be split with <a href="http://www.cuetools.net/wiki/CUETools">CUETools</a>, <a href="http://tmkk.pv.land.to/xld/index_e.html">XLD</a>, or <a href="http://www.exactaudiocopy.de/">EAC</a>.</strong> No other splitter is acceptable for a score adjustment. You will not receive a score adjustment for copy-only range rips approved with AccurateRip, nor for range rips done with test and copy without AccurateRip enabled. See <a href="wiki.php?action=article&id=111">this wiki</a> for information on splitting image rips with <a href="http://www.exactaudiocopy.de/">EAC</a>.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li id="r2.2.10.7"><a href="#r2.2.10"><strong>↑_</strong></a> <a href="#r2.2.10.7">2.2.10.7.</a> <strong>A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet.</strong> See <a href="wiki.php?action=article&id=168">this wiki</a> for more information on cue sheets.
|
<li id="r2.2.10.7"><a href="#r2.2.10"><strong>↑_</strong></a> <a href="#r2.2.10.7">2.2.10.7.</a> <strong>A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet.</strong> See <a href="wiki.php?action=article&id=168">this wiki</a> for more information on cue sheets.
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.2.10.7.1"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.1">2.2.10.7.1.</a> <strong>A 100% log rip without a cue sheet can be replaced by a 100% log rip with a noncompliant cue sheet ONLY when the included cue sheet is materially different from "a cue generated from the ripping log." Examples of a material difference include additional or correct indices, properly detected pre-gap lengths, and <a href="wiki.php?action=article&id=386">pre-emphasis</a> flags.</strong> If you upload a torrent with a cue sheet that provides nothing additional beyond what is contained in the rip log of the preexisting torrent, it will be deleted as a dupe.</li>
|
<li id="r2.2.10.7.1"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.1">2.2.10.7.1.</a> <strong>A 100% log rip without a cue sheet can be replaced by a 100% log rip with a noncompliant cue sheet ONLY when the included cue sheet is materially different from "a cue generated from the ripping log." Examples of a material difference include additional or correct indices, properly detected pre-gap lengths, and <a href="wiki.php?action=article&id=386">pre-emphasis</a> flags.</strong> If you upload a torrent with a cue sheet that provides nothing additional beyond what is contained in the rip log of the preexisting torrent, it will be deleted as a dupe.</li>
|
||||||
<li id="r2.2.10.7.2"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.2">2.2.10.7.2.</a> <strong>Exceptions: An <a href="http://www.exactaudiocopy.de/">EAC</a> 0.95 rip with a 100% log and no cue file, uploaded before September 14, 2010, may be trumped by a torrent that scores 100% under the current log checker requirements.</strong> </li>
|
<li id="r2.2.10.7.2"><a href="#r2.2.10.7"><strong>↑_</strong></a> <a href="#r2.2.10.7.2">2.2.10.7.2.</a> <strong>Exceptions: An <a href="http://www.exactaudiocopy.de/">EAC</a> 0.95 rip with a 100% log and no cue file, uploaded before September 14, 2010, may be trumped by a torrent that scores 100% under the current log checker requirements.</strong> </li>
|
||||||
@ -341,31 +341,32 @@
|
|||||||
<li id="r2.3.12"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.12">2.3.12.</a> <strong>The maximum character length for audio files is 180 characters.</strong> Path length values must not be so long that they cause incompatibility problems with operating systems and media players. For example, "My Artist Name - My Album Name (2012) - FLAC/01 - Long Track Name for the First Track.flac" is a typical torrent folder that contains the audio files. This path name consists of 91 characters. As of September 01, 2012, new torrents will be trumpable if their path lengths exceed 180 characters. This limit includes the number of characters in the main torrent folder (in this case, 46 characters) and any sub-folders and audio files within that torrent folder. For example, unnecessary nested folders will count towards this limit; and lengthy classical music file names will count towards this limit. Torrents that were uploaded prior to September 01, 2012 with character lengths that are longer than 180 characters may remain on the site. However, torrents with exceedingly long path lengths will only remain on the site at the discretion of staff.</li>
|
<li id="r2.3.12"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.12">2.3.12.</a> <strong>The maximum character length for audio files is 180 characters.</strong> Path length values must not be so long that they cause incompatibility problems with operating systems and media players. For example, "My Artist Name - My Album Name (2012) - FLAC/01 - Long Track Name for the First Track.flac" is a typical torrent folder that contains the audio files. This path name consists of 91 characters. As of September 01, 2012, new torrents will be trumpable if their path lengths exceed 180 characters. This limit includes the number of characters in the main torrent folder (in this case, 46 characters) and any sub-folders and audio files within that torrent folder. For example, unnecessary nested folders will count towards this limit; and lengthy classical music file names will count towards this limit. Torrents that were uploaded prior to September 01, 2012 with character lengths that are longer than 180 characters may remain on the site. However, torrents with exceedingly long path lengths will only remain on the site at the discretion of staff.</li>
|
||||||
<li id="r2.3.13"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.13">2.3.13.</a> <strong>Track numbers are required in file names (e.g., "01 - TrackName.mp3").</strong> If a torrent without track numbers in the file names is uploaded, then a torrent with the track numbers in the file names can take its place. When formatted properly, file names will sort in order by track number or playing order. Also see <a href="#r2.3.14">2.3.14</a>. Exception: Track numbers are not required for single-track torrents.</li>
|
<li id="r2.3.13"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.13">2.3.13.</a> <strong>Track numbers are required in file names (e.g., "01 - TrackName.mp3").</strong> If a torrent without track numbers in the file names is uploaded, then a torrent with the track numbers in the file names can take its place. When formatted properly, file names will sort in order by track number or playing order. Also see <a href="#r2.3.14">2.3.14</a>. Exception: Track numbers are not required for single-track torrents.</li>
|
||||||
<li id="r2.3.14"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.14">2.3.14.</a> <strong>When formatted properly, file names will alphabetically sort into the original playing order of the release.</strong>
|
<li id="r2.3.14"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.14">2.3.14.</a> <strong>When formatted properly, file names will alphabetically sort into the original playing order of the release.</strong>
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.3.14.1"><a href="#r2.3.14"><strong>↑_</strong></a> <a href="#r2.3.14.1">2.3.14.1.</a><strong>For albums with more than one artist, if the name of the artist is in the filename, it must come after the track number in order for the tracks to sort into the correct order.</strong> For example, "01 U2 - Where the Streets Have No Name.flac" is a properly formatted file name for a multiple-artist album. "U2 - 01 - Where the Streets Have No Name.mp3" is not correct in the context of a compilation album because the resultant file list will sort in alphabetical order by artist rather than by numerical track number. <strong>Note:</strong> there is no requirement for artist names to be in the track filenames, other than <a href="#r2.3.16.2">2.3.16.2.</a> Torrents that have improperly-formatted or incomplete file names will be trumpable.</li>
|
<li id="r2.3.14.1"><a href="#r2.3.14"><strong>↑_</strong></a> <a href="#r2.3.14.1">2.3.14.1.</a><strong>For albums with more than one artist, if the name of the artist is in the filename, it must come after the track number in order for the tracks to sort into the correct order.</strong> For example, "01 U2 - Where the Streets Have No Name.flac" is a properly formatted file name for a multiple-artist album. "U2 - 01 - Where the Streets Have No Name.mp3" is not correct in the context of a compilation album because the resultant file list will sort in alphabetical order by artist rather than by numerical track number. <strong>Note:</strong> there is no requirement for artist names to be in the track filenames, other than <a href="#r2.3.16.2">2.3.16.2.</a> Torrents that have improperly-formatted or incomplete file names will be trumpable.</li>
|
||||||
<li id="r2.3.14.2"><a href="#r2.3.14"><strong>↑_</strong></a> <a href="#r2.3.14.2">2.3.14.2.</a><strong>If a torrent has subfolders for multiple discs of a release, these subfolders must sort by disc order.</strong> If each disc has a title (<a href="torrents.php?id=62329">torrents.php?id=62329</a>, for example) and the discs are not numbered, this rule does not apply, and each subdirectory should have the disc name included.</li>
|
<li id="r2.3.14.2"><a href="#r2.3.14"><strong>↑_</strong></a> <a href="#r2.3.14.2">2.3.14.2.</a><strong>If a torrent has subfolders for multiple discs of a release, these subfolders must sort by disc order.</strong> If each disc has a title (<a href="torrents.php?id=62329">torrents.php?id=62329</a>, for example) and the discs are not numbered, this rule does not apply, and each subdirectory should have the disc name included.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li id="r2.3.15"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.15">2.3.15.</a> <strong>Multiple-disc torrents cannot have tracks with the same numbers in one directory.</strong> You may place all the tracks for Disc One in one directory and all the tracks for Disc Two in another directory. If you prefer to use one directory for all the audio files, you must use successive numbering. For example, Disc One has 15 tracks and Disc Two has 20. You may either number tracks in Disc One as #01-#15 and those of Disc Two as #16-#35 in the same directory, or you may add a Disc number before the track numbers such that the numbers are #1 06 for Disc One Track 06, and #2 03 for Disc 2 Track 03, and so forth.</li>
|
<li id="r2.3.15"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.15">2.3.15.</a> <strong>Multiple-disc torrents cannot have tracks with the same numbers in one directory.</strong> You may place all the tracks for Disc One in one directory and all the tracks for Disc Two in another directory. If you prefer to use one directory for all the audio files, you must use successive numbering. For example, Disc One has 15 tracks and Disc Two has 20. You may either number tracks in Disc One as #01-#15 and those of Disc Two as #16-#35 in the same directory, or you may add a Disc number before the track numbers such that the numbers are #1 06 for Disc One Track 06, and #2 03 for Disc 2 Track 03, and so forth.</li>
|
||||||
<li id="r2.3.16"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.16">2.3.16.</a> <strong>Properly tag your music files.</strong>
|
<li id="r2.3.16"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.16">2.3.16.</a> <strong>Properly tag your music files.</strong>
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.3.16.1"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.1">2.3.16.1.</a>Certain meta tags (e.g., ID3, Vorbis) are required on all music uploads. Make sure to use the proper format tags for your files (e.g., no ID3 tags for FLAC - see <a href="#r2.2.10.8">2.2.10.8</a>. ID3v2 tags for files are highly recommended over ID3v1.</li>
|
<li id="r2.3.16.1"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.1">2.3.16.1.</a>Certain meta tags (e.g., ID3, Vorbis) are required on all music uploads. Make sure to use the proper format tags for your files (e.g., no ID3 tags for FLAC - see <a href="#r2.2.10.8">2.2.10.8</a>. ID3v2 tags for files are highly recommended over ID3v1.</li>
|
||||||
<li id="r2.3.16.2"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.2">2.3.16.2.</a>ID3 tags are recommended for AC3 torrents, but are not mandatory because the format does not natively support file metadata tagging (for AC3, the file names become the vehicle for correctly labeling media files). Because of this lack of support, the Album and Artist information must be included in the torrent folder for AC3 and DTS files. In addition, the Track Number and Track Title information must be included in the file names for AC3 and DTS files; for various artists compilations, the Track Artist must be included in the file names as well. ensuring that they also satisfy <a href="#r2.3.14">2.3.14.</a></li>
|
<li id="r2.3.16.2"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.2">2.3.16.2.</a>ID3 tags are recommended for AC3 torrents, but are not mandatory because the format does not natively support file metadata tagging (for AC3, the file names become the vehicle for correctly labeling media files). Because of this lack of support, the Album and Artist information must be included in the torrent folder for AC3 and DTS files. In addition, the Track Number and Track Title information must be included in the file names for AC3 and DTS files; for various artists compilations, the Track Artist must be included in the file names as well. ensuring that they also satisfy <a href="#r2.3.14">2.3.14.</a></li>
|
||||||
<li id="r2.3.16.3"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.3">2.3.16.3.</a>Torrents uploaded with both good ID3v1 tags and blank ID3v2 tags (a dual set of tags) are trumpable by torrents with either just good ID3v1 tags or good ID3v2 tags (a single set of tags). See <a href="wiki.php?action=article&id=170">this wiki</a> for more information on ID3 tags.</li>
|
<li id="r2.3.16.3"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.3">2.3.16.3.</a>Torrents uploaded with both good ID3v1 tags and blank ID3v2 tags (a dual set of tags) are trumpable by torrents with either just good ID3v1 tags or good ID3v2 tags (a single set of tags). See <a href="wiki.php?action=article&id=170">this wiki</a> for more information on ID3 tags.</li>
|
||||||
<li id="r2.3.16.4"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.4">2.3.16.4.</a>If you upload an album missing one or more of the required tags, then another user may add the tags, re-upload, and report your torrent for deletion. The required tags are:
|
<li id="r2.3.16.4"><a href="#r2.3.16"><strong>↑_</strong></a> <a href="#r2.3.16.4">2.3.16.4.</a>If you upload an album missing one or more of the required tags, then another user may add the tags, re-upload, and report your torrent for deletion. The required tags are:
|
||||||
<ul>
|
<ul>
|
||||||
<li>Artist</li>
|
<li>Artist</li>
|
||||||
<li>Album</li>
|
<li>Album</li>
|
||||||
<li>Title</li>
|
<li>Title</li>
|
||||||
<li>Track Number</li>
|
<li>Track Number</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
<span style="font-style: italic;">Note: The "Year" tag is optional, but strongly encouraged. However, if missing or incorrect, this is not grounds for trumping a torrent.</span>
|
<span style="font-style: italic;">Note: The "Year" tag is optional, but strongly encouraged. However, if missing or incorrect, this is not grounds for trumping a torrent.</span>
|
||||||
</li>
|
</li>
|
||||||
<li id="r2.3.17"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.17">2.3.17.</a> <strong>The torrent artist for classical works should use the full composer name.</strong> Before uploading see <a href="wiki.php?action=article&id=700">this wiki</a> for guidelines on uploading classical music torrents. Also, consult <a href="wiki.php?action=article&id=691">this wiki</a> for a full explanation of the classical music tagging system.</li>
|
<li id="r2.3.17"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.17">2.3.17.</a> <strong>The torrent artist for classical works should use the full composer name.</strong> Before uploading see <a href="wiki.php?action=article&id=700">this wiki</a> for guidelines on uploading classical music torrents. Also, consult <a href="wiki.php?action=article&id=691">this wiki</a> for a full explanation of the classical music tagging system.</li>
|
||||||
<li id="r2.3.18"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.18">2.3.18.</a> <strong>Newly re-tagged torrents trumping badly tagged torrents must reflect a substantial improvement over the previous tags.</strong> Small changes that include replacing ASCII characters with proper foreign language characters with diacritical marks, fixing slight misspellings, or missing an alternate spelling of an artist (e.g., excluding "The" before a band name) are insufficient grounds for replacing other torrents. Artist names that are misspelled in the tags are grounds for trumping; this includes character accents and characters that mean one letter in one language and a different letter in another language. Improper capitalization in the tags is grounds for trumping; this includes artist tags (or composer tags) that contain names that are all capitalized or track titles that are all capitalized. Tags with multiple entries in the same tag (e.g., track number and track title in the track title tags; or track number, artist, and track title in the artist tags) are subject to trumping. You may trump a release if the tags do not follow the data from a reputable music cataloguing service such as <a href="http://musicbrainz.org/">Musicbrainz</a> or <a href="http://www.discogs.com/">Discogs</a>. In the case of a conflict between reputable listings, either tagged version is equally preferred on the site and cannot trump the other. For example, an album is tagged differently in <a href="http://musicbrainz.org/">Musicbrainz</a> and in <a href="http://www.discogs.com/">Discogs</a>. Either style of tagging is permitted; neither is "better" than the other. In that case, any newly tagged torrents replacing an already properly tagged torrent, which follows good tagging convention, will result in a dupe. Note: For classical music, please follow these <a href="wiki.php?action=article&id=691">tagging guidelines</a>.</li>
|
<li id="r2.3.18"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.18">2.3.18.</a> <strong>Newly re-tagged torrents trumping badly tagged torrents must reflect a substantial improvement over the previous tags.</strong> Small changes that include replacing ASCII characters with proper foreign language characters with diacritical marks, fixing slight misspellings, or missing an alternate spelling of an artist (e.g., excluding "The" before a band name) are insufficient grounds for replacing other torrents. Artist names that are misspelled in the tags are grounds for trumping; this includes character accents and characters that mean one letter in one language and a different letter in another language. Improper capitalization in the tags is grounds for trumping; this includes artist tags (or composer tags) that contain names that are all capitalized or track titles that are all capitalized. Tags with multiple entries in the same tag (e.g., track number and track title in the track title tags; or track number, artist, and track title in the artist tags) are subject to trumping. You may trump a release if the tags do not follow the data from a reputable music cataloguing service such as <a href="http://musicbrainz.org/">Musicbrainz</a> or <a href="http://www.discogs.com/">Discogs</a>. In the case of a conflict between reputable listings, either tagged version is equally preferred on the site and cannot trump the other. For example, an album is tagged differently in <a href="http://musicbrainz.org/">Musicbrainz</a> and in <a href="http://www.discogs.com/">Discogs</a>. Either style of tagging is permitted; neither is "better" than the other. In that case, any newly tagged torrents replacing an already properly tagged torrent, which follows good tagging convention, will result in a dupe. Note: For classical music, please follow these <a href="wiki.php?action=article&id=691">tagging guidelines</a>.</li>
|
||||||
<li id="r2.3.19"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.19">2.3.19.</a> <strong>Avoid embedding large images if including cover art in the meta tags.</strong> Do not embed large images (in excess of 512 KB) in the file meta tags. It adds unnecessary bloat to the files. Include the artwork in a separate directory if it is too big or if it consists of high-resolution images. Should you include an image of over 512 KB as embedded artwork, your torrent will be trumpable.</li>
|
<li id="r2.3.19"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.19">2.3.19.</a> <strong>Avoid embedding large images if including cover art in the meta tags.</strong> Do not embed large images (in excess of 512 KB) in the file meta tags. It adds unnecessary bloat to the files. Include the artwork in a separate directory if it is too big or if it consists of high-resolution images. Should you include an image of over 512 KB as embedded artwork, your torrent will be trumpable.</li>
|
||||||
|
<li id="r2.3.20"><a href="#h2.3"><strong>↑_</strong></a> <a href="#r2.3.20">2.3.20.</a> <strong>Leading spaces are not allowed in any file or folder names.</strong> Leading spaces cause usability and interoperability problems among various operating systems and programs. Torrents with file or folder names that contain leading space characters are trumpable.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
<h5 id="h2.4"><a href="#h2.4k"><strong>↑</strong></a> <a href="#h2.4">2.4.</a> Bonus Content</h5>
|
<h5 id="h2.4"><a href="#h2.4k"><strong>↑</strong></a> <a href="#h2.4">2.4.</a> Bonus Content</h5>
|
||||||
@ -460,8 +461,8 @@
|
|||||||
<li>Collection of random live tracks from multiple artists</li>
|
<li>Collection of random live tracks from multiple artists</li>
|
||||||
<li>Collection of remixed live tracks</li>
|
<li>Collection of remixed live tracks</li>
|
||||||
<li>Radio broadcast of a live performance</li>
|
<li>Radio broadcast of a live performance</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
@ -498,8 +499,8 @@
|
|||||||
<li id="r2.8.5"><a href="#h2.8"><strong>↑_</strong></a> <a href="#r2.8.5">2.8.5.</a> <strong> Downsampling of SACD sources is allowed in certain cases.</strong>
|
<li id="r2.8.5"><a href="#h2.8"><strong>↑_</strong></a> <a href="#r2.8.5">2.8.5.</a> <strong> Downsampling of SACD sources is allowed in certain cases.</strong>
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.8.5.1"><a href="#r2.8.5"><strong>↑_</strong></a> <a href="#r2.8.5.1">2.8.5.1.</a> <strong> A multichannel lossless rip must have the same number of and arrangement of channels as the source media.</strong> In addition, the rip must be encoded at the same bit depth and sampling rate as the original stream. Downsampled versions of the original source material may be trumped by a torrent containing audio files ripped directly from the disc at the bit depth and sampling rate originally found on disc. For example, there is a 192 kHz track and a 44.1 kHz track on the SACD. A user uploads only the 192 kHz track and that source is subsequently downsampled to 44.1 kHz. Another user who rips the actual 44.1 kHz track from the original disc may trump the downsampled torrent.</li>
|
<li id="r2.8.5.1"><a href="#r2.8.5"><strong>↑_</strong></a> <a href="#r2.8.5.1">2.8.5.1.</a> <strong> A multichannel lossless rip must have the same number of and arrangement of channels as the source media.</strong> In addition, the rip must be encoded at the same bit depth and sampling rate as the original stream. Downsampled versions of the original source material may be trumped by a torrent containing audio files ripped directly from the disc at the bit depth and sampling rate originally found on disc. For example, there is a 192 kHz track and a 44.1 kHz track on the SACD. A user uploads only the 192 kHz track and that source is subsequently downsampled to 44.1 kHz. Another user who rips the actual 44.1 kHz track from the original disc may trump the downsampled torrent.</li>
|
||||||
<li id="r2.8.5.2"><a href="#r2.8.5"><strong>↑_</strong></a> <a href="#r2.8.5.2">2.8.5.2.</a> <strong>Downmixing of SACD sources is prohibited.</strong> Do not downmix a 5.1 (or higher) channel mix to stereo and upload the resulting audio files. You may still downconvert lossless audio sources from 24-bit to 16-bit.</li>
|
<li id="r2.8.5.2"><a href="#r2.8.5"><strong>↑_</strong></a> <a href="#r2.8.5.2">2.8.5.2.</a> <strong>Downmixing of SACD sources is prohibited.</strong> Do not downmix a 5.1 (or higher) channel mix to stereo and upload the resulting audio files. You may still downconvert lossless audio sources from 24-bit to 16-bit.</li>
|
||||||
<li id="r2.8.5.3"><a href="#r2.8.5"><strong>↑_</strong></a> <a href="#r2.8.5.3">2.8.5.3.</a> <strong> All lossy SACD torrents must be uploaded in a Redbook-compliant form.</strong> Any stereo lossless sources must be downconverted to 16 bits and downsampled to 44.1 kHz before they are transcoded to lossy MP3 formats. No other bit depth or sampling rate is allowed for lossy SACD torrents.</li>
|
<li id="r2.8.5.3"><a href="#r2.8.5"><strong>↑_</strong></a> <a href="#r2.8.5.3">2.8.5.3.</a> <strong> All lossy SACD torrents must be uploaded in a Redbook-compliant form.</strong> Any stereo lossless sources must be downconverted to 16 bits and downsampled to 44.1 kHz before they are transcoded to lossy MP3 formats. No other bit depth or sampling rate is allowed for lossy SACD torrents.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
@ -507,8 +508,8 @@
|
|||||||
<h5 id="h2.9"><a href="#h2.9k"><strong>↑</strong></a> <a href="#h2.9">2.9.</a> Blu-ray</h5>
|
<h5 id="h2.9"><a href="#h2.9k"><strong>↑</strong></a> <a href="#h2.9">2.9.</a> Blu-ray</h5>
|
||||||
<div class="box pad" style="padding:10px 10px 10px 20px;">
|
<div class="box pad" style="padding:10px 10px 10px 20px;">
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.9.1"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.1">2.9.1.</a> <strong>Only digital rips of the lossless audio track from a Blu-ray disc may be uploaded (see <a href="wiki.php?action=article&id=926">this wiki</a> and <a href="wiki.php?action=article&id=854">this wiki</a> for more information).</strong> Analog Blu-ray rips are forbidden. Blu-ray discs may contain all of the following formats: Dolby Digital (AC3), DTS, Dolby Digital Plus (AC3), DTS-HD, PCM, Dolby TrueHD, DTS-HD Master Audio. Only PCM, Dolby TrueHD, and DTS-HD Master Audio contain truly lossless audio material on the Blu-ray disc. See <a href="#r2.1.1">2.1.1</a> and <a href="#r2.7.1">2.7.1 </a> for more information on multichannel audio material on the site.</li>
|
<li id="r2.9.1"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.1">2.9.1.</a> <strong>Only digital rips of the lossless audio track from a Blu-ray disc may be uploaded (see <a href="wiki.php?action=article&id=926">this wiki</a> and <a href="wiki.php?action=article&id=854">this wiki</a> for more information).</strong> Analog Blu-ray rips are forbidden. Blu-ray discs may contain all of the following formats: Dolby Digital (AC3), DTS, Dolby Digital Plus (AC3), DTS-HD, PCM, Dolby TrueHD, DTS-HD Master Audio. Only PCM, Dolby TrueHD, and DTS-HD Master Audio contain truly lossless audio material on the Blu-ray disc. See <a href="#r2.1.1">2.1.1</a> and <a href="#r2.7.1">2.7.1 </a> for more information on multichannel audio material on the site.</li>
|
||||||
<li id="r2.9.2"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.2">2.9.2.</a> <strong> Uploading movie audio tracks is prohibited.</strong> For example, the Inception Blu-ray disc set features a DTS-HD Master Audio 5.1 surround sound track for the entire movie, which cannot be uploaded, and a DTS-HD Master Audio 5.1 surround sound mix of the movie soundtrack, which can be uploaded. Uploading movie audio tracks will result in a warning and the loss of your uploading privileges.</li>
|
<li id="r2.9.2"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.2">2.9.2.</a> <strong> Uploading movie audio tracks is prohibited.</strong> For example, the Inception Blu-ray disc set features a DTS-HD Master Audio 5.1 surround sound track for the entire movie, which cannot be uploaded, and a DTS-HD Master Audio 5.1 surround sound mix of the movie soundtrack, which can be uploaded. Uploading movie audio tracks will result in a warning and the loss of your uploading privileges.</li>
|
||||||
<li id="r2.9.3"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.3">2.9.3.</a> <strong> Blu-ray rip sources must be properly labeled.</strong>
|
<li id="r2.9.3"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.3">2.9.3.</a> <strong> Blu-ray rip sources must be properly labeled.</strong>
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.9.3.1"><a href="#r2.9.3"><strong>↑_</strong></a> <a href="#r2.9.3.1">2.9.3.1.</a> <strong> If the source was lossy (e.g., AC3 or DTS) do not transcode to other formats.</strong> </li>
|
<li id="r2.9.3.1"><a href="#r2.9.3"><strong>↑_</strong></a> <a href="#r2.9.3.1">2.9.3.1.</a> <strong> If the source was lossy (e.g., AC3 or DTS) do not transcode to other formats.</strong> </li>
|
||||||
@ -517,15 +518,15 @@
|
|||||||
</li>
|
</li>
|
||||||
<li id="r2.9.4"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.4">2.9.4.</a> <strong>Lineage information for a Blu-ray transfer is required and should be included in the torrent folder.</strong>
|
<li id="r2.9.4"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.4">2.9.4.</a> <strong>Lineage information for a Blu-ray transfer is required and should be included in the torrent folder.</strong>
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.9.4.1"><a href="#r2.9.4"><strong>↑_</strong></a> <a href="#r2.9.4.1">2.9.4.1.</a> <strong> All Blu-ray rips require lineage information that includes the identity of the Blu-ray source, any software used for ripping and encoding, disc drive and other equipment used, and details of the transfer process.</strong> Any torrents that lack this lineage information are trumpable.</li>
|
<li id="r2.9.4.1"><a href="#r2.9.4"><strong>↑_</strong></a> <a href="#r2.9.4.1">2.9.4.1.</a> <strong> All Blu-ray rips require lineage information that includes the identity of the Blu-ray source, any software used for ripping and encoding, disc drive and other equipment used, and details of the transfer process.</strong> Any torrents that lack this lineage information are trumpable.</li>
|
||||||
<li id="r2.9.4.2"><a href="#r2.9.4"><strong>↑_</strong></a> <a href="#r2.9.4.2">2.9.4.2.</a> <strong>No lineage editing or misrepresentation will be tolerated.</strong> Doing so will result in the loss of upload privileges. If you are unsure of a lineage, then do not provide it. Do NOT guess.</li>
|
<li id="r2.9.4.2"><a href="#r2.9.4"><strong>↑_</strong></a> <a href="#r2.9.4.2">2.9.4.2.</a> <strong>No lineage editing or misrepresentation will be tolerated.</strong> Doing so will result in the loss of upload privileges. If you are unsure of a lineage, then do not provide it. Do NOT guess.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li id="r2.9.5"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.5">2.9.5.</a> <strong> Downsampling of Blu-ray sources is allowed in certain cases.</strong>
|
<li id="r2.9.5"><a href="#h2.9"><strong>↑_</strong></a> <a href="#r2.9.5">2.9.5.</a> <strong> Downsampling of Blu-ray sources is allowed in certain cases.</strong>
|
||||||
<ul>
|
<ul>
|
||||||
<li id="r2.9.5.1"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.1">2.9.5.1.</a> <strong> A multichannel lossless rip must have the same number of and arrangement of channels as the source media.</strong> In addition, the rip must be encoded at the same bit depth and sampling rate as the original stream. Downsampled versions of the original source material may be trumped by a torrent containing audio files ripped directly from the disc at the bit depth and sampling rate originally found on disc. For example, there is a 96 kHz track and a 44.1 kHz track on the Blu-ray disc. A user uploads only the 96 kHz track and that source is subsequently downsampled to 44.1 kHz. Another user who rips the actual 44.1 kHz track from the original disc may trump the downsampled torrent.</li>
|
<li id="r2.9.5.1"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.1">2.9.5.1.</a> <strong> A multichannel lossless rip must have the same number of and arrangement of channels as the source media.</strong> In addition, the rip must be encoded at the same bit depth and sampling rate as the original stream. Downsampled versions of the original source material may be trumped by a torrent containing audio files ripped directly from the disc at the bit depth and sampling rate originally found on disc. For example, there is a 96 kHz track and a 44.1 kHz track on the Blu-ray disc. A user uploads only the 96 kHz track and that source is subsequently downsampled to 44.1 kHz. Another user who rips the actual 44.1 kHz track from the original disc may trump the downsampled torrent.</li>
|
||||||
<li id="r2.9.5.2"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.2">2.9.5.2.</a> <strong> Downmixing of Blu-ray sources is prohibited.</strong> Do not downmix a 5.1 (or higher) channel mix to stereo and upload the resulting audio files. You may still downconvert lossless audio sources from 24-bit to 16-bit.</li>
|
<li id="r2.9.5.2"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.2">2.9.5.2.</a> <strong> Downmixing of Blu-ray sources is prohibited.</strong> Do not downmix a 5.1 (or higher) channel mix to stereo and upload the resulting audio files. You may still downconvert lossless audio sources from 24-bit to 16-bit.</li>
|
||||||
<li id="r2.9.5.3"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.3">2.9.5.3.</a> <strong> All lossy Blu-ray torrents must be uploaded in a Redbook-compliant form.</strong> Any stereo lossless sources must be downconverted to 16 bits and downsampled to 44.1 kHz before they are transcoded to lossy MP3 formats. No other bit depth or sampling rate is allowed for lossy Blu-ray torrents.</li>
|
<li id="r2.9.5.3"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.3">2.9.5.3.</a> <strong> All lossy Blu-ray torrents must be uploaded in a Redbook-compliant form.</strong> Any stereo lossless sources must be downconverted to 16 bits and downsampled to 44.1 kHz before they are transcoded to lossy MP3 formats. No other bit depth or sampling rate is allowed for lossy Blu-ray torrents.</li>
|
||||||
<li id="r2.9.5.4"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.4">2.9.5.4.</a> <strong> Do not downsample, downmix, transcode or otherwise manipulate any lossy Blu-ray format (e.g., Dolby Digital (AC3), DTS, Dolby Digital Plus (AC3), and DTS-HD).</strong> </li>
|
<li id="r2.9.5.4"><a href="#r2.9.5"><strong>↑_</strong></a> <a href="#r2.9.5.4">2.9.5.4.</a> <strong> Do not downsample, downmix, transcode or otherwise manipulate any lossy Blu-ray format (e.g., Dolby Digital (AC3), DTS, Dolby Digital Plus (AC3), and DTS-HD).</strong> </li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user