1.1.
Do not create more than one account.
Users are allowed one account per lifetime. Do not create additional accounts under any circumstance. If your account is disabled, contact staff in #red-disabled on IRC.

1.2.
Do not trade, sell, give away, or offer accounts.
If you no longer wish to use your account, send a Staff PM and request that your account be disabled. Note, we do not delete accounts.

1.3.
Do not share accounts.
Accounts are for personal use only. Granting access to your account in any way (e.g., shared login details, external programs) is prohibited. Invite friends and family if they wish to use the site.

2.1.
Do not invite bad users.
You are responsible for your invitees. You will not be punished if your invitees fail to maintain required share ratios, but invitees who break golden rules or invite rules will place your invite privileges and account at risk.

2.2.
Do not trade, sell, publicly give away, or publicly offer invites.
Only invite people you know and trust. Staff and approved users may offer invites on other private trackers in designated, user class-restricted invite forums. Do not offer invites on public websites or any private sites that exist solely for the purpose of invite giveaways, trading, and/or selling. Do not offer invites on IRC channels or other social chat clients. Even if you offer the invite in a personal message it is still considered a giveaway and against the rules. Responding to public invite requests is prohibited. See this wiki article for more information about inviting users.

2.3.
Do not request invites or accounts.
Requesting invites to—or accounts on—Redacted or other trackers is prohibited. Invites may be offered, but not requested, in the site's Invites forum (restricted to the Power User class and above). You may request invites by messaging users only when they have offered them in the Invites Forum. Unsolicited invite requests, even by private message, are prohibited.

3.1.
Do not engage in ratio manipulation.
Transferring buffer—or increasing your buffer—through unintended uses of the BitTorrent protocol or site features (e.g., request abuse) constitutes ratio manipulation. When in doubt, send a Staff PM asking for more information.

3.2.
Do not report incorrect data to the tracker (i.e., cheating).
Reporting incorrect data to the tracker constitutes cheating, whether it is accomplished through the use of a modified "cheat client" or through manipulation of an approved client.

3.3.
Do not use unapproved clients.
Your client must be found on the Client Whitelist. You must not use clients that have been modified in any way. Developers interested in testing unstable clients must first receive staff approval.

3.4.
Do not modify Redacted .torrent files.
Embedding non-Redacted announce URLs in Redacted .torrents is prohibited. Doing so causes false data to be reported and will be interpreted as cheating. This applies to standalone .torrent files and .torrent files that have been loaded into a client.

3.5.
Do not share .torrent files or your passkey.
Embedded in each Redacted .torrent file is an announce URL containing your personal passkey. Passkeys enable users to report stats to the tracker.

4.1.
Do not blackmail, threaten, or expose fellow users.
Exposing or threatening to expose private information about users for any reason is prohibited. Private information includes but is not limited to personally identifying information (e.g., names, records, biographical details, photos). Information that hasn't been openly volunteered by a user should not be discussed or shared without permission. This includes private information collected via investigations into openly volunteered information (e.g., Google search results).

4.2.
Do not scam or defraud.
Scams (e.g., phishing) of any kind are prohibited.

4.3.
Do not disrespect staff decisions.
Disagreements must be discussed privately with the deciding moderator. If the moderator has retired or is unavailable, you may send a Staff PM. Do not contact multiple moderators hoping to find one amenable to your cause; however, you may contact a site administrator if you require a second opinion. Options for contacting staff include private message, Staff PM, and #red-disabled on IRC.

4.4.
Do not impersonate staff.
Impersonating staff or official service accounts (e.g., Drone) on-site, off-site, or on IRC is prohibited. This includes impersonating staff of other trackers. Deceptively misrepresenting staff decisions is also prohibited.

4.5.
Do not backseat moderate.
"Backseat moderation" occurs when users police other users. Confronting, provoking, or chastising users suspected of violating rules—or users suspected of submitting reports—is prohibited. Submit a report if you see a rule violation.

4.6.
Do not request special events.
Special events (e.g., freeleech, neutral leech, picks) are launched at the discretion of the staff. They do not adhere to a fixed schedule, and may not be requested by users.

4.7.
Do not harvest user-identifying information.
Using Redacted's services to harvest user-identifying information of any kind (e.g., IP addresses, personal links) through the use of scripts, exploits, or other techniques is prohibited.

4.8.
Do not use Redacted's services (including the tracker, website, and IRC network) for commercial gain.
Commercializing services provided by or code maintained by Redacted (e.g., Gazelle, Ocelot) is prohibited. Commercializing content provided by Redacted users via the aforementioned services (e.g., user torrent data) is prohibited. Referral schemes, financial solicitations, and money offers are also prohibited.

5.1.
Do not browse Redacted using public proxies, Tor, or free VPN services.
Do not browse the site using free proxy or VPN services. Browsing or torrenting through Tor is also forbidden. You may browse the site through paid-for VPN services, private and shared seedboxes, and private servers and proxies. Shared VPNs or VPNs with dynamic IPs need to be approved by staff before use. When in doubt, send a Staff PM seeking approval of your VPN. See our Proxy/VPN Tips and Multiple IPs articles for more information.

5.2.
Do not abuse automated site access.
All automated site access must be done through the API. API use is limited to 5 requests within any 10-second window. Scripts and other automated processes must not scrape the site's HTML pages.

5.3.
Do not autosnatch freeleech torrents.
The automatic snatching of freeleech torrents using any method involving little or no user-input (e.g., API-based scripts, log or site scraping, etc.) is prohibited. See Redacted's Freeleech Autosnatching Policy article for more information.

6.1.
Do not seek or exploit live bugs for any reason.
Seeking or exploiting bugs in the live site (as opposed to a local development environment) is prohibited. If you discover a critical bug or security vulnerability, immediately report it in accordance with Redacted's Responsible Disclosure Policy. Non-critical bugs can be reported in the Bugs Forum.

6.2.
Do not publish exploits.
The publication, organization, dissemination, sharing, technical discussion, or technical facilitation of exploits is prohibited at staff discretion. Exploits are defined as unanticipated or unaccepted uses of internal, external, non-profit, or for-profit services. See Redacted's Exploit Policy article for more information. Exploits are subject to reclassification at any time.







Ratio Rules

Ratio System Overview:
Your ratio is calculated by dividing the amount of data you've uploaded by the amount of data you've downloaded. You can view your ratio in the site header or in the "stats" section of your user profile.
To maintain leeching privileges, your ratio must remain above a minimum value. This minimum value is your required ratio.
If your ratio falls below your required ratio, you will be given two weeks to raise your ratio back above your required ratio. During this period, you are on ratio watch.
If you fail to raise your ratio above your required ratio in the allotted time, your leeching privileges will be revoked. You will be unable to download more data. Your account will remain enabled.


Required Ratio Overview:
Your required ratio represents the minimum ratio you must maintain to avoid ratio watch. You can view your required ratio in the site header after the word "required" or in the "stats" section of your user profile.
Your required ratio is unique; each person's required ratio is calculated for their account specifically.
Your required ratio is calculated using (1) the total amount of data you've downloaded and (2) the total number of torrents you're seeding. The seeding total is not limited to snatched torrents (completed downloads) — the total includes, but is not limited to, your uploaded torrents.
The required ratio system lowers your required ratio when you seed a greater number of torrents. The more torrents you seed, the lower your required ratio will be. The lower your required ratio is, the less likely it is that you'll enter ratio watch.


Required Ratio Table

Amount Downloaded	Required Ratio (0% seeded)	Required Ratio (100% seeded)
0–5 GB	0.00	0.00
5–10 GB	0.15	0.00
10–20 GB	0.20	0.00
20–30 GB	0.30	0.05
30–40 GB	0.40	0.10
40–50 GB	0.50	0.20
50–60 GB	0.60	0.30
60–80 GB	0.60	0.40
80–100 GB	0.60	0.50
100+ GB	0.60	0.60


Required Ratio Calculation:
1: Determine the maximum and minimum possible values of your required ratio. Using the table above, determine your amount downloaded bracket from the first column. Next, locate the values in the adjacent columns. The second column lists the maximum required ratio for each bracket, and the third column lists the minimum required ratio for each bracket. The maximum and minimum required ratios are also referred to as the 0% seeded and 100% seeded required ratios, respectively.
2: Determine the actual required ratio. Your actual required ratio will be a number that falls between the maximum and minimum required ratio values determined in the previous step. To determine your actual required ratio, the system first uses the maximum required ratio (0% seeded) and multiplies it by the value [1 − (seeding / snatched)]. Formatted differently, the calculation performed by the system looks like this:

required ratio = (maximum required ratio) * (1 - (seeding / snatched))


In this formula, snatched is the number of non-deleted unique snatches you have made. If you snatch a torrent twice, it only counts once. If a snatched torrent is deleted from the site, it is not counted at all.
In this formula, seeding is the average number of torrents you've seeded over a 72 hour period within the last week. If you've seeded a torrent for less than 72 hours within the last week, it will not raise your seeding total. Please note that while it is possible to seed more torrents than you have snatched, the system effectively caps the value at 100% of your snatched amount.
3: Round, if necessary. The value determined in the previous step is rounded up to your minimum required ratio (100% seeded) if necessary. This step is required because most amount downloaded brackets have a minimum required ratio (100% seeded) greater than zero, and the value returned by the above calculation is zero when seeding equals snatched.


Required Ratio Details:
If you stop seeding for one week, your required ratio will become the maximum required ratio (0% seeded) for your amount downloaded bracket. Once you have resumed seeding for a 72 hour period, your required ratio will decrease according to the above calculations.
If your download total is less than 5 GB, you won't be eligible for ratio watch, and you will not need a required ratio. In this circumstance, your required ratio will be zero regardless of your seeding percentage.
If your download total is less than 20 GB and you are seeding a number of torrents equal to 100% of your snatches, your required ratio will be zero.
As your download total increases, your minimum (100% seeded) and maximum (0% seeded) required ratios taper together. After you have downloaded 100 GB, those values become equal to each other. This means that users with download totals greater than or equal to 100 GB have a minimum required ratio (100% seeded) of 0.60 from that point forward.


Required Ratio Example:
In this example, Rippy has downloaded 25 GB. Rippy falls into the 20–30 GB amount downloaded bracket in the table above. Rippy's maximum required ratio (0% seeded) is 0.30, and his minimum required ratio (100% seeded) is 0.05.
In this example, Rippy has snatched 90 torrents, and is currently seeding 45 torrents.
To calculate Rippy's actual required ratio, we take his maximum required ratio (0% seeded), which is 0.30, and multiply it by [1 − (seeding / snatched)] (which is 0.50). Written out: 0.30 * [1 − (45 / 90)] = 0.15
The resulting required ratio is 0.15, which falls between the maximum required ratio of 0.30 and the minimum required ratio of 0.05 for his amount downloaded bracket.
If Rippy's on-site required ratio was listed as a value greater than the calculated value, this would be because he hadn't seeded those 45 torrents for a 72 hour period in the last week. In this case, the system would not be counting all 45 torrents as seeded.


Ratio Watch Overview:
Everyone gets to download their first 5 GB before ratio watch eligibility begins.
If you've downloaded more than 5 GB and your ratio does not meet or surpass your required ratio, you will be put on ratio watch and have two weeks to raise your ratio above your required ratio.
If you download 10 GB while on ratio watch, your leeching privileges will automatically be disabled.
If you fail to leave ratio watch within a two week period, you will lose leeching privileges. After losing leeching privileges, you will be unable to download more data. Your account will remain enabled.
The ratio watch system is automated and cannot be interrupted by staff.


Leaving Ratio Watch:
To leave ratio watch, you must either raise your ratio by uploading more, or lower your required ratio by seeding more. Your ratio must be equal to or above your required ratio in order for ratio watch to end.
If you fail to improve your ratio by the time ratio watch expires and lose leeching privileges, your required ratio will be temporarily set to the maximum possible requirement (as if 0% of snatched torrents were being seeded).
After losing leeching privileges, in order to adjust the required ratio so that it reflects the actual number of torrents being seeded, you must seed for a combined 72 hours within a weeklong period. After 72 hours of seeding occur, the required ratio will update to reflect your current seeding total, just as it would for a leech-enabled user.
Leeching privileges will be restored once your ratio has become greater than or equal to your required ratio.













