↑_2.1.4.Bitrates must accurately reflect encoder presets or average bitrate of the audio files. You are responsible for supplying correct format and bitrate information on the upload page. All audio torrents must have accurate labeling for the encoder settings used or the average bitrate. This means that lossy formats such as MP3, AAC, DTS, and Ogg Vorbis cannot have a bitrate of "lossless." Conversely, FLAC cannot have fixed bitrates or xxx(VBR) bitrates. Non-LAME formats and MP3 encoders cannot use LAME's VBR switches (-V0, -V1, -V2, etc). If you are uploading a non-LAME MP3, determine the average bitrate of the files. Then select "Other" for bitrate and type in xxx (VBR) where "xxx" is the bitrate you found. Some tools to determine the bitrates of audio files are Audio Identifier, Mr. Questionman (mirror), or Dnuos. If the bitrate is labeled incorrectly on your torrent, your torrent may be deleted if reported.
-
↑_2.1.5.Albums must not be ripped or uploaded as a single track. If the tracks on the original CD were separate, you must rip them to separate files. Clearly, CDs with single tracks are permitted to be uploaded without prior splitting. You are encouraged to use MusiCutter or MP3DirectCut for MP3 and CUE Tools, XLD, or EAC for lossless if you need to split up an album image into individual tracks. Exceptions: Gapless DJ or professional mixes released as MP3+CUE images are allowed as unseparated album images on the site. This includes scene DJ mixes. No other format is allowed in this unsplit form. Unsplit MP3 albums containing separate tracks are not allowed if missing a cue sheet.
+
↑_2.1.5.Albums must not be ripped or uploaded as a single track. If the tracks on the original CD were separate, you must rip them to separate files. Clearly, CDs with single tracks are permitted to be uploaded without prior splitting. You are encouraged to use MusiCutter or MP3DirectCut for MP3 and CUE Tools, XLD, or EAC for lossless if you need to split up an album image into individual tracks. Exceptions: Gapless DJ or professional mixes released as MP3+CUE images are allowed as unseparated album images on the site. This includes scene DJ mixes. No other format is allowed in this unsplit form. Unsplit MP3 albums containing separate tracks are not allowed if missing a cue sheet.
↑_2.1.6.All music torrents must be encoded with a single encoder using the same settings. This means you cannot create a torrent which contains both CBR and VBR files, nor can you upload torrents containing a mix of APS (VBR)/-V2 (VBR) and APX (VBR)/-V0 (VBR). Including other kinds of audio quality, such as duplicate lossy files in a lossless torrent is also prohibited. This kind of release is referred to as a "mutt rip."
@@ -375,23 +375,23 @@
↑_2.2.15.1.All FLAC CD rips must come from official CD sources. Rips must be taken from commercially pressed or official-pressed CD sources. They may not come from CD-R copies of the same pressed CDs. Undetected errors may be introduced from the original CD rip and subsequent burning process to CD-R. Even though the CD-R is ripped with proper settings in XLD or EAC, it may still be a sub-par rip with a good log. Exceptions: If the release is only distributed on CD-R, then that is acceptable. Promotions and small distributions of albums tend to be in CD-R format.
+
↑_2.2.15.1.All FLAC CD rips must come from official CD sources. Rips must be taken from commercially pressed or official-pressed CD sources. They may not come from CD-R copies of the same pressed CDs. Undetected errors may be introduced from the original CD rip and subsequent burning process to CD-R. Even though the CD-R is ripped with proper settings in XLD or EAC, it may still be a sub-par rip with a good log. Exceptions: If the release is only distributed on CD-R, then that is acceptable. Promotions and small distributions of albums tend to be in CD-R format.
↑_2.2.15.2.A FLAC torrent without a rip log can be trumped by a FLAC torrent of the same release containing a rip log. The FLAC torrent without a log will be trumped in favor of one containing a log. Please make sure your rip log has the extension .log in order to be displayed properly on the torrents page. Exceptions: If the FLAC torrent with a log contains excessive rip errors (e.g. suspicious positions, skips, or pops), it cannot replace the existing torrent. Audiochecker, auCDtect, and other MPEG analyzer logs do not count as rip logs, even if renamed with the .log extension. Soundboards and other exclusive lossless digitally-distributed files cannot be unofficially burned to CD-R and re-ripped in order to trump existing digital copies of the same quality and source.
-
↑_2.2.15.3.A FLAC upload with an EAC or XLD rip log that scores 100 on the logchecker replaces one with a lesser score. Proper EAC or XLD rips can replace rips made by other rippers or with sub-par settings. No log scoring less than 100 can trump an already existing one under 100. For example, a FLAC+log rip that scores a 50 in the logchecker can not be trumped by a FLAC+log that scores an 80. What.CD recommends xuncat's guide for EAC, and this guide for XLD. What.CD strongly encourages enabling AccurateRip if available for your CD extraction app of choice. Note: If a log scores 95 due to not defeating audio cache, and the torrent description contains accepted proof of the drive for ripping caches less than 64 kB of audio data, then that torrent can not be trumped by a torrent with a 100 score. The 95 torrent may be upgraded to 100 once a staff member has been alerted to the case, and has manually corrected the score. See 2.2.15.6.
+
↑_2.2.15.3.A FLAC upload with an EAC or XLD rip log that scores 100 on the logchecker replaces one with a lesser score. Proper EAC or XLD rips can replace rips made by other rippers or with sub-par settings. No log scoring less than 100 can trump an already existing one under 100. For example, a FLAC+log rip that scores a 50 in the logchecker can not be trumped by a FLAC+log that scores an 80. What.CD recommends xuncat's guide for EAC, and this guide for XLD. What.CD strongly encourages enabling AccurateRip if available for your CD extraction app of choice. Note: If a log scores 95 due to not defeating audio cache, and the torrent description contains accepted proof of the drive for ripping caches less than 64 kB of audio data, then that torrent can not be trumped by a torrent with a 100 score. The 95 torrent may be upgraded to 100 once a staff member has been alerted to the case, and has manually corrected the score. See 2.2.15.7.
-
↑_2.2.15.4.XLD and EAC log in languages other than English require manual logchecker score adjustment. The current logchecker cannot parse non-English logs made by EAC and XLD. However, a special exception is made for foreign-language logs since the rip quality is equivalent to English logs. Please report your torrent with the RP link so staff can approve your torrent manually.
+
↑_2.2.15.4.XLD and EAC log in languages other than English require manual logchecker score adjustment. The current logchecker cannot parse non-English logs made by EAC and XLD. However, a special exception is made for foreign-language logs since the rip quality is equivalent to English logs. Please report your torrent with the RP link so staff can approve your torrent manually.
-
↑_2.2.15.5.Range rips of hidden tracks or range rips under strict conditions require manual score adjustment. The new logchecker cannot accurately score range-ripped hidden tracks appended to proper rip logs. If you have created a 100 rip with a hidden track, but the logchecker decreased your score for the hidden track, report the torrent. That way your score can be adjusted to reflect the proper settings. What.CD does not encourage ripping entire CDs as range rips. Instead, please rip CDs to separate tracks according to the EAC Guide. For those rare cases where you have created a CD image rip with matching CRCs for test and copy, and the tracks have a AccurateRip verification of 2 or more, then you may submit your torrent for manual adjustment. Note: The CD Image rip must be split with CUE Tools, XLD, or EAC. No other splitter is acceptable for a score adjustment. You will not receive score adjustment for copy-only range rips approved with AccurateRip nor range rips done with test and copy only.
+
↑_2.2.15.5.Range rips of hidden tracks or range rips under strict conditions require manual score adjustment. The new logchecker cannot accurately score range-ripped hidden tracks appended to proper rip logs. If you have created a 100 rip with a hidden track, but the logchecker decreased your score for the hidden track, report the torrent. That way your score can be adjusted to reflect the proper settings. What.CD does not encourage ripping entire CDs as range rips. Instead, please rip CDs to separate tracks according to the EAC Guide. For those rare cases where you have created a CD image rip with matching CRCs for test and copy, and the tracks have a AccurateRip verification of 2 or more, then you may submit your torrent for manual adjustment. Note: The CD Image rip must be split with CUE Tools, XLD, or EAC. No other splitter is acceptable for a score adjustment. You will not receive score adjustment for copy-only range rips approved with AccurateRip nor range rips done with test and copy only.
↑_2.2.15.6.A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet ONLY when the included cue sheet is materially different than 'a cue generated from the ripping log' http://eachelper.uphero.com/index.php. Examples of a material difference include additional or correct indices, and pre-emphasis flags. If you upload a torrent with a cue sheet that provides nothing additional beyond what is contained in the ripping log of the preexistent torrent, it will be deleted as a dupe. Exception: An EACv0.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 logchecker.
-
↑_2.2.15.7.Drives that cache less than 64 kB of audio data may leave the audio cache enabled. Proof is required. They can be trumped by a 100 rip if no proof is included. Under certain conditions, rips made without the audio cache disabled may trump other rips if all other settings are correct. A pasted log (hosted at Pastebin or similar site is OK) or screenshot of proof from Feurio! and a screenshot from CacheX should be posted in the torrent description field. See the Wiki page for examples of allowed proof. You will need to present proof from both CacheX and Feurio!. EAC's own cache detection may give erroneous results sometimes, so a screenshot of EAC's drive features test cannot serve as proof. Also, XLD logs before CDParanoia III 10.2 engine require AccurateRip verification because the cache is not properly defeated on earlier CDParanoia versions. Please report your torrent with the RP link so staff can approve your torrent manually to 100 score.
+
↑_2.2.15.7.Drives that cache less than 64 kB of audio data may leave the audio cache enabled. Proof is required. They can be trumped by a 100 rip if no proof is included. Under certain conditions, rips made without the audio cache disabled may trump other rips if all other settings are correct. A pasted log (hosted at Pastebin or similar site is OK) or screenshot of proof from Feurio! and a screenshot from CacheX should be posted in the torrent description field. See the Wiki page for examples of allowed proof. You will need to present proof from both CacheX and Feurio!. EAC's own cache detection may give erroneous results sometimes, so a screenshot of EAC's drive features test cannot serve as proof. Also, XLD logs before CDParanoia III 10.2 engine require AccurateRip verification because the cache is not properly defeated on earlier CDParanoia versions. Please report your torrent with the RP link so staff can approve your torrent manually to 100 score.
↑_2.2.15.8.FLAC rips that contain ID3 tags or other non-compliant tags for FLAC may be trumped by same score rips that have faulty tags removed and replaced with the standard for each format. Enabling ID3 tags in EAC when ripping to FLAC may prevent some players from playing the files due to the inclusion of ID3 headers. If you wish to trump a FLAC rip that was ripped with ID3 tags enabled, upload the corrected torrent with the proper Vorbis comments, and report the old torrent. Add information about your clean-up in the Release description, or your torrent may be deleted for a dupe. Do not edit the log and change the ID3 tag setting to "No." Note: A simple way of getting rid of the ID3 header is to decompress the files to WAV. Then compress the files to FLAC, and again add the proper Vorbis comments.
diff --git a/sections/torrents/add_alias.php b/sections/torrents/add_alias.php
index c8f54f27..6a94a2f5 100644
--- a/sections/torrents/add_alias.php
+++ b/sections/torrents/add_alias.php
@@ -9,9 +9,6 @@
if(!is_number($GroupID) || !$GroupID) {
error(0);
}
-/*if(!check_perms('torrents_edit')) {
- error(403);
-}*/
$Changed = false;
diff --git a/sections/user/user.php b/sections/user/user.php
index 2333ed9d..875963e4 100644
--- a/sections/user/user.php
+++ b/sections/user/user.php
@@ -138,7 +138,7 @@ function check_paranoia_here($Setting) {
$Badges.=($Enabled == '1' || $Enabled == '0' || !$Enabled) ? '': '';
-show_header($Username,'user,bbcode');
+show_header($Username,'user,bbcode,requests');
?>
@@ -762,14 +762,14 @@ function check_paranoia_here($Setting) {
';
-show_header($Username,'user,bbcode');
+show_header($Username,'user,bbcode,requests');
?>
@@ -762,14 +762,14 @@ function check_paranoia_here($Setting) {