Requests
Do not make requests for torrents that break the rules. It is your responsibility that the request follows the rules. Your request will be deleted, and you will not get your bounty back. Requests cannot be more specific than the upload (and trumping) rules. For example, requesting an MP3 torrent with a log when the rules prohibit replacing an MP3 torrent without a log. Such a request asks for a duplicate to be uploaded.
Only one title (application, album, etc.) per request. No requests for multiple albums (e.g. discographies) or vague requirements. You may ask for multiple formats, but you cannot specify all of them. For example, you may ask for either a FLAC or V0 but not both formats. You may also make a list of albums by one artist that satisfies your request, but the request can be filled with only one album. Application requests can consist of only one application, but may span a range of different versions. However, such requests can be filled with only one version of that title.
Do not unfill requests for trivial reasons. If you did not specify in your request what you wanted (such as bitrates or a particular edition), do not unfill and later change the description. Do not unfill requests if you are unsure of what you are doing (e.g. the filled torrent may be a transcode, but you don't know how to tell). Ask for help from first-line support or staff in that case. You may unfill the request if the torrent does not fit your specifications stated clearly in the request.
All users must have an equal chance to fill a request. Trading upload credit is not allowed. Abusing the request system to exchange favors for other users is not tolerated. That includes making specific requests for certain users (whether explicitly named or not). Making requests for releases, and then unfilling so that one particular user can fill the request is not allowed. If reported, both the requester and user filling the request will receive a warning and lose the request bounty.
No manipulation of the requester for bounty. The bounty is a reward for helping other users — it should not be a ransom. Any user who refuses to fill a request unless the bounty is increased will face harsh punishment.












Collages
Collages in the Discography, Staff Picks, Label, and Charts categories must be based on fact, and not opinion. If something is a published Best Of (for instance, "Pitchfork's Best Albums of the 1990's") then it should go in the Charts category.
Collages in the Personal, Theme, and Genre Introductions categories may be based on opinion. You must respect others' opinions whilst creating and populating Theme and Genre Introduction collages.
Vandalizing of collages will be taken very seriously, resulting in collage editing privileges being removed (at a minimum).
Personal Best Of collages are only allowed in the new Personal Collages category. You must be a Power User+ or Donor to create one.
A well-defined group of people, for instance Torrent Masters, or Interviewers, may create a Group Picks Theme collage with one pick per person, after having gained permission for the collage from Staff.
There may only be one collage per Genre Introduction/Theme. Dupe collages will be deleted.
Theme/Genre Introduction collages must be sensible, and reasonably broad. Those that do not fit this description will be deleted.
Collages are not an alternative to the tagging system. A collage such as 'mathcore torrents' wouldn't be allowed, because it is far more appropriate to just tag the torrents as mathcore. Of course, an 'xysite.com worst 50 mathcore albums' collage would be looked upon differently.
Collages should not be used to create artist discographies, as the artist pages already exist for this purpose. However, for an artist who has a multitude of side projects, it is allowed to create a collage containing all of the projects, to be placed in the Discography category.
Power Users and Donors get one personal collage. Elites can have two, Torrent Masters can have up to three, Power TMs up to four and Elite TM+ up to five. Donors always receive one more than the class maximum.
Every collage must have at least 3 torrent groups in it, except for collages of type "Label", "Personal", and "Staff Picks".
Please check to see that a similar collage does not already exist. If a similar collage does exist, please contribute to the existing collage.
Please give your collage an appropriate title and a decent description explaining its purpose.
Please attempt to add album art to every torrent in your collage.






Client Whitelist
Client rules are how we maintain the integrity of our swarms. This allows us to filter out disruptive and dishonest clients that may hurt the performance of either the tracker or individual peers.
Allowed Client
aTorrent 2.0.x
aTorrent 2.1.x - 3.0.x
Bittorrent Embedded SDK 2.x
btgdaemon 0.9.x
btgdaemon 1.0.x
btpd 0.13
btpd 0.15
btpd 0.16
Deluge 1.2.1
Deluge 1.2.2
Deluge 1.2.3
Deluge 1.3.x
Flud 1.4.8.x
Flud 1.4.9.x
Halite 0.3.2.2
Halite 0.4.0.2
Halite 0.4.0.4
KTorrent 2.1x
KTorrent 2.2x
KTorrent 3.0x
KTorrent 3.1x
KTorrent 3.2x
KTorrent 3.3x
KTorrent 3.5x
KTorrent 4.0.x
KTorrent 4.1
KTorrent 4.1.1
KTorrent 4.1.2
KTorrent 4.1.3
KTorrent 4.2
KTorrent 4.3
KTorrent 5.0.x
Libtorrent (Rasterbar)
libtorrent 0.10.x (rtorrent)
libtorrent 0.11.x (rtorrent)
libtorrent 0.12.x (rtorrent)
libtorrent 0.13.x (rtorrent)
Mainline (BitTorrent)
qBittorrent 2.3.x
qBittorrent 2.4.x
qBittorrent 2.5.x
qBittorrent 2.6.x
qBittorrent 2.7.x
qBittorrent 2.8.x
qBittorrent 2.9.x
qBittorrent 3.0.x
qBittorrent 3.1.x
qBittorrent 3.2.x
qBittorrent 3.3.x
Transmission 1.5.4
Transmission 1.6.x
Transmission 1.7.x
Transmission 1.8.x
Transmission 1.92
Transmission 1.93
Transmission 2.xx
uTorrent 1.8.x
uTorrent 2.0.4
uTorrent 2.1.x
uTorrent 2.2.x
uTorrent 3.0 Linux Server
uTorrent 3.0.x
uTorrent 3.1.2
uTorrent 3.1.3
uTorrent 3.2.x
uTorrent 3.3.x
uTorrent 3.4.x
uTorrent 3.5.x
uTorrent embedded 2.1 Buffalo LinkStation Live
uTorrent Mac 0.9x
uTorrent Mac 1.0x
uTorrent Mac 1.1x
uTorrent Mac 1.5x
uTorrent Mac 1.6x
uTorrent Mac 1.7x
uTorrent Mac 1.8x




Uploading Rules


Filter (empty to reset)
 Example: The search term FLAC returns all rules containing FLAC. The search term FLAC+trump returns all rules containing both FLAC and trump.

Introduction
1. Uploading Rules
1.1. General
1.2. Specifically Banned
1.3. Scene Uploads
2. Music
2.1. General
2.2. Duplicates & Trumping
2.2.9. Lossy rules
2.2.10. Lossless rules
2.2.11. Editions and Releases rules
2.3. Formatting
2.4. Bonus Content
2.5. Vinyl
2.6. Live Music and Soundboards
2.6.9.1. Allowed Live Music
2.6.9.2. Disallowed Live Music
2.7. Multichannel
2.8. SACD
2.9. Blu-ray
2.10. Cassettes
3. Comedy (Audio) & Audiobooks
4. Applications
4.1. General
4.2. Duplicates & Trumping
5. Comic Books
5.1. General
5.2. Multi-comic
5.3. Duplicates & Trumping
5.4. Formatting
6. ebooks, eLearning Books & Sheet Music
7. eLearning Videos
↑ Introduction
The uploading rules below are overwhelmingly long and detailed for a reason. The length is necessary to explain the rules clearly and thoroughly. A summary of each rule is in bold text before the actual rule for easier reading. You may also find the corresponding rule sections in the Index. The corresponding ↑ (move one level up) and rule section links (move down into the document) help provide quick navigation.
Before you upload anything, if you are still unsure of what a rule means, PLEASE ask your questions at any of the following points of site user support: First-Line Support, the Help Forum, or #red-help on IRC. Send a Staff PM addressed to staff if other support has directed you to a moderator or if support has been unhelpful in your particular case. If you find any dead or broken links in the upload rules, send a Staff PM addressed to staff, and include in your message the upload rule number (e.g. 2.4.3) and preferably the correct link to replace the broken one.
↑ 1. Uploading Rules
↑ 1.1. General
↑_ 1.1.1. Only music, applications, comic books, ebooks, comedy (audio), audiobooks, and music-related eLearning videos are allowed on the site.
↑_ 1.1.2. Duplicate torrents in any category are not allowed. There are some exceptions to this rule, which are outlined in their relevant sections below.
↑_ 1.1.3. No freely available content in non-music sections. If you could just download something from the web, so can everyone else. Each main section explains in greater detail what "freely available" means in the context of that section. See 2.1.9 in regards to freely available music. See 4.1.3 in regards to freely available applications.
↑_ 1.1.4. Seed complete copies of your uploads. Do not upload a torrent unless you intend to seed until there are at least 1.0 distributed copies. Seeding past this minimum is strongly encouraged.
↑_ 1.1.5. No advertising or personal credits. Providing artist, album, label, or retailer information is not considered advertising.
↑_ 1.1.5.1 Do not advertise sites, groups, or persons in torrent contents (e.g., folder names, file names, or file tags). Exceptions: untouched scene uploads are exempt from this rule. For analog uploads, ripper credits may be included in a lineage text file, in a folder name, or in an optional file tag field (e.g. "comment" or "ripped by"), but never in a required tag field).
↑_ 1.1.5.2 Do not advertise sites, groups, or persons in torrent descriptions. Exception: torrent source information (e.g. ripper, scene group, or original uploader credit) is allowed in torrent descriptions.
↑_ 1.1.6. Archived files in uploads are not allowed. Exceptions: The sections that allow archived files (e.g., zip, rar, iso, etc.) are the following:
Comic Books (.cbr and .cbz).
Scene released torrents in non-music categories.
Sheet music may be individually archived.
↑ 1.2. Specifically Banned
↑_ 1.2.1. Anything not specifically allowed below. If you have any doubts, ask before uploading.
↑_ 1.2.2. Any car parts and car data programs. This ban includes programs like AllData and vendor-specific diagnostic programs such as Carsoft.
↑_ 1.2.3. Videos of any kind (other than eLearning Videos). No movies, no TV shows, no concerts, and no data/video tracks from enhanced CDs.
↑_ 1.2.4. Pornography or nudity of any kind unless it is part of the official packaging for a commercial audio release. This ban includes pictures, erotic comic books or hentai, sex manuals, erotic magazines, etc.
↑_ 1.2.5. Games of any kind. No games of any kind for PC, Mac, Linux, mobile devices, or any other platform are allowed.
↑_ 1.2.6. Collections of pictures or wallpapers are not applications. You may not upload them to any category. Commercially available template and clip art packs are acceptable for the application category (see 4.1.9).
↑_ 1.2.7. User compilations in any category. All releases, packs, or collections must be reasonably official as specified in each category.
↑_ 1.2.8. DRM-restricted files. Files must not be encrypted or be in a restricted format that impedes sharing. You are also highly encouraged to remove personal information from any non-DRM protected files (such as iTunes Plus releases).
↑ 1.3. Scene Uploads
↑_ 1.3.1. You may give credit to the release group (optional). If you really want to give credit to the release group, mention the full release name, including group name, in the Release description section only. Do not add this information to the Album description section.
↑_ 1.3.2. No NFO art pasted in the album description. Unedited NFOs are allowed within the specific torrent Release description - not in the Album page description. If you must include some information from the NFO in the Album description or Release description, include only the tracklist, album notes, and other essential information. Specific encoding settings belong in the Release description.
↑_ 1.3.3. Use the actual album title on the upload page; do not use the scene-given title. Naming your album_titles_like_this or your.albums.like.this is not allowed. Use the actual release title and artist. Do not use the title from the torrent folder or NFO for the scene release.
↑_ 1.3.4. Scene releases must be complete (as released) to use the Scene label. If you've changed the tags, unpacked the archive, removed any files, split the tracks, or altered the track naming, then it is no longer a scene release. It should not be labeled as such. If any of these changes has taken place, file names should not include any reference to the release group (see 1.1.5, 2.3.2, and 2.3.11).
↑_ 1.3.5. No protected archives. Archived releases must not be password protected.
↑_ 1.3.6. Scene releases in each torrent category must conform to the rules specified for their respective sections. For example, music scene releases must adhere to the music quality and formatting rules no matter how the original files were released. If the scene archives were password protected, you cannot upload them to this site unmodified. Exceptions: You may upload scene releases that originally do not fit in the rules if you can make the necessary changes within the rules. However, these modified uploads must not be labeled as scene.
↑ 2. Music
↑ 2.1. General
↑_ 2.1.1. The only formats allowed for music are:
Lossy: MP3, AAC, AC3, DTS
Lossless: FLAC (maximum 24-bit depth, maximum 192 kHz sampling rate)
Only standard versions of each format are allowed. Hybrid formats that combine both lossless and lossy audio data in the same file, such as DTS-HD, mp3HD, and HD-AAC, are not allowed. AC3 and DTS are reserved for commercial media sources and only if they contain such tracks; transcoding from any other source, including lossless (e.g., PCM and MLP formats), is not allowed.
↑_ 2.1.2. No transcodes or re-encodes of lossy releases are acceptable here.
↑_ 2.1.2.1. The only acceptable transcodes are releases that were transcoded from a lossless source (e.g., CD, SBD, DAT, Vinyl, SACD, or LPCM). Please refer to this wiki for more information on transcodes and how to detect them.
↑_ 2.1.2.2. Official lossy-mastered releases are not considered transcodes. They are allowed on the site. See this wiki for further information.
↑_ 2.1.2.3. Releases from Bandcamp, Beatport, and similar online retailers are considered official lossy-mastered releases when lossy mastered by the artist or label. A non-lossy mastered release from any source may trump a lossy mastered release from a WEB source. And if the same WEB retailer revises their release and subsequently supplies a non-lossy mastered release, the new source may trump the original upload.
↑_ 2.1.3. Music releases must have an average bitrate of at least 192 kbps regardless of the format. Exceptions: The following VBR encodes may go under the 192 kbps limit: LAME V2 (VBR), V1 (VBR), V0 (VBR), APS (VBR), APX (VBR), MP3 192 (VBR), and AAC ~192 (VBR) to AAC ~256 (VBR) releases. See this wiki for more information on encoding options.
↑_ 2.1.4. Bitrates must accurately reflect encoder presets or the average bitrate of the audio files. You are responsible for supplying correct format and bitrate information on the upload page. See this wiki for further information.
↑_ 2.1.5. Albums must not be ripped or uploaded as a single track.
↑_ 2.1.5.1. If the tracks on the original CD were separate, you must rip them to separate files. Unsplit rips may be present on the site but are NOT the preferred format for lossless rips. Any unsplit FLAC rips lacking a cue sheet will be deleted outright. Any unsplit FLAC rip that includes a cue sheet will be trumpable by a properly split FLAC torrent. CDs with single tracks can be uploaded without prior splitting. See this wiki for information on unsplit rips. Information about splitting rips can be found here. Users who upload unsplit rips will be warned.
↑_ 2.1.5.2. Gapless DJ or professional mixes released as MP3+CUE images are allowed as unseparated album images on the site. This includes scene DJ mixes. You cannot take a previously split collection of tracks and upload it as an unsplit mix because the original form of those audio tracks was not a single unsplit file. Such torrents will be removed when reported. Split and unsplit versions do not count as duplicates of one another and may coexist.
↑_ 2.1.5.3. For albums that contain separate tracks, unsplit MP3 albums are allowed for continuous albums and mixes only and must include a cue sheet. If there is no reason for the album to be uploaded unsplit, or if the torrent is lacking a cue sheet, it will be deleted. Exception: If the retail version of an unsplit MP3 album is sold without a cue sheet, you may upload the unsplit rip without a cue sheet.
↑_ 2.1.6. All music torrents must be encoded with a single encoder using the same settings.
↑_ 2.1.6.1. This means that you cannot create a torrent that contains both CBR and VBR files, nor can you upload torrents containing a mix of APS (VBR)/V2 (VBR) and APX (VBR)/V0 (VBR) files. Likewise, this means that you cannot upload torrents containing files of varying bit depths or sampling rates. Exceptions: If the source media was delivered in different bit depths (e.g., 16-bit and 24-bit) or sampling rates (e.g., 48 kHz and 96 kHz) you may upload a torrent containing audio files with different attributes.
↑_ 2.1.6.2. Some WEB-sourced albums are only available in hybrid collections (e.g., albums consisting of both 24-bit files and 16-bit files, 96 kHz-sampled and 48 kHz-sampled files, or stereophonic and monophonic files). If the online retailer supplies the files with such inconsistency, they are acceptable on the site. When requested by the staff, you must be able to provide proof of the WEB-sourcing in the form of web store receipts and album information indicating the non-uniform nature of the audio files. Label them according to the highest bit depth or sampling rate and be sure to note the variation in audio quality in the torrent description (e.g., Tracks 1, 2, and 3 are encoded at 24 bits while Tracks 4, 5, 6, and 7 are encoded at 16 bits).
↑_ 2.1.6.3. Including other kinds of audio quality differences in a torrent (e.g., duplicate lossy files in a lossless torrent) is prohibited. This kind of release is referred to as a "mutt rip".
↑_ 2.1.7. Use only the allowed container formats for audio files. Use .m4a and .mp4 for AAC, and .flac for FLAC only. All other formats should not be encapsulated in random containers (e.g., FLAC must not be in an Ogg container, MP3 must not be in an .m4a container, and so forth). Exceptions: DTS CD-sourced audio rips, although contained in WAV, should have the .dts extension (see 2.7).
↑_ 2.1.8. Music not sourced from vinyl must not contain pops, clicks, or skips. They will be deleted for rip/encode errors if reported. Music sourced from vinyl must follow the rules found here.
↑_ 2.1.9. Freely available music is allowed. Uploaded music may be freely available on the web (come from official sources such as record labels, band web sites, or the Internet Archive). Uploads can come from other torrent sites, but you are responsible for determining the audio quality of the music (e.g., that it is not transcoded, that it does not contain an edited log, that it is not a user compilation, etc.). Users are highly encouraged to provide a link to the source of their upload when uploading freely available music. However, this is not required and the lack of such a link to further information is not grounds for reporting a torrent. All freely available music must conform to both quality rules and formatting rules. This means it must be tagged correctly, not be a transcode, have separate tracks, and so forth. Freely available music uploads should have the "WEB" media format if no other source media (e.g., CD, DVD, etc.) can be established for the files.
↑_ 2.1.10. Clearly label water-marked or voice-over releases. Watermarks or voice-overs must be clearly indicated in the torrent description. The torrent will be deleted for quality misrepresentation if this information is not noted.
↑_ 2.1.11. Music ripped from the radio (Satellite or FM), television, the web, or podcasts are not allowed. See this wiki for the difference between web rips and the WEB category.
↑_ 2.1.12. No unofficial audience recordings may be uploaded. These include but are not limited to AUD (Audience), IEM (In Ear Monitor), ALD (Assistive Listening Device), Mini-Disc, and Matrix-sourced recordings (see 2.6.3).
↑_ 2.1.13. Tape (VHS, Video-8, etc.) music sources are not allowed, except for cassette rips and certain soundboards. See 2.6 for further information.
↑_ 2.1.14. The WEB media category is for digital downloads only. Digital downloads released only on the internet from internet sources cannot be given the CD media label on the upload page. This includes downloads from the iTunes Store, LiveDownloads, Beatport, Amazon.com, Rhapsody, and other web stores. Scene releases with no source information must be labeled as WEB. Freely available music with no source information must also be labeled as WEB. If possible, indicate the source of your files (e.g., the specific web store) in the torrent description. You are responsible for determining whether the downloaded files conform to Redacted's rules for music quality. Note: Do not confuse WEB-sourced files with web rips (see this wiki). WEB media torrents are not always web rips (meaning transcodes). Please check the spectrals before assuming that they are web rips.
↑_ 2.1.15. WEB uploads must be uploaded at the bit depths and sampling rates they were sold at. WEB uploads of the same audio with different sampling rates or bit depths may coexist if that is how they are sold or distributed. This means that if, for example, an album is sold with a bit depth of 24 bits and a sampling rate of 88.2 kHz, it must be uploaded directly with no modifications to the audio stream. An existing WEB upload of the same material with a bit depth of 24 and a sampling rate of 96 kHz may coexist with the new 24/88.2 upload but does not trump it. See 2.1.6.2 for more information.
↑_ 2.1.16. User-made compilations are not allowed.
↑_ 2.1.16.1. These are defined as compilations made by the uploader or anyone else who does not officially represent the artist or the label. Compilations must be reasonably official. For example, "34 of my favourite Grateful Dead songs" is not a reasonably official collection. Compiling a release from a list, such as a Top 100 Billboard Chart, is not allowed. User-made and unofficial multichannel mixes are also not allowed. See this wiki for more information.
↑_ 2.1.16.2. Exceptions: Bootlegs are allowed if they meet quality standards for music and are proven to be retail releases in either a digital or physical form. Bootlegs/mixtapes assembled and available from internet-only sources (e.g., music blogs, message boards, etc.) are not considered official enough for this site.
↑_ 2.1.17. No comedy, audiobook, or spoken word releases may be uploaded as music. These torrents must not be grouped with other formats from the same release (i.e., they need to have individual torrent pages). See 3.2 and this wiki for more information.
↑_ 2.1.18. Sound sample packs must be uploaded as applications. See 4.1.9 for more information.
↑_ 2.1.19. All music torrents must represent a complete release, and may not be missing tracks (or discs in the case of a multi-disc release).
↑_ 2.1.19.1. If an album is released as a multi-disc set (or box set) of CDs or vinyl discs, then it must be uploaded as a single torrent. Preferably, each individual CD rip in a multi-disc set should be organized in its own folder (see 2.3.15).
↑_ 2.1.19.2. A single track (e.g., one MP3 file) cannot be uploaded on its own unless it is an officially released single. If a specific track can only be found on an album, the entire album must be uploaded in the torrent.
↑_ 2.1.19.3. Bonus discs may be uploaded separately in accordance with 2.4. Please note that individual bonus tracks cannot be uploaded without the rest of the album. Bonus tracks are not bonus discs. Enhanced audio CDs with data or video tracks must be uploaded without the non-audio tracks. If you want to share the videos or data, you may host the files off-site with a file sharing service and include the link to that service in your torrent description.
↑_ 2.1.20. User made discographies may not be uploaded. Multi-album torrents are not allowed on the site under any circumstances. That means no discographies, Pitchfork compilations, etc. If releases (e.g., CD singles) were never released as a bundled set, do not upload them together. Live soundboard material should be uploaded as one torrent per night, per show, or per venue. Including more than one show in a torrent results in a multi-album torrent. Exceptions: Only official boxsets and official compilation collections can contain multiple albums.
↑_ 2.1.21. Pre-emphasis is allowed in lossless torrents only. Lossless FLAC torrents with pre-emphasis are allowed on the site. They are allowed to coexist with lossless de-emphasized torrents (both in their separate album edition groups). In contrast, lossy formats may not have pre-emphasis and will be deleted if uploaded.
↑_ 2.1.22. Edition Information must be provided for digitally-sourced torrents. Digitally-sourced (including CD-sourced) rips of albums that were first released before the availability of their source medium must have accurate edition information. For example, if a CD rip is of an album whose original release date was 1957, predating the creation and distribution of CDs, then the uploader must make note of the correct year in which the CD was pressed, and preferably note the catalog identification as well. Rips for which Edition Information cannot be provided must be marked as an "Unknown Release". Under no circumstances may you guess or feign knowledge of the Edition Information. See this wiki for more information on album editions.
↑_ 2.1.23. Audio can only be ripped from a video game CD under very specific circumstances. Audio ripped from a video game DVD is not allowed on site.
↑_ 2.1.23.1. This audio layer must comply with the Red Book standard for audio data. If there is no Red Book audio on the game disc, you may not upload a rip of the disc. Be prepared to provide extensive information on any audio that is ripped from a gaming disc (see this wiki for information about providing proof).
↑_ 2.1.23.2. The audio must meet the minimum requirements for music on the site (see 2.1.3 and 2.1.6).
↑_ 2.1.23.3. Officially-released game soundtracks, which adhere to Red Book standards, are always allowed.
↑_ 2.1.24. AAC torrents may only be uploaded if they represent editions unavailable on Redacted in any other format sourced from the same medium and edition (e.g., an iTunes AAC WEB release can co-exist with a CD release of the same edition). See 2.2.9.11 for information about trumping AAC torrents.
↑_ 2.1.25. No HDCD content may be uploaded to the site. 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 this wiki for more details on the media format.
↑_ 2.1.26. Downsampling of digital sources is allowed for certain media types. 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 2.8.5, 2.7.3, and 2.9.5 for more information.
↑ 2.2. Duplicates & Trumping
↑_ 2.2.0. Overview
Audio Dupe and Trump Chart

This chart is an overview of how the dupe and trump rules work.
↑_ 2.2.1. Upload an allowed format if it doesn't already exist on the site. If there is no existing torrent of the album in the format you've chosen, you can upload it in any bitrate that averages at least 192 kbps.
↑_ 2.2.2. Torrents that have the same bitrates, formats, and comparable or identical sampling rates for the same music release are duplicates. If a torrent is already present on the site in the format and bitrate you wanted to upload, you are not allowed to upload it - it's a duplicate (dupe). So if there's a 192 kbps CBR MP3 torrent on the site, you are not allowed to upload another 192 kbps CBR MP3 torrent for the same release. Similarly, if a torrent is already present on the site in the format and at the sampling rate you wanted to upload, you are not allowed to upload it - it's a duplicate (dupe). So if there's a 48 kHz WEB FLAC torrent on the site, you are not allowed to upload a 44.1 kHz WEB FLAC torrent for the same release. You cannot trump an existing torrent with another version solely because the new version includes album art. Exceptions: Different editions and source media do not count as dupes. See 2.2.11 for more information.
↑_ 2.2.3. Report all trumped and duplicated torrents. If you trump a torrent or notice a duplicate torrent, please use the report link (RP) to notify staff for removal of the old or duplicate torrent. This process is particularly vital for lossless rips. If you are uploading a superior rip to the current one in the same format on the site, report the older torrent and include a link to your new torrent in the report. Your torrent will be deleted as a dupe if the older torrent is not reported. Note: Trump - This occurs when a new torrent is uploaded in a preferred bitrate or quality (as specified by the lossy-, lossless-, and edition-specific rules below) and replaces the older version that exists on the site. Dupe - This occurs when a new torrent is uploaded in a bitrate or quality that is equal to the existing older version on the site. Because the two torrents cannot coexist, the most recent upload is considered a duplicate.
↑_ 2.2.4. Dupe rules also apply to previous uploads. All of the dupe rules below concerning music formats may apply to torrents uploaded at an earlier time. For example, if you upload an album in 192 kbps MP3, someone can upload the same album in 320 kbps at a later date and trump your 192 kbps MP3.
↑_ 2.2.5. Scene and non-scene torrents for the same release, in the same bitrate and format, are dupes. The Scene label does not make the torrents unique from one another. If a scene V0 (VBR) of an album from CD is already uploaded, you may not upload another V0 (VBR) of the same album from CD.
↑_ 2.2.6. All vinyl torrents must be ripped at the correct speed. You must rip all vinyl albums at the speed with which they were intended to be played (see 2.5.7).
↑_ 2.2.7. Complete or untouched releases replace incomplete or watermarked versions. Watermarked promos containing voice-overs and similar imperfections can be trumped by a non-watermarked release. Releases missing hidden or pre-gap tracks can be replaced by proper rips that include the entire range of tracks. These hidden or pre-gap tracks should be in their own file, not appended to the beginning of track one. Releases where the hidden or pre-gap track is appended to the first track can be trumped by one where the track is in a separate file.
↑_ 2.2.8. Torrents that have been inactive (e.g., not seeded) for two weeks may be trumped by the identical torrent (e.g., reseeded) or by a brand new rip or encode (see this wiki for the torrent inactivity rules) of the album. If you have the original torrent files for the inactive torrent, it is preferable to reseed those original files instead of uploading a new torrent. Uploading a replacement torrent should be done only when the files from the original torrent cannot be recovered or are unavailable.
↑_ 2.2.9. Lossy rules
↑_ 2.2.9.1. Higher bitrate CBR (constant bitrate) and ABR (average bitrate) torrents replace lower ones. Once a CBR (constant bitrate) rip has been uploaded, no CBR rips of that bitrate or lower can be uploaded. In the same manner, once an ABR (average bitrate) rip has been uploaded, no ABR rips of that bitrate or lower can be uploaded. For example, if a 320 kbps CBR rip is already on the site, you are not allowed to upload a 256 kbps CBR. ABR and CBR may be interchangeably trumped. A CBR can trump a lower bitrate ABR and an ABR may trump a lower bitrate CBR. You may not upload a 192 kbps CBR if a 256 kbps ABR of the same release is already up. For more information, see the Wikipedia articles on average bitrate, constant bitrate, and variable bitrate.
↑_ 2.2.9.2. Lossy format torrents with .log files do not replace equivalent existing torrents. If you want to upload a lossy format (e.g., MP3) torrent that contains a log, when that format already exists in the same medium and album edition (but without the log), your new torrent will be considered a dupe. For example, a V2 (VBR) MP3 torrent with a log cannot replace a V2 (VBR) MP3 without a log. The same standard applies for lossy audio torrents with .m3u, .cue, and other additions such as artwork. Exceptions: If an existing torrent contains encode/rip errors, you may upload another copy that does not have errors. The bad torrent needs to be reported (with clear information about which tracks and what time points are affected) or your torrent will be deleted as a dupe. Also, see 2.3.8 through 2.3.16 for replacing poorly named and tagged torrents.
↑_ 2.2.9.3. V0 (VBR) and 320 CBR MP3 are allowed at any time. You may upload a V0 (VBR) or 320 CBR MP3 as long as another rip with the same bitrate and format doesn't already exist. So if a V0 (VBR) is on the site, you may still upload a 320 CBR MP3 of the same release.
↑_ 2.2.9.4. V2 (VBR) replaces APS (VBR), and both replace CBR rips under 256 kbps, 192 (ABR), and rips averaging 192 (VBR) to 210 (VBR). Once a rip with either the V2 (VBR) or APS (VBR) LAME encoding preset has been uploaded, you are not allowed to upload any CBR torrents under 256 kbps bitrate. Furthermore, a V2 (VBR) or APS (VBR) rip will trump all indiscriminate VBR rips of similar bitrate. A V2 (VBR) rip will replace a 192 (VBR) rip or 210 (VBR) rip, for example. Also, a V2 (VBR) will replace a 192 (ABR) torrent.
↑_ 2.2.9.5. V0 (VBR) replaces APX (VBR), and both replace CBR rips under 320 kbps, V1 (VBR), V2 (VBR), all (ABR) rips, APS (VBR), and all other non-LAME preset (VBR) rips. Once a rip with either the V0 (VBR) or APX (VBR) LAME encoding preset has been uploaded, you are not allowed to upload any CBR torrents under 320 kbps bitrate. Furthermore, a V0 (VBR) or APX (VBR) rip will trump all indiscriminate VBR rips (of 192 kbps average bitrate or higher). A V0 (VBR) rip will replace a 256 (VBR) rip, for example. You may not upload a V1 (VBR) LAME encoding preset if either V0 (VBR) or APX (VBR) are already present.
↑_ 2.2.9.6. No constant bitrate encodes higher than 320 CBR are allowed on the site. You may upload MP3 files from 192 kbps to 320 kbps if no torrent exists in that format for a release. Any CBR bitrates under 192 kbps and bitrates higher than 320 kbps will be deleted. See 2.2.9.1 for more information.
↑_ 2.2.9.7. Non-LAME preset VBR rips do not replace each other. Similar bitrate VBR encodes are considered dupes. Thus, a 192 (VBR) is allowed to coexist with a significantly higher VBR encode. You may not upload a 224 (VBR) if a 256 (VBR) is already present, nor vice versa.
↑_ 2.2.9.8. V2 (VBR) and V0 (VBR) LAME encodes trump APS (VBR) and APX (VBR) respectively, and V0 (VBR) trumps V2 (VBR). V2 (VBR) trumps an APS (VBR) encode of the same release. Once a V2 (VBR) is uploaded, you may not upload an APS (VBR) encode. V0 (VBR) trumps an APX (VBR) encode of the same release. Once a V0 (VBR) is uploaded, you may not upload an APX (VBR) encode.
↑_ 2.2.9.9. Encoding profiles/object types at the same bitrate are not unique uploads. A 256 (VBR) in LC profile is a dupe if a 256 (VBR) HE object type encode already exists on the site. Similarly, different extensions (.m4a and .mp4) count as dupes if available in the same bitrate.
↑_ 2.2.9.10. VBR AAC encodes can be trumped by 256 CBR encodes. Any VBR AAC encode, regardless of encoder used, may be deleted in favor of 256 CBR encodes. This includes 320 (VBR) encodes or encodes made with Nero presets.
↑_ 2.2.9.11. An AAC encode can be trumped by an allowed encode of the same medium and edition. Note: For WEB torrents, comparisons of audio quality and source reliability will determine whether or not an MP3 may trump an AAC (at the discretion of the moderator involved).
↑_ 2.2.9.12. Only one lossy vinyl rip in a specific bitrate is allowed per edition. See 2.5.2.
↑_ 2.2.9.13. Any lossy formats must be encoded at the same sampling rate as their lossless source. FLAC files from a CD rip (sampled at 44.1 kHz) can only be transcoded to 44.1 kHz lossy formats. Any 48 kHz lossy formats for the same release that are uploaded after the 44.1 kHz torrents are on the site are considered dupes. FLAC files from a WEB FLAC (sampled at 48 kHz) can only be transcoded to 48 kHz lossy formats. If the 48 kHz FLAC torrent is uploaded, and the lossy formats are populated for this album at 48 kHz, no 44.1 kHz torrents (lossless or lossy) may be uploaded because those later torrents will be considered dupes.
↑_ 2.2.10. Lossless rules
↑_ 2.2.10.1. All FLAC CD rips must come from official CD sources.
↑_ 2.2.10.1.1. Rips must be taken from commercially pressed or official (e.g., artist- or label-approved) CD sources. They may not come from CD-R copies of the same pressed CDs.
↑_ 2.2.10.1.2. Exceptions: If the release is only distributed on CD-R by the label or artist, then that is acceptable. See this wiki for more information on CD-R releases.
↑_ 2.2.10.2. A FLAC torrent without a log (or with a log from a non-EAC or non-XLD ripping tool like dBpoweramp or Rubyripper) may be trumped by a FLAC torrent with a log from an approved ripping tool that scores either 100% or <100% because of non-audio deductions. For example, an EAC log that scores 50% (because of CRC mismatches or other audio deductions) cannot trump a Rubyripper log. See this wiki for more information on approved ripping tools. Also, see this wiki for setting up EAC and this wiki for ripping with EAC. See this wiki for ripping with XLD. Please make sure the log file has the ".log" extension so that it can display properly on the torrent page.
↑_ 2.2.10.3. A FLAC upload with an EAC or XLD rip log that scores 100% on the log checker replaces one with a lower score. No log scoring less than 100% can trump an already existing one that scores under 100%. For example, a FLAC+log rip that scores 50% in the log checker cannot be trumped by a FLAC+log rip that scores 80%. Redacted recommends this guide for EAC, and this guide for XLD. See this wiki for more information about the site log checker.
↑_ 2.2.10.3.1. A 100% scoring log containing a valid checksum or signature can trump a 100% rip log lacking a valid checksum or signature. An EAC or XLD log that passes checksum or signature validation may replace an already present 100% rip if it belongs to the same distinct edition. These torrents have the "Trumpable" label.
↑_ 2.2.10.3.2. EAC 0.99 rips that score 100% and were ripped before 2017 count as "Perfect" FLACs. These EAC 0.99 rips count towards userclass advancement. However, they are subject to trumping with a 100% log containing a checksum or signature. These torrents also have the "Trumpable" label.
↑_ 2.2.10.4. A FLAC upload with only non-audio deductions in the log (see this wiki) may replace a FLAC upload with a log that scores 0% or contains audio deductions. For example, a log with a non-audio deduction (e.g. ID3 tags added to FLAC files) can trump a log that has audio deductions for mismatching track CRCs.
↑_ 2.2.10.5. XLD and EAC logs in languages other than English require a manual log checker score adjustment by staff. The current log checker 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" button and select "Log Rescore Request" for the reason of the report so staff can score your torrent manually. Do not translate the log yourself (see 2.2.10.9).
↑_ 2.2.10.6. Range rips may be re-adjusted if they are used only for extracting hidden tracks. Some CDs contain HTOA (Hidden Track One Audio), which is a track hidden before the start of Track 1 on a disc. For a proper extraction, follow this wiki. Full album range rips are not covered by this rule.
↑_ 2.2.10.6.1. The new log checker 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 log checker has decreased your score for the hidden track, report the torrent and the log score will be corrected by staff.
↑_ 2.2.10.6.2. Full album range rips are subject to point deductions when scored by the log checker, and they must be split properly to comply with site formatting rules.
↑_ 2.2.10.6.3. The CD image rip must be split with CUETools, XLD, or EAC. See this wiki for splitting image rips with EAC and this wiki for CueTools.
↑_ 2.2.10.7. A 100% log rip lacking a cue sheet can be replaced by another 100% log rip with a noncompliant cue sheet. See this wiki for more information on cue sheets.
↑_ 2.2.10.8. FLAC rips that contain ID3 tags or other non-compliant tags for FLAC may be trumped by rips with identical scores that have the 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 because of 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 tag clean-up in the "Release description", or your torrent may be deleted as 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 compressing the files to FLAC, and adding the proper Vorbis comments.
↑_ 2.2.10.9. No log editing is permitted.
↑_ 2.2.10.9.1. Forging log data is a serious misrepresentation of quality, and will result in a warning and the loss of your uploading privileges when the edited log is found. We recommend that you do not open the rip log file for any reason. However, if you must open the rip log, do not edit anything in the file for any reason. If you discover that one of your software settings is incorrect in the ripping software preferences, you must rip the CD again with the proper settings. Do not consolidate logs under any circumstances. If you must re-rip specific tracks or an entire disc and the rip results happen to have the new log appended to the original, leave them as is. Do not remove any part of either log, and never copy/paste parts of a new log over an old log.
↑_ 2.2.10.9.2. If you find that an appended or combined log has not been scored properly, please report the torrent for a manual rescore.
↑_ 2.2.10.10. FLAC files must be compressed. We strongly recommend that FLAC files be compressed to Level 8. Lack of compression can increase the torrent size by 5% or more. Any torrents that have uncompressed FLAC files may be reported and trumped.
↑_ 2.2.10.11. Any lossless formats must be encoded at the same sampling rate as their lossless source material. Lossless files from a Red Book-compliant CD rip (sampled at 44.1 kHz) can only be encoded to 44.1 kHz FLAC files for uploading in lossless torrents. Any 48 kHz lossless torrents for the same release are considered dupes. FLAC files from a WEB FLAC (sampled at 48 kHz) can only be uploaded as 48 kHz FLAC torrents. Any 44.1 kHz torrents for the same release are considered dupes. When albums are available in a number of different lossless formats (44.1 kHz, 48 kHz, 96 kHz, etc.) the first lossless torrent that is uploaded to the site may remain while all subsequent versions are considered dupes. See 2.2.2 and 2.2.9.13 for more information.
↑_ 2.2.11. Editions and Releases rules
↑_ 2.2.11.1. Different editions and source media count as separate releases.
↑_ 2.2.11.1.1. A rip from a different medium (e.g., vinyl) or release (e.g., a remaster) of an already existing torrent counts as a different edition. The dupe rules do not apply to the two different album editions, nor do they apply to two differently sourced torrents. So if a FLAC ripped from a CD is already up, you are still allowed to upload a FLAC ripped from vinyl. And if a 320 kbps CBR MP3 release for an original mastering of an album was uploaded, you are still allowed to upload a 320 kbps CBR MP3 remaster. See this wiki for the procedure on how to enter album edition information for a torrent.
↑_ 2.2.11.1.2. Only one edition of each unofficial live recording is allowed. See 2.6.2.
↑_ 2.2.11.2. Rip log information (ToC, peak levels, and pre-gaps), tracklist, and running order determine distinct editions, not catalog information. Merely having different catalog numbers or CD packaging is not enough to justify a new, distinct edition, though differences in year, label (imprint), or catalog number determine distinct releases. Though different editions may coexist, distinct releases that are not also distinct editions may not, and are considered dupes. See this wiki for more information.
↑_ 2.2.11.3. Multiple releases may be grouped into one edition. In such a case, torrents belonging to any of the releases determined to be in the same edition are considered dupes. Conversely, release groups may be split into more than one edition when it is determined that there is a material difference in audio content (different editions that have the same catalog information are known as "silent remasters"), in which case other formats may be uploaded for both editions.
↑_ 2.2.11.4. Lossless uploads with edition information trump lossless rips with nonexistent or insufficient logs and no release information. An insufficient log is a log that doesn't provide any information (e.g., ToC, peak levels, and pre-gaps) about the audio being ripped.
↑_ 2.2.11.5. If a lossless torrent has no release information (an "unknown release") but does have a log containing ToC, peak level, and pre-gap information, it cannot be trumped by a lossless torrent with release information unless the "lossless unknown release torrent" can be determined to be the same edition as a lossless torrent for which the release information is known. If such an identification can be made, the "lossless unknown release torrent" (and all lossy torrents that can be identified as transcodes of it) is moved into the same edition as the lossless torrent with edition information, and the merged torrents are then subject to dupe and trump rules as per 2.2.11.2. If the rip log is incomplete (missing ToC, peak level, or pre-gap information) and the information available matches a torrent in an edition whose release information is known, the torrent whose release information is known trumps the torrent whose release information is unknown.
↑_ 2.2.11.6. Lossy torrents with release information trump unknown release torrents if they share the same tracklist and running order, with one exception. If it can be established that a lossy Unknown Release torrent is a transcode of an Unknown Release FLAC, and the Unknown Release FLAC is moved into an edition whose release information is known as per 2.2.11.5, then all lossy transcodes of it are moved with it and are treated as any other lossy torrents already present in the edition as per 2.2.11.2.
↑_ 2.2.11.7. Bonus disc-only uploads can coexist with the complete set in accordance with the trumping rules. A bonus disc-only release can be trumped by an upload containing the "full" original album + bonus discs, in the same format, in accordance with the usual trumping rules (see 2.4 for the rules specific to bonus materials).
↑_ 2.2.11.8. Unknown Release torrents may be trumped by seemingly identical torrents whose Edition Information can be verified. Torrents marked as "Unknown Release" are eligible to be trumped by rips sourced from the same medium, with the same track listing and running order, whose source Edition Information is provided and can be verified.
↑_ 2.2.11.9. Only one lossless and two 24-bit lossless vinyl rips are allowed per edition. A poor sounding lossless rip may be trumped by a better sounding lossless rip, regardless of lineage information. The same quality trump can occur for 24-bit lossless rips. To trump an older torrent for a better sounding version, you need to report it with clear information about how your rip sounds better than the other one (e.g., specific tracks where the audio is appreciably improved, specific time points that demonstrate the improvement, etc.). Rips of extremely poor quality may be deleted outright if reported. All quality trumps/deletions of this nature are at the discretion of the moderator involved. See 2.5.
↑ 2.3. Formatting
↑_ 2.3.1. Music releases must be in a directory that contains the music. This includes single track releases, which must be enclosed in a torrent folder even if there is only one file in the torrent. No music may be compressed in an archive (e.g., .rar, .zip, .tar, .iso). Scene archives of music must be unpacked and not labeled as "scene".
↑_ 2.3.2. Name your directories with meaningful titles, such as "Artist - Album (Year) - Format". The minimum acceptable is "Album" although it is preferable to include more information. If the directory name does not include this minimum then another user can rename the directory, re-upload, and report your torrent for deletion. In addition, torrent folders that are named using the scene convention will be trumpable if the Scene label is absent from the torrent.
↑_ 2.3.3. Avoid creating unnecessary nested folders (such as an extra folder for the actual album) inside your properly named directory. A torrent with unnecessary nested folders is trumpable by a torrent with such folders removed. For single disc albums, all audio files must be included in the main torrent folder. For multi-disc albums, the main torrent folder may include one sub-folder that holds the audio file contents for each disc in the box set, e.g., the main torrent folder is "Adele - 19 (2008) - FLAC" while appropriate sub-folders may include "19 (Disc 1of2)" or "19" and "Live From The Hotel Cafe (Disc 2of2)" or "Acoustic Set Live From The Hotel Cafe, Los Angeles". Additional folders are unnecessary because they do nothing to improve the organization of the torrent. If you are uncertain about what to do for other cases, PM a staff member for guidance.
↑_ 2.3.4. Label your torrents according to site standards. For examples, see torrent naming suggestions guide for help on how to name your uploaded torrents properly. Use the Edition Information box on the upload page to denote different editions or versions of an album (e.g., censored version versus an uncensored version). If you need help merging or editing your upload, please request help in this forum. For the album category/release type, follow the guidelines here.
↑_ 2.3.5. Torrents should never have [REQ] or [REQUEST] in the title or artist name. If you fill a request using the Requests system, everyone who voted for it will be automatically notified.
↑_ 2.3.6. Torrent album titles must accurately reflect the actual album titles. Use proper capitalization when naming your albums. Typing the album titles in all lowercase letters or all capital letters is unacceptable and makes the torrent trumpable. For detailed information on naming practices see this wiki. Any descriptions like [Advance] or [CDM] (if you must use them) should be entered in the Edition Information box on the upload page, not in the title. Exceptions: If the album uses special capitalization, then you may follow that convention.
↑_ 2.3.7. The Artist field in the torrent name should contain only the artist name. Do not add additional information about the artist in the artist field unless the album credits the artist in that manner. For example, "Artist X (of Band Y)" or "Band X (feat. Artist Y)". It is recommended that you search existing torrents for the artist name so that you can be sure that you name the artist the exact same way. A torrent with a proper artist name will be grouped with the existing torrents for that artist on a common artist page, and thus will be easy to find. Capitalization problems will also make a torrent trumpable. Labeling the artist incorrectly prevents your torrent from being grouped with the other torrents for the same artist. See this wiki for more information.
↑_ 2.3.8. The year of the original recording should be used for the "Year" field on the upload page. Use the recording year for "Year of the original release" (if you can establish it), and use the option to add the release year for the album or edition you are uploading in the Edition Information on the upload page. For example, all editions of The Beatles (White Album) would have 1968 in the main Year box. However, each of the various mono pressings, remasters, re-releases, expanded editions, reconstructions, etc. would have its respective release year in the Edition Information box.
↑_ 2.3.9. All lossless analog rips should include clear information about source lineage. All lossless SACD digital layer analog rips must include source information. SACD rips without source lineage are subject to deletion. Vinyl rips should include lineage information, but vinyl rips can still be uploaded without a lineage. Lineage should clear information about recording equipment used (see 2.8). If you used a USB turntable for a vinyl rip, clearly indicate this in your lineage information. Also include all intermediate steps up to lossless encoding, such as the program used for mastering, sound card used, etc. Lossless analog rips missing rip information can be trumped by better documented lossless analog rips of equal or better quality. In order to trump a lossless analog rip without a lineage, this lineage must be included as a .txt or .log file within the new torrent.
↑_ 2.3.10. All lossless soundboard recordings must include clear information about source lineage. This information should be displayed in the torrent description. Optionally, the uploader may include the information in a .txt or .log file within the torrent. Lossless soundboard recordings missing lineage information will be deleted if reported (see 2.6.7).
↑_ 2.3.11. File names must accurately reflect the song titles. You may not have file names like 01track.mp3, 02track.mp3, etc. Torrents containing files that are named with incorrect song titles can be trumped by properly labeled torrents. Also, torrents that are sourced from the scene but do not have the Scene label must comply with site naming rules (no release group names in the file names, no advertisements in the file names, etc.). Note that these must be substantial improvements such as the removal of garbage characters. Small changes such as diacritical marks are insufficient grounds for trumping. English translations of song titles in file names are encouraged but not necessary for foreign language song titles. If all the letters in the track titles are capitalized, the torrent is trumpable. Exceptions: Rare albums featuring no track listing or untitled tracks may have file names like 01track.mp3, 02track.mp3, and so forth. Please note this track list in the "Album description". If foreign language characters create playback problems for some systems and cannot be coherently translated, file names such as "01track" are acceptable for those few cases.
↑_ 2.3.12. The maximum character length for files is 180 characters. 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 90 characters. 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), any sub-folders, and files within that torrent folder. For example, unnecessarily nested folders will count towards this limit; lengthy classical music file names will count towards this limit.
↑_ 2.3.13. Track numbers are required in file names (e.g., "01 - TrackName.mp3"). 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 2.3.14. Exception: Track numbers are not required for single-track torrents.
↑_ 2.3.14. When formatted properly, file names will alphabetically sort into the original playing order of the release.
↑_ 2.3.14.1.For albums with more than one artist, if the name of the artist is in the file name, it must come after the track number in order for the tracks to sort into the correct order. 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. Note: there is no requirement for artist names to be in the track file names, other than 2.3.16.2. Torrents that have improperly-formatted or incomplete file names will be trumpable.
↑_ 2.3.14.2.If a torrent has subfolders for multiple discs of a release, these subfolders must sort by disc order. If each disc has a title (torrents.php?id=19000, for example) and the discs are not numbered, this rule does not apply, and each subdirectory should have the disc name included.
↑_ 2.3.15. Multiple-disc torrents cannot have tracks with the same numbers in one directory. 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 tracks. 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.
↑_ 2.3.16. Properly tag your music files.
↑_ 2.3.16.1.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 2.2.10.8). ID3v2 tags for files are highly recommended over ID3v1.
↑_ 2.3.16.2.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 2.3.14.
↑_ 2.3.16.3.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 this wiki for more information on ID3 tags.
↑_ 2.3.16.4.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:
Artist
Album
Title
Track Number
Note: The "Year" tag is optional but strongly encouraged. However, if missing or incorrect, this is not grounds for trumping a torrent.
↑_ 2.3.17. The torrent artist for classical works should use the full composer name. Also, consult this wiki for a full explanation of the classical music tagging system.
↑_ 2.3.18. Newly re-tagged torrents trumping badly tagged torrents must reflect a substantial improvement over the previous tags. 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 MusicBrainz or Discogs. 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 MusicBrainz and in Discogs. 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 tagging guidelines.
↑_ 2.3.19. Avoid embedding large images in file metadata. The combined size of embedded images and padding may not exceed 1024 KiB per file. You may include the artwork separately if it is too big. When removing embedded images, make sure that the padding is removed or reduced to a few kilobytes. Refer to this wiki article for more information.
↑_ 2.3.20. Leading spaces are not allowed in any file or folder names. 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.
↑ 2.4. Bonus Content
↑_ 2.4.1. All music torrents must represent a complete release, and may not be missing tracks or discs (see 2.1.19). Bonus tracks or bonus discs should be uploaded as a complete release with the main album. Do not cobble together main album and bonus content from different sources if you do not have the complete release. Such torrents will be regarded as mutt rips or user compilations, and a staff member may ask for proof of the torrent's authenticity.
↑_ 2.4.2. A FLAC bonus disc-only release is not automatically deleted due to the presence of the complete set (Album + Bonus disc). An upload consisting solely of a bonus disc can only be trumped by the complete set when the trumping torrent's log score qualifies based on the usual lossless rules (see 2.2.10). No bonus disc-only upload can trump a complete set that has a total score of 100%.
↑_ 2.4.3. When a "perfect" FLAC rip (with a log scoring 100%) of the complete release (including the bonus disc) is uploaded, all bonus disc-only torrents are considered dupes of the complete set.
↑_ 2.4.4. A lossy bonus disc-only torrent can be trumped by the complete set in the same format and bitrate.
↑_ 2.4.5. Exclusive bonus content from services such as iTunes or Amazon may be uploaded in a separate torrent but may be trumped by a complete torrent containing the full digital release and bonus material. For instance, an iTunes release that contains two iTunes bonus tracks may have a torrent uploaded of solely the two bonus tracks, though it remains trumpable by the complete iTunes release that includes the bonus material.
↑_ 2.4.6. Lossy bonus content which is otherwise unavailable may be uploaded in a separate torrent and must not be included in the same torrent as the original album, as to avoid creating mutt rips in accordance with 2.1.6.3. This includes, but is not limited to: Bonus MP3 content provided in the data portion of a CD, "subscription" bonus material where content is released (gradually or wholly) to subscribers or fan club members, or downloadable exclusives for purchasers of a release. All lossy bonus content must meet the minimum bitrate requirements of 2.1.3.
↑_ 2.4.7. Mixed media sets are to be uploaded as one torrent per medium. For example, a release which contains a CD, a vinyl, and a cassette in one package must be uploaded as three separate torrents, with one torrent containing the CD content, another torrent containing the vinyl content, and another torrent containing the cassette content (in compliance with the tape rip requirements in 2.10).
↑ 2.5. Vinyl
↑_ 2.5.1. Downsampling of analog rips is allowed. Analog rips that have been downsampled may be uploaded (e.g., a 24/96 vinyl rip downsampled to 16/44.1). Any downsampled torrents must include the specific programs and methods used to downsample in addition to the lineage for the original rip or it will be deleted.
↑_ 2.5.2. Only one lossy vinyl rip in a specific bitrate is allowed per edition. Once someone has uploaded a lossy format vinyl rip (in MP3), you may not upload another copy in the same bitrate. It does not matter whether or not the lossy files are of differing sampling rates. For example, if a 44.1 kHz V2 (VBR) copy is already up, you may not upload the same album in V2 (VBR) at 48 kHz.
↑_ 2.5.3. Only one 16-bit lossless vinyl rip is allowed per edition. Lossless 16-bit vinyl rips must have a sampling rate of either 44.1 kHz or 48 kHz. Upsampling of rips is strictly forbidden. See this wiki for vinyl ripping information and this wiki for general information on the vinyl medium.
↑_ 2.5.4. A maximum of two 24-bit lossless vinyl rips are allowed per edition: A lossless 24-bit rip with sampling rate equal to 192 kHz and a lossless 24-bit rip with sampling rate equal to 44.1, 48, 88.2, or 96 kHz. Lossless 24/96 vinyl rips trump 24/44.1, 24/48, and 24/88.2 rips. Two or more lossless 24-bit vinyl rips with sampling rates equal to 44.1, 48, or 88.2 kHz are considered dupes. So a 24/88.2 rip and a 24/48 rip of the same material are considered dupes. Rips must sound as good as or better than the rips they are attempting to trump (see 2.2.11.9 for examples of trumping proofs). Upsampling of rips is strictly forbidden. See this wiki for more information on 24-bit vinyl ripping.
↑_ 2.5.5. Vinyl rips may be trumped by better-sounding rips of the same bit depth, regardless of lineage information (see 2.3.9).
↑_ 2.5.5.1. Lossless 16-bit rips may be trumped by better-sounding lossless 16/44.1 or 16/48 rips.
↑_ 2.5.5.2. Lossless 24-bit rips with sampling rate equal to 44.1, 48, 88.2, or 96 kHz may be trumped by better-sounding lossless 24/96 rips.
↑_ 2.5.5.3. Lossless 24-bit rips with sampling rate equal to 192 kHz may be trumped by better-sounding lossless 24/192 rips.
↑_ 2.5.5.4. Lossy vinyl rips may be trumped by substantially better-sounding lossy vinyl rips when the difference in quality is obvious. To trump an old rip with a new torrent that may be a better sounding version, you need to report it with clear information about how your rip sounds better than the other one, with references to specific tracks and time positions to justify your report (see 2.2.11.9). The following are acceptable reasons to both report and/or remove a torrent.
↑_ 2.5.5.4.1. The vinyl audio was captured at the wrong playback speed.
↑_ 2.5.5.4.2. At least one track has a constant level of static.
↑_ 2.5.5.4.3. At least one track has a noticeable pop or click. This pop must be visible in the frequency spectrals for the track and should last 1/20th of a second.
↑_ 2.5.5.4.4. There is noticeable wobbling during playback.
↑_ 2.5.5.4.5. The needle drop is audible.
↑_ 2.5.5.4.6. At least one track is truncated or improperly split.
↑_ 2.5.5.5. Rips of extremely poor quality (lossy or lossless) may be deleted outright if reported. All quality trumps/deletions of this nature are at the discretion of the moderator involved.
↑_ 2.5.6. Lossy transcodes of lossless vinyl rips trumped under rule 2.2.11.9 and the rules in this section are trumpable by lossy transcodes of the trumping vinyl rips. For example, lossy torrent A and lossless torrent A exist on the site. A new vinyl rip (lossless torrent B) is uploaded and trumps lossless torrent A (the old vinyl rip). All lossy transcodes from lossless torrent B will automatically trump the corresponding lossy torrents transcoded from lossless torrent A; only the torrent B formats will remain on the site. So that the correct source for the lossless rip can be easily identified, you are strongly encouraged to mention or link to the vinyl rip that you are using for the lossless-to-lossy transcode and to reproduce its lineage in the release description of transcodes that you upload.
↑_ 2.5.7. All vinyl torrents must be ripped at the correct speed. You must rip all vinyl albums using the speed at which they were intended to be played. For example, you may not rip a 45 rpm vinyl at 33 rpm and upload it to the site. In addition, turntables that have been improperly calibrated, and therefore play back LPs at an incorrect speed, will cause pitch changes that are noticeable. Any such vinyl albums that were captured at the wrong playback speed will be deleted once reported.
↑ 2.6. Live Music and Soundboards
↑_ 2.6.1. Live soundboard material should be uploaded as one torrent per show.
↑_ 2.6.2. Only one edition of each unofficial live recording is allowed. Such bootlegs and mixtapes can be unofficially remastered several times, and such constant remastering is of little consequence on a site where bootlegs are not the primary focus. Only one unofficial soundboard recording of each show is allowed, and it should be uploaded on the torrent page in the absence of any edition information. See this wiki for more information on how live music is organized on the site.
↑_ 2.6.3. No unofficial audience recordings.
↑_ 2.6.3.1. AUD (Audience), IEM (In Ear Monitor), ALD (Assistive Listening Device), Mini-Disc, and Matrix-sourced recordings cannot be uploaded.
↑_ 2.6.3.2. Officially-remastered AUD/IEM/ALD/Mini-Disc/Matrix recordings are allowed. These may be re-appropriated recordings released with the artist's or their label's consent. Bonus tracks from such recording sources are also exempt. Be prepared to provide clear proofs of such re-releases to the staff when asked.
↑_ 2.6.4. Soundboards must comprise complete shows. Incomplete shows will be deleted.
↑_ 2.6.5. Soundboards may not include soundchecks. Those uploaded with a soundcheck will be deleted.
↑_ 2.6.6. One tape generation and one CD-R generation are allowed for each soundboard upload.
↑_ 2.6.6.1. The tape generation must be the first generation. For example, there can be a master tape and then a subsequent tape (with no other transfer in between). Any additional tape generations beyond the secondary tape will require staff approval.
↑_ 2.6.6.2. If a limited number of tracks (at the discretion of the staff member involved) have been patched with a short amount of tape-sourced data you may still upload the recording but this information must be clearly stated in the lineage and the album description.
↑_ 2.6.7. Include lineage information for each soundboard recording (see 2.3.10).
↑_ 2.6.7.1. Lineage information for a soundboard recording is highly recommended.
↑_ 2.6.7.2. If a soundboard is uploaded without a lineage, and a lineage is later found that contains more than one tape or CD-R generation, then the uploader will be warned and the torrent deleted.
↑_ 2.6.7.3. No lineage editing or misrepresentation will be tolerated. 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.
↑_ 2.6.8. Soundboards must be uploaded according to this naming and uploading guide and according to this wiki on site organization.
↑_ 2.6.9. The following lists should illustrate when Live music may or may not be uploaded.
↑_ 2.6.9.1. Allowed Live Music
Live album bought from an online retailer
CD bought from a brick & mortar store
Soundboard recording that follows the Live Music rules
Soundboard recording that has been adopted by the artist
WEB-sourced live bootleg (released by the artist or a record label)
CD-sourced live bootleg (released by the artist or a record label)
Bootleg album that was later sanctioned by the record label
Soundboard recordings containing a tape generation in the lineage; this will require staff approval unless the tape generation is the first generation
↑_ 2.6.9.2. Disallowed Live Music
Unofficial live mix of a studio album (no artist or record label involvement)
Vanity House mix
Incomplete soundboard recordings
Soundboard recordings containing sound checks or other non-performance portions
Collection of random live tracks from a single artist
Collection of random live tracks from multiple artists
Collection of remixed live tracks
Radio broadcast of a live performance
↑ 2.7. Multichannel
↑_ 2.7.1. The only lossy multichannel audio formats allowed are AC3 and DTS. If the source is DTS or AC3, do not transcode to other formats. Exceptions: Transcoding is allowed if the source is lossless (LPCM or MLP). Those should be compressed with multichannel FLAC. See this wiki for more information.
↑_ 2.7.2. DTS-CD rips cannot be re-compressed to a lossless codec and they must be kept as WAV files with the .dts extension.
↑_ 2.7.3. A multichannel lossless rip of multichannel source media must have the same number of and arrangement of channels as the source media. 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 encoded at the original bit depth and sampling rate as the files on disc.
↑_ 2.7.4. A multichannel rip of source media that includes both multichannel and stereo streams may coexist with a rip of the stereo stream off the same media. A rip of the stereo stream trumps a downmix of the multichannel rip. However, if there is no rip of a stereo stream uploaded, a stereo downmix of a rip from the multichannel stream may coexist with a multichannel rip of the same stream. For example, a DVD-Audio disc may include both stereo LPCM (Linear Pulse-Code Modulation) audio and 5.1 MLP (Meridian Lossless Packing) audio. In this case, a stereo rip of the LPCM stream could coexist with a 5.1 rip of the MLP stream, and the stereo LPCM rip would trump a stereo downmix of a multichannel MLP stream rip. If no stereo LPCM rip of this source media was uploaded, a stereo downmix of the MLP stream could coexist with a 5.1 multichannel rip of the MLP stream.
↑_ 2.7.5. Be aware of the special tagging rules for AC3 torrents (see 2.3.16).
↑ 2.8. SACD
↑_ 2.8.1. Digital rips produced by the PlayStation 3 (PS3) - SACD ripper process (see this wiki) trump any other SACD digital or analog rips (e.g., Oppo method, analog output to ADC, DSD stream from a SACD player, etc.). Non-PS3 digital SACD rips trump analog SACD rips. Torrents containing a 88.2 kHz digitally-sourced PCM stream compressed with FLAC are trumpable by new digital rips made directly from the SACD disc using the PS3-SACD ripper method. See this wiki for more information on the SACD format. Note: This means that you cannot download another user's uncompressed DSD source files and manipulate those.
↑_ 2.8.2. Analog SACD rips may have a sampling rate equal to 88.2 or 96 kHz and may be trumped at any time by a digital 24/88.2 SACD rip. If a digital SACD rip has frequencies higher than 44.1 kHz, contact a moderator privately for approval to upload a 24-bit rip with a sampling rate greater than 88.2 kHz.
↑_ 2.8.3. SACD hybrid rip sources must be properly labeled.
↑_ 2.8.3.1. SACD hybrid discs ripped from the CD layer should be labeled as CD and not SACD. If you used your CD/DVD drive and a CD ripper (such as EAC) to extract the audio, then label it as "CD" sourced because it is not true 24-bit audio.
↑_ 2.8.3.2. If the rip came from the genuine digital SACD layer via a PS3 player or through a SACD player mod or line out, it should be 24-bit quality SACD. You may include "SACD Hybrid" in the Edition Information box on the upload page.
↑_ 2.8.4. Lineage information for an SACD capture is required and should be included in the torrent folder.
↑_ 2.8.4.1. Both digital and analog SACD rips require lineage information that includes the SACD ripping process, equipment used, applicable conversion software (with the conversion settings), and any post-capture software mastering that was performed. Any torrents that lack this lineage information are trumpable.
↑_ 2.8.4.2. Digital rips that use the Saracon or Philips converters will trump foobar rips that use the SACD_input converter; all three of these rips would trump a digital rip that uses the Audiogate converter.
↑_ 2.8.4.3. Digital rips created from the Saracon and Philips converters must be "de-clicked" (PM a moderator for details on the process, which consists of trimming 53 samples from the DFF file and then prepending and appending 12 samples back onto the file during the conversion process).
↑_ 2.8.4.4. No lineage editing or misrepresentation will be tolerated. 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.
↑_ 2.8.5. Downsampling of SACD sources is allowed in certain cases.
↑_ 2.8.5.1. A multichannel lossless rip must have the same number of and arrangement of channels as the source media. 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.
↑_ 2.8.5.2. Downmixing of SACD sources is prohibited. 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.
↑_ 2.8.5.3. All lossy SACD torrents must be uploaded in a Red Book-compliant form. 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.
↑ 2.9. Blu-ray
↑_ 2.9.1. Only digital rips of the lossless audio track from a Blu-ray disc may be uploaded (see this wiki for more information). 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 2.1.1 and 2.7.1 for more information on multichannel audio material on the site.
↑_ 2.9.2. Uploading movie audio tracks is prohibited. 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.
↑_ 2.9.3. Blu-ray rip sources must be properly labeled.
↑_ 2.9.3.1. If the source was lossy (e.g., AC3 or DTS) do not transcode to other formats.
↑_ 2.9.3.2. If the source was a genuine lossless track, identify the track in the album edition field, e.g., "16-bit PCM" or "24-bit DTS-HD MA 5.1". Sampling rate information may also be included (e.g., "16/48 LPCM") in the album edition field.
↑_ 2.9.4. Lineage information for a Blu-ray transfer is required and should be included in the torrent folder.
↑_ 2.9.4.1. 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. Any torrents that lack this lineage information are trumpable.
↑_ 2.9.4.2. No lineage editing or misrepresentation will be tolerated. 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.
↑_ 2.9.5. Downsampling of Blu-ray sources is allowed in certain cases.
↑_ 2.9.5.1. A multichannel lossless rip must have the same number of and arrangement of channels as the source media. 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.
↑_ 2.9.5.2. Downmixing of Blu-ray sources is prohibited. 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.
↑_ 2.9.5.3. All lossy Blu-ray torrents must be uploaded in a Red Book-compliant form. 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.
↑_ 2.9.5.4. 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).
↑ 2.10. Cassettes
↑_ 2.10.1. Cassettes are allowed under strict conditions. "Cassettes" include compact cassettes, 8-track tape cartridges, and non-cassette consumer reel-to-reel audio tape recordings.
↑_ 2.10.1.1. Cassette releases may not be uploaded if the release exists on the site in any other format. A non-cassette release may trump a cassette release. A bonus track which only appears on the cassette release is considered exclusive content for that release, and the full cassette release may be uploaded. A different mastering or a different track order is not sufficient to justify the upload of a cassette rip.
↑_ 2.10.1.2. Rips must be made from official (e.g., artist- or label-approved) cassette sources; secondhand copies are prohibited. Bootlegs are often secondhand copies and may be deleted outright if they do not meet high quality audio standards. Please see rule 2.10.8.
↑_ 2.10.2. All cassette rips should include clear information about lineage. Include a description of the ripping hardware if this is a personal rip or if a rip downloaded elsewhere includes this information. It is strongly recommended that uploaders include a photo of the cassette and artwork in the torrent description. Any torrents that lack lineage information are trumpable by those that have lineage information.
↑_ 2.10.3. Cassette uploads must be ripped at a sample rate of 44.1 kHz or 48 kHz and 88.2 kHz or 96 kHz. Cassette uploads with sample rates above 96 kHz may be deleted at moderator discretion. Lossy transcodes of cassette FLACs must retain the sample rate of the original FLAC if it is 44.1 kHz or 48 kHz. 44.1 kHz and 48 kHz rips may not exist concurrently; 88.2 kHz and 96 kHz may not exist concurrently; if one is already available, the other is considered a dupe unless a substantial improvement in audio quality is evident (see rule 2.10.6).
↑_ 2.10.4. Cassette rips will be trumped by an upload of the same release in any other medium. A cassette edition with bonus tracks not available in another edition is not subject to trumping.
↑_ 2.10.5. Cassette rips are subject to the duplicates and trumping rules outlined in rule 2.2.
↑_ 2.10.6. Cassette rips can be trumped if a substantially better-sounding version is uploaded. To trump an old rip with a new torrent that may be a better-sounding version, you need to report it with clear information about how your rip sounds better than the other one, with references to specific tracks and time positions to justify your report. All quality trumps/deletions of this nature are at the discretion of the moderator involved.
↑_ 2.10.7. Cassette rips of extremely poor quality (lossy or lossless) may be deleted outright if reported. All quality trumps/deletions of this nature are at the discretion of the moderator involved.
↑_ 2.10.8. Exceptions to any of the above rules may be made at a moderator's discretion. Please contact staff before uploading with detailed reasons why such an exception should be considered. Examples: a higher sample rate for a high quality reel-to-reel recording, a cassette release that was subsequently released on brickwalled CD master, a lower sample rate for a good rip of a Type I cassette, a good rip of a second generation tape with rare content. This is not an exhaustive list of possible reasons to grant an exception.
↑ 3. Comedy (Audio) & Audiobooks
↑_ 3.1. The only formats allowed for comedy and audiobooks are those listed below:
MP3, AAC, FLAC
↑_ 3.1.1. Lossless audio files are allowed at all times, in accordance with the dupe rules (see 3.9).
↑_ 3.1.2. Lossy comedy and audiobook torrents must have a minimum average bitrate of 32 kbps (for MP3 and AAC).
↑_ 3.2. No music is permitted in these two categories. They are for spoken word only. See this wiki for more information. For example, if a comedy artist performs a stand-up routine that is recorded on CD, this would be classified as a Comedy album. If this same artist sings some funny songs on an album, this would be classified as a Comedy album. If this same artist produces a music CD with no hint of comedic material (e.g., spoken word tracks), this would be classified as a music album (see 2.1).
↑_ 3.3. No radio talk shows or podcasts are allowed. Redacted is primarily a music site, and those recordings do not belong in any torrent category.
↑_ 3.4. Comedy and audiobooks must not be freely available. Free audiobooks and comedy releases from official sources may not be uploaded. Exceptions: Uploads that are at a different bitrate from those freely available are allowed. If a comedy album in 96 kbps CBR MP3 is freely available, you may still upload a V8 (VBR) or higher bitrate torrent of the freely available torrent if it does not already exist on the site.
↑_ 3.5. Releases must be unarchived and consist of a single release. Comedy and audiobook releases should not be archived in a file (e.g., .zip or .rar). The torrent must consist of a directory containing the audio files. Only one release per torrent is allowed. You may not bundle multiple audiobooks or comedy releases into one torrent. See 1.2.7 and 2.1.20.
↑_ 3.6. All comedy and audiobook releases must have an average bitrate of at least 32 kbps. However, higher bitrates are preferred over this minimum requirement.
↑_ 3.6.1. V0 (VBR), V2 (VBR), and V8 (VBR) MP3 torrents for the same album are allowed at all times.
↑_ 3.6.2. V8 (VBR) replaces V3 (VBR) through V7 (VBR) and replaces CBR rips between 32 kbps and 191 kbps. Once a rip with a V8 (VBR) encoding preset has been uploaded, you are not allowed to upload any V3 (VBR) through V7 (VBR) torrents or any CBR torrents under 192 kbps.
↑_ 3.6.3. V2 (VBR) replaces CBR rips between 192 kbps and 320 kbps. Once a rip with a V2 (VBR) encoding preset has been uploaded, you are not allowed to upload any CBR torrents.
↑_ 3.6.4. V0 (VBR) replaces V1 (VBR) and replaces CBR rips at 320 kbps and above. Once a rip with a V0 (VBR) encoding preset has been uploaded, you are not allowed to upload a V1 (VBR) torrent or any CBR torrents at 320 kbps and above.
↑_ 3.6.5. The preferred AAC bitrate is 64 kbps. All other AAC bitrates may be trumped by a 64 kbps upload. Once a 64 kbps AAC torrent has been uploaded, no further AAC uploads are allowed for that album.
↑_ 3.7. Lossy sources, including lossy transcodes, are allowed in this section only. The source may come from cassette, VHS (audio), radio, or a higher bitrate lossy file. While the sharing of transcoded material is strongly discouraged for music, the audio quality is less important for spoken word material. Note: You may not transcode a lower bitrate file to a higher bitrate file and upload it here. For example, if you find a 32 kbps CBR WMA you cannot transcode it to 64 kbps CBR MP3 and share this on the site.
↑_ 3.8. Online audiobook sources may carry only low bitrate audio files. Audiobook sources such as audible.com have standard audio quality levels that may be at or below the standards for the site (see 3.1.2). Please make sure that you know the audio quality of your source material (e.g., many audiobook retailers only supply 64 kbps files) before you transcode to V8 (VBR), V2 (VBR), or V0 (VBR). Transcoding from a lower bitrate file to a higher bitrate file is forbidden.
↑_ 3.9. Duplicate torrents of the same bitrate and format are not allowed. No uploads of the same bitrate and format are allowed to coexist on the site. See 3.6.
↑_ 3.10. Scene and non-scene versions of the same release, bitrate, and format are dupes. The Scene label does not make torrents unique from one another. If a V2 (VBR) torrent for an album on CD is already uploaded, you may not upload another V2 (VBR) scene release of the same album on CD.
↑_ 3.11. Releases must follow the usual formatting guidelines for file names and tags. Audiobooks and comedy must follow the formatting rules outlined in section 2.3. This means that file names must include track numbers, audio files must have metatags, etc.
↑_ 3.12. Do not upload multiple formats for a Comedy or audiobook album onto the same album page. Each format should have its own torrent page. Likewise, do not group existing single-torrent Comedy and audiobook releases onto a single common album page with multiple formats. Grouping torrents in these non-music categories as if they were music torrents causes a number of database and organizational problems on the site.
↑ 4. Applications
↑ 4.1. General
↑_ 4.1.1. App releases can be either a torrent of a directory or a single archive.
↑_ 4.1.1.1. Scene released applications may be archived but must not be password protected. If archives were originally password protected and had the protection removed, they cannot be represented as official scene releases and should not be labeled as scene torrents. The file hashes between protected and unprotected archives are different, resulting in a modification of the original files. Some packs and collections cannot be archived (see 4.1.9).
↑_ 4.1.1.2. Mac applications must be archived for them to function. Mac applications uploaded as .app directories will require a CHMOD operation, which is unnecessary when the application is properly archived (e.g., .dmg, .zip, etc.).
↑_ 4.1.2. All applications must come with a crack, keygen, or other method of ensuring that downloaders can install them easily. App torrents with keygens, cracks, or patches that do not work or torrents missing clear installation instructions will be deleted if reported. No exceptions.
↑_ 4.1.3. App releases must not be freely available tools. Application releases cannot be freely downloaded anywhere from any official source. Nor may you upload open source applications where the source code is available for free. Closed or shareware installers like Crossover Office are allowed. Note: If all official sources stop hosting and remove a freely available application and its source code from their site(s) due to varying reasons (e.g., legal concerns, dead development, etc.), the application ceases to be freely available. You may then upload it in that case.
↑_ 4.1.4. Release descriptions for applications must contain good information about the application. You should either have a small description of the program (either taken from its web site or from an NFO file) or a link to the information — but ideally both. Torrents missing this information will be deleted when reported.
↑_ 4.1.5. The torrent title must have a descriptive name. The torrent title should at least include the application name and release version. Optionally, you may include additional labels for operating system and method of circumvention (e.g., crack, patch, keygen, or serial). For example, "AcrylicApps Wallet v3.0.1.493 MacOSX Cracked".
↑_ 4.1.6. Use relevant tags for your torrent. Add all applicable default Gazelle tags to help downloaders find your torrent. The default tags are apps.mac for Mac applications, apps.windows for Windows applications, and apps.sound for audio applications. You may add additional tags if the default ones do not apply (such as apps.linux).
↑_ 4.1.7. Games of any kind are prohibited (see 1.2.5).
↑_ 4.1.8. Application "packs" are not allowed. That means no 0-day packs or "video utilities" compilations. Also, packaging multiple versions of the same application into a single torrent is not allowed (e.g., Adobe Acrobat 8 and Adobe Acrobat 9 in a single torrent). Exceptions: The applications are from the same company and an official release. For example, Adobe CS and Macromedia Studio packaged in one set.
↑_ 4.1.9. Sound sample packs, template collections, and font collections are allowed if they are official releases, not freely available, and unarchived. Sound sample packs, template collections, and font collections must be official compilations and they must not be uploaded as an archive. The files contained inside the torrent must not be archived so that users can see what the pack contains. That means if sound sample packs are in WAV format, they must be uploaded as WAV. If the font collection, template collection, or sound sample pack was originally released as an archive, you must unpack the files before uploading them in a torrent. None of the contents in these packs and collections may be freely available.
↑_ 4.1.10. Application components such as plug-ins, add-ons, expansions, filters, and so forth may be uploaded in a collection if they correspond to a particular application. You may upload plug-ins, expansions, add-ons, filters, and other application components as collections provided they are compatible to a particular application and version. For example, you may not upload a megapack of all filters for Adobe Photoshop CS2, CS3, and CS4. But you may upload a pack of Adobe Photoshop CS4 filters.
↑_ 4.1.11. Collections of cracks, keygens or serials are not allowed. The crack, keygen, or serial for an application must be in a torrent with its corresponding application. It cannot be uploaded separately from the application.
↑_ 4.1.12. Torrents containing hacking or cracking tools are prohibited.
↑_ 4.1.13. Never post serial numbers in torrent descriptions. Serial numbers should be in a text file contained within the torrent. If a serial number is posted in the torrent description and not included as a text file in the torrent folder, the torrent will be removed when reported. No exceptions.
↑_ 4.1.14. All applications must be complete. If an application consists of multiple CDs or DVDs, these should all be uploaded as one torrent and not as separate torrents. This also applies to scene uploads where multiple CDs or DVDs were released separately.
↑ 4.2. Duplicates & Trumping
↑_ 4.2.1. Applications having the same version number are dupes. An application may have older versions than those already uploaded. Those are not dupes. Only identical versions are duplicates. Note: Not everyone has updated to the latest operating system. In such cases, older versions of applications may still be useful for a number of users.
↑_ 4.2.2. A scene archived torrent may coexist with an unarchived torrent of the same application version. If both a scene archive and an unarchived copy are uploaded of the same application and version, both may stay on the site. Any subsequent uploads of the same torrent in either form (with identical install methods) are dupes.
↑_ 4.2.3. Different language editions of the same application and version are unique. Multi-language versions and single language versions of different languages are not considered dupes.
↑_ 4.2.4. Existing application torrents can be trumped by other torrents with better install methods. Applications with serial keys may be trumped by crack/patch versions or torrents with keygens. Once an application with either a crack/patch or keygen is uploaded to the site, no other identical application with a different installation method is allowed. Report the older torrent when you are trumping it with a torrent of the same application containing an improved method of installation.
↑_ 4.2.5. Applications that no longer work will be deleted when reported. If the install method for an application no longer works (e.g., the developer has coded a patch, the install method is no longer supported, etc.) the torrent will be removed.
↑ 5. Comic Books
↑ 5.1. General
↑_ 5.1.1. Comic books must be uploaded in the following specified formats, according to descending preference:
A rar archive (Preferably with the .cbr extension)
A zip archive (Preferably with the .cbz extension)
A PDF file
A directory containing only the images themselves
↑_ 5.1.2. Pages must be scanned cleanly and be of good quality. Scans of poor quality will be deleted, especially if the quality is so poor as to render the image difficult to read. Poorer quality scans may be acceptable for very old or rare comics with staff approval.
↑_ 5.1.3. Comic books must not be freely available. Comics must be official publications and cannot be taken for free from official sources. You may upload comics from other torrent and unofficial distribution sites, but it is your responsibility to make sure that they conform to our quality and formatting rules for comic books. Note: If all official sources stop hosting a comic and remove the official freely available release from their site(s), the release ceases to be freely available. You may only upload it at that time.
↑_ 5.1.4. 0-Day comic uploads are allowed and encouraged.
↑ 5.2. Multi-comic
↑_ 5.2.1. Multi-comic and series packs must follow site formatting requirements. Multi-comic and series packs are both accepted and encouraged but care must be taken to make a valid compilation. The rules in this section outline the requirements for multi-comic torrents.
↑_ 5.2.2. 0-Day comic packs are allowed. Make sure such uploads are synchronized with any previous packs. 0-Day comic uploads must not be missing any of their corresponding DCP or Minutemen scans for that time period.
↑_ 5.2.3. Collections may not span more than one comic title. You may not include multiple, different comic titles in a single collection, e.g., "The Amazing Spider-Man #1" and "The Incredible Hulk #1". Exceptions: Titles may contain more than one comic title if either of the following is true: it's a recognized comic crossover/event or it's a DCP weekly release.
↑_ 5.2.4. Any "multi-part" comic enveloping the whole event is allowed as a single torrent. Whole events may be uploaded together. For example, the comics "Buffy the Vampire Slayer Season Eight - 2007 - part 1.cbr" and "Buffy the Vampire Slayer Season Eight - 2007 - The Long Way Home Part 2.cbr" can be uploaded as a single torrent provided there are only 2 parts to "The Long Way Home".
↑_ 5.2.5. Torrents containing complete volumes of comics may be uploaded. For example, "The Amazing Spider-Man Vol. 1 #1-#441" can be uploaded.
↑_ 5.2.6. Torrents spanning multiple volumes are too large and must be uploaded as separate volumes.
↑_ 5.2.7. Torrents containing specific #Number-#CurrentDay issues are allowed only if the comics appear in no other pack. For example, if #1-#35 are already on the site and the current issue is #50, #1-#50 is NOT allowed to be uploaded, but #36-#50 is allowed.
↑ 5.3. Duplicates & Trumping
↑_ 5.3.1. A dupe of a single comic is defined as two scans of the same book by the same scanner, where the same pages have been scanned. The scanner may be an individual, a release group, or a scanning device. Exceptions: The following examples are NOT dupes:
Two copies of the same book by the same scanner, but one is a c2c copy and the other is a "no ads" copy
Two scans of the same book by different scanners
Two scans of the same book by the same scanner, when the copy you're uploading contains fixes
↑_ 5.3.2. Releases in .cbz and .cbr are always allowed, with preference given to the earliest upload. In the event of a dupe occurring between a .cbr and a .cbz, the earliest upload remains. In the event of any other dupe, the order listed in 5.1.1 determines which torrent is kept. For example, if a PDF is uploaded followed by a .cbr, the .cbr remains on the site and the PDF is deleted as a trump. If a .cbz is uploaded followed by a PDF, the .cbz remains on the site and the PDF is deleted as a dupe.
↑_ 5.3.3. Multi-comic collections and packs must conform to either of these collection types in order of preference.
↑_ 5.3.3.1. A torrent consisting of issues #1-50 is currently on the site. The only packs that are allowed to contain any of the comics before #50 are a #1-100 pack or a complete volume pack.
↑_ 5.3.3.2. Packs consisting of #1-#10, #11-#20, #21- #40, etc. are allowed only if the comics appear in no other pack. Each pack must contain at least 10 new comics.
↑_ 5.3.3.3. Packs consisting of #1-#100, #101-#200, etc. are allowed only if they are not a complete volume pack.
↑_ 5.3.3.4. A pack composed of #1-#EndOfVolume is allowed at any time.
↑_ 5.3.4. Complete volume or series packs will trump any torrent consisting of the same comic issues. See 5.3.1 for details on what constitutes a duplicate comic. For example, the complete volume "The Amazing Spider-Man Vol. 1 #1-#441" will trump any torrents containing those issues, e.g., "The Amazing Spider-Man #1-#50" or "The Amazing Spider-Man #150-#200" or "The Amazing Spider-Man #300-#310," etc. Exception: If the image quality of the comic issue(s) in a torrent is higher than the quality of the corresponding comic(s) in a complete volume or series pack, the higher quality version may coexist on the site with the complete collection.
↑ 5.4. Formatting
↑_ 5.4.1. All comic page scans must have zero-padded numbers and may be archived in .pdf, .rar (.cbr) or .zip (.cbz) files. The contents of the archive or directory must be image files (either JPEG or PNG), which are named sequentially so that they display in the correct order by comic reading software such as CDisplay and FFView. The page numbers and books must be zero-padded for this same reason. For example, this constitutes good numbering: file01.jpg, file02.jpg,... file30.jpg; and this constitutes bad numbering: file1.jpg, file2.jpg, file3.jpg,... file30.jpg.
↑_ 5.4.2. Comic book archive file names must be informative. The archive names should include at least the book's name (e.g., "Uncanny X-Men"), the volume (if there's more than one volume for that book), and the issue number. Including the cover year, scanner information (to differentiate between different scans of the same book), and the issue's title (e.g., "Days of Future Past") is strongly recommended. For example: Buffy the Vampire Slayer Season Eight - #01 - 2007 - The Long Way Home Part 1.cbr and Amazing Spiderman - Volume 1 - #10 - 1964.cbz.
↑_ 5.4.3. The directory name should uniquely identify its contents. You should include the title, as well as the issue numbers included (if applicable). The title, volume, cover year, and story name can often be found in small type at the bottom of the page opposite the inside cover. Directories should be named with the title of the series and the issue numbers. For example: ../Buffy the Vampire Slayer Season Eight - #01-#08/ and ../Amazing Spiderman - Volume 1 - #10-#20/.
↑ 6. ebooks, eLearning Books & Sheet Music
↑_ 6.1. Individual releases can be either a torrent of a directory, an archive, or the original format (e.g., .epub, .pdf, .chm, .txt, etc.). Neither the individual release or archive can be password protected. Note: ebooks cannot be uploaded in an archive. Users must be able to see the ebook format that is in the torrent.
↑_ 6.2. Uploading a pack of ebooks in one archive (e.g., .tar, .rar, .zip) is prohibited. ebook collections cannot be uploaded. Exception: ebooks that come in a retail set may be uploaded in a single torrent.
↑_ 6.3. ebook pages must be of good quality (in other words, legible with little or no artifacting) and must be scanned cleanly (if the pages were hand-scanned). Poor quality scans will be deleted, especially if the quality is so poor that the resulting image is difficult to read. Judgments on quality are at the discretion of the moderator involved.
↑_ 6.4. Only published ebooks are allowed. Freely available ebooks are not allowed. This rule also covers recipes and cookbooks. Only official publications are allowed.
↑_ 6.5. Collections/packs of ebooks are prohibited, even if each title is somehow related to other ebook titles in some way. All ebooks must be uploaded individually and cannot be archived (users must be able to see the ebook format in the torrent).
↑_ 6.6. Two identical ebooks or two identical sheet music uploads are dupes of one another. The same ebook and sheet music titles in the same format (e.g., .epub, .pdf, .chm, .txt, etc.) are dupes.
↑_ 6.7. Manually-scanned, scanned and OCR'ed (optical character recognized), and retail ebooks are all allowed on the site. OCR'ed ebooks may trump manually-scanned versions, while untouched retail ebooks will trump both hand-scanned and OCR'ed versions.
↑_ 6.8. Include proper Gazelle tags for your ebook and sheet music uploads. You are strongly encouraged to use the appropriate default tags with your uploads. That way other users can find your uploads easily through the tag search system. Sheet music should use the sheet.music tag. ebooks should at least contain the fiction tag or the non.fiction tag depending on the content. You may add additional tags if the defaults do not apply or are not enough to describe the torrent contents.
↑ 7. eLearning Videos
↑_ 7.1. The eLearning Videos category is only for tutorial videos on specific topics pertaining to music (see 7.3 in this section). Any video clips mentioned in Section 1.2 cannot be uploaded to the eLearning Videos category.
↑_ 7.2. No freely available eLearning videos are allowed. You may not upload videos that are officially hosted from university sites, the author's site, the Internet Archive, or the publisher's site. You may upload videos from other torrent sites as long as they conform to the rules in this section.
↑_ 7.3. Tutorials on how to use musical instruments, vocal training, producing music, or otherwise learning the theory and practice of music are the only allowed topics. No material outside of these topics is allowed. For example, instruction videos about Kung Fu training, dance lessons, beer brewing, or photography are not permitted here. What is considered allowable under these topics is ultimately at the discretion of the staff.
↑_ 7.4. eLearning Videos must be either in a video file format (.mkv, .avi, .mov, .mp4, etc.) or a disk image (.iso, .bin/.cue, etc.). Only one video file format and one disk image format are allowed per video. The same video in another file format or within another disk image type is a dupe. Torrents should not be uploaded in compressed archives. Such torrents will be removed when reported.
↑_ 7.5. eLearning video uploads must contain an informative description and use proper Gazelle tags. Uploads should include a proper description and/or a link to further information. Using the elearning.videos Gazelle tags is strongly encouraged.






Forum Rules
Many forums (Sandbox, Suggestions, Serious Discussion, etc.) have their own set of rules. Make sure you read and take note of these rules before you attempt to post in one of these forums.
Don't use all capital letters, excessive !!! (exclamation marks) or ??? (question marks). It seems like you're shouting!
No lame referral schemes. This includes freeipods.com, freepsps.com, or any other similar scheme in which the poster gets personal gain from users clicking a link.
No asking for money for any reason whatsoever. We don't know or care about your friend who lost everything, or dying relative who wants to enjoy their last few moments alive by being given lots of money.
Do not inappropriately advertise your uploads. In special cases, it is acceptable to mention new uploads in an approved thread, but be sure to carefully read the thread's rules before posting. It is also acceptable to discuss releases you have uploaded when conversing about the music itself. Blatant attempts to advertise your uploads outside of the appropriate forums or threads may result in a warning or the loss of forum privileges.
No posting music requests in forums. There's a request link at the top of the page; please use that instead.
No flaming; be pleasant and polite. Don't use offensive language, and don't be confrontational for the sake of confrontation.
Don't point out or attack other members' share ratios. A higher ratio does not make you better than someone else.
Try not to ask stupid questions. A stupid question is one that you could have found the answer to yourself with a little research, or one that you're asking in the wrong place. If you do the basic research suggested (i.e., read the rules/wiki) or search the forums and don't find the answer to your question, then go ahead and ask. Staff and First Line Support (FLS) are not here to hand-feed you the answers you could have found on your own with a little bit of effort.
Be sure you read all the sticky threads in a forum before you post.
Use descriptive and specific subject lines. This helps others decide whether your particular words of wisdom relate to a topic they care about.
Try not to post comments that don't add anything to the discussion. When you're just cruising through a thread in a leisurely manner, it's not too annoying to read through a lot of "hear, hear"'s and "I agree"'s. But if you're actually trying to find information, it's a pain in the neck. So save those one-word responses for threads that have degenerated to the point where none but true aficionados are following them any more.
Or short: NO spamming
Refrain from quoting excessively. When quoting someone, use only the portion of the quote that is absolutely necessary. This includes quoting pictures!
No posting of requests for serials or cracks. No links to warez or crack sites in the forums.
No political or religious discussions. These types of discussions lead to arguments and flaming users, something that will not be tolerated. The only exception to this rule is the Serious Discussion forum, which exists solely for the purpose of intellectual discussion and civilized debate.
Don't waste other people's bandwidth by posting images of a large file size.
Be patient with newcomers. Once you have become an expert, it is easy to forget that you started out as a newbie too.
No requesting invites to any sites anywhere on the site or IRC. Invites may be offered in the invite forum, and nowhere else.
No language other than English is permitted in the forums. If we can't understand it, we can't moderate it.
Be cautious when posting mature content on the forums. All mature imagery must abide by the rules found here. Gratuitously sexual or violent content which falls outside of the allowable categories will result in a warning or worse.
Mature content in posts must be properly tagged. The correct format is as follows: [mature=description] ...content... [/mature], where "description" is a mandatory description of the post contents. Misleading or inadequate descriptions will be penalized.
Threads created for the exclusive purpose of posting mature imagery will be trashed. Mature content (including graphic album art) should be contextually relevant to the thread and/or forum you're posting in. Mature content is only allowed in: The Lounge, Serious Discussion, General Music, Power Users, Elite, Torrent Masters, VIPs, and the Sandbox. If you are in doubt about a post's appropriateness, send a Staff PM to the Forum Moderators and wait for a reply before proceeding.
IRC Rules
Staff have the final decision. If a staff member says stop and you continue, expect at least to be banned from the IRC network.
Be respectful to IRC Operators and Administrators. These people are site staff who volunteer their time for little compensation. They are there for the benefit of all and to aid in conflict resolution; do not waste their time.
Do not link shock sites or anything NSFW (not safe for work) without a warning. If in doubt, ask a staff member in #red-help about it.
Excessive swearing will get you kicked; keep swearing to a minimum.
Do not leave Caps Lock enabled all the time. It gets annoying, and you will likely get yourself kicked.
No arguing. You can't win an argument over the Internet, so you are just wasting your time trying.
No prejudice, especially related to race, religion, politics, ethnic background, etc. It is highly suggested to avoid this entirely.
Flooding is irritating and will warrant you a kick. This includes, but is not limited to, automatic "now playing" scripts, pasting large amounts of text, and multiple consecutive lines with no relevance to the conversation at hand.
Impersonation of other members — particularly staff members — will not go unpunished. If you are uncertain of a user's identity, check their vhost.
Spamming is strictly forbidden. This includes, but is not limited to, personal sites, online auctions, and torrent uploads.
Obsessive annoyance — both to other users and staff — will not be tolerated.
Do not PM, DCC, or Query anyone you don't know or have never talked to without asking first; this applies specifically to staff.
No language other than English is permitted in the official IRC channels. If we cannot understand it, we cannot moderate it.
The offering, selling, trading, and giving away of invites to this or any other site on our IRC network is strictly forbidden.
Read the channel topic before asking questions.














Tagging is an important part of uploading at Redacted. We are a community that values good organisation and cataloguing highly, and good tagging practice is an essential part of this. This guidance will help you to understand which tags you should and should not add, and how to help us create a beautifully arranged archive.

Redacted
These general guidelines are the basics of tagging on Redacted. All users should adhere to them and be familiar with the practices described.

• All tags should be comma-separated on the upload form.

• You should use a period (".") to separate any words inside a tag. For example, "hip.hop" or "post.rock".

• Abbreviations should be avoided. It's "alternative.rock" or "progressive.rock", not "alt.rock" or "prog".

• The most common tags can be selected from the dropdown on the upload page. We recommend adding more specific sub-genres manually, but it is fine to use only these official tags if you do not feel qualified to be more specific.

• Tags can be upvoted or downvoted on any release page. Users with editing privileges can also outright delete these tags if it is appropriate to do so. (In cases of misspelling or blatant miscategorisation, for example.) Do not abuse this privilege, or you may lose it.

• Deliberately adding junk tags is against the rules, and doing this persistently may get you warned. This includes meme tags, which are not acceptable.

Disallowed Tags

The following types of tag should not be added at any time. This is because the information is either redundant, misleading, or unhelpful.

• Anything you would specify elsewhere on the upload form. Artists, formats, release types and bitrates should never be added as tags, as this is redundant. Tags such as "vinyl", "flac" and "soundtrack" would count as this.

• Personal opinions, slurs and useless information. This includes tags such as "seen.live", "awesome" and "rubbish".

• The year of the release. To tag the year, use the decade instead, so "2010s", not "2016". Please note that "2000s" refers to the years 2000-2009. Always use the year of the original release here, so for a 1979 album remastered in 2000, use "1970s".

• Information on live recordings. The "Live Album" and "Concert Recording" categories make tags such as "live" and "soundboard" redundant.

• The tag "hardcore". This is too vague as it could refer to two distinct and unrelated genres. Use "hardcore.punk" or "hardcore.dance" instead.

• The tag "garage". Again, this tag is vague as it refers to two distinct and unrelated genres. Use "garage.house" or "garage.rock" instead.

• Anything better suited to a collage.

Official vs. Unofficial Tags

Redacted has many official tags that you may use. However, we always encourage users to add niche genres as a tag as is appropriate. A genre such as "bhangra" or "nerd.punk" may not be prominent enough for listing on the search form by default, but adding it to an upload greatly assists other users in finding such material.

If you feel that a tag should be added to our official list, please post in our forum thread here. We regularly monitor this thread and uploads for new trends and genres and update our list as appropriate.

Any questions?

If you're unsure about any of the above information, please don't hesitate to ask us! You may direct any questions to First Line Support. You can also gain assistance through IRC in the #RED-editing channel. Happy tagging!