Luke Posted September 21, 2007 Share Posted September 21, 2007 Achei que devia de partilhar esta informação, pois ao longo dos anos tenho visto/lido que há muitos de vós que não sabem o que é um 0day, Propper, ou até um Cam São estas as regras que definem as realeses ************ RULES SUMMARY ********** SVCD DVD rips - Length: no more than 55 minutes per CD. - Max. video bitrate 2450kbps. - Min. average video bitrate 1700kbps for widescreen releases or 1900kbps for full screen releases. - Use VBR 2-pass or higher. - Min. audio bitrate 192kbps, maximum 224kbps. DivX DVD rips - Length: PAL (25 fps) 105 minutes/CD FILM (23.976 fps) 110 minutes/CD NTSC (29.97 fps) 92 minutes/CD - Audio VBR MP3 or AC3 - Codec DivX 3.11 or XviD - Use 2-pass encoding - Resolution: width 512 - 640 pixels and must be a multiple of 16 height must be a multiple of 16 black bars must be cropped DVDR DVD rips - must be at least 4.15 Gb unless source is dvd5 - CCE must be used for all re-encoded streams - Min. bitrate 3000 kbps - 100 minutes or below min. 4 pass, over 100 minutes min. 5 pass - Keep menus, English audio (original audio if non-English) and subtitles in three of the most common languages - Macrovision must be removed - Must be region free ********** XVID ********** The federation of releasing groups presents The DivX Releasing Standards 2002 Requirements: Notepad with terminal font or other ascii viewer [ INTRO ] In an unparalleled event of co-operation and innovation, the DivX scene united once again to bring you the 2002 installment of the TDX guideli- nes. We thank all of you who so kindly gave up time and energy to bring us suggestions and help us brainstorm on the newest of video technolo- gies. So without further ado, we present to you, the DivX ripper/enthu- siast, the TDX 2002 Releasing Standards. [ RELEASE RULES ] Movie Length: - PAL (25 fps) = min runtime is 105 minutes/CD - FILM (23.976 fps) = min runtime is 110 minutes/CD - NTSC (29.97 fps) = min runtime is 92 minutes/CD TV-Series Episodes shall NOT be exempt from these rules (See Series Notes). These runtimes are scalable via the following equation: N cd time minimum = (N-1) * allowed_time where N is number of CDs and allowable time applies to your format (i.e. 4 cd FILM rip min = 110 x (4-1) = 330 minutes) Media usage is at Ripper's discretion, please use it. Releases should utilize at minimum 97% of total media capacity, however an undersized release is not a technical flaw. AUDIO: - MUST be MP3 or Studio AC3 (AC3 transcoding forbidden). - MUST be STEREO for STEREO sources, MONO for MONO sources (MONO audio as STEREO on source is considered a MONO source). - MUST BE VBR! NO CBR MP3! - VBR techniques: - strongly recommended to use --r3mix with LAME - ABR is considered a VBR technique. - AC3 MUST be used wisely and correctly. - AC3 MUST be interleaved at 64 or 96 ms. VIDEO: Keyframe: - MUST be <=20 seconds and MUST be inserted according to scene changes and framesizes as determined by the codec or encoding application. Framerate: - MUST be as close to original source framerate as possible. Codec: - MUST be DivX 3.11 or XviD. - MUST use 2 pass technique during encoding! - NO DUPES BASED ON CODEC TYPE, USE INTERNAL. Resolution: - Width: 512 - 640 pixels and MUST be a multiple of 16. EXCEPTION: 4:3 FS sources may use a minimum resolution of 448 pixels. - Height: Must be a multiple of 16. - Cropping is required. Subs, Interactive Menus, Trailers: - OPTIONAL (if and ONLY if all other requirements have been met). - VOBSUB is the preferred format due to the fact it does not use OCR, however, any format that displays with DVobSub is acceptable. - Subtitles may be MUXED with video stream, but may NOT be BURNED into video stream. - Subtitles not muxed into video stream MUST be encapsulated in .rar file with the MOST compression available and shall be contained in the directory named 'Subs' and will NOT be packaged with main movie .rars. - Subbed is preferred over dubbed. - Burned subtitles shall only be permissible when the source exhibits forementioned subtitles in the picture itself (i.e. Subs in the matte portion of the picture MUST be typed in a seperate file and the frame shall be cropped). - Subs on non english movies MUST fit on CD with main movie, all other optional subs SHOULD fit on CD. Series Notes: - Episodes shall not overlap on CDs (i.e. 2eps/CD, 4eps/CD is allowed 1.5eps/CD is NOT). - Episodes are not subject to the same scaling rules as cinematic features and must obey forementioned rule. - Suggested media usage: 4x23min = 1CD, 2x45min = 1CD, 1x60min = 1CD Packaging: - All releases must be AVI, not BIN/CUE. (see Notes Section) - Must be packed with RAR, compression is NOT ALLOWED and broken into 15 or 20 MB volumes - Recovery record recommended. - Must have SFV - Must have NFO - NFO MUST INCLUDE: Group name Title Actual DivX release date DVD release date US theater release date Video size Framesize/aspect ratio Audio bitrate Video bitrate Movie runtime/length IMDB/adultdvdempire link Number of rars per cd (eg. 44x15MB) Ripping Method Credits: - Movie credits are preferred but CAN be cut in order to fit within 1 CD (700 MB) if the movie length would exceed 110 minutes. - NOT required in the AVI itself. - NOT required in the NFO - it is 'recommended' to list the main few characters as IMDB lists them. Samples: - REQUIRED - 1 full minute in length (approximately 10 MB) and in separate folder marked 'SAMPLE'. - MUST be taken from the movie - NOT encoded separately. Propers: - Propers are ONLY permitted in the case of a technical flaw with the original release (i.e. Bad IVTC, Interlacing, etc). - Releases not nuked on release lists and/or sites MUST include original sample of technical flaw. - Qualitative propers are not allowed, nor are propers based on decisions made by a ripper (i.e. # of CDs, AC3 or MP3, etc). - Propers based upon the compliance with new instances of TDX guidelines are also forbidden (i.e. older rips with 720px res). - Subbed (in original movie language) propers dubbed (in any language). Directory Naming: - Directory names shall NOT exceed 64 characters. - All releases are to include production year. - DO NOT indicate Ripping method (MM4/VM2/VBR/SBC and so on), WS (widescreen), DVD/DivX release DATE, GENRE or anything else in the directory name (ONLY within the NFO). - Acceptable characters in naming a directory include (NO spaces or double dots - single dots or underscores ONLY): ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789 . -_ - All Release directories, regardless of year, shall be named according to Movie.Name.Year.Source.Codec-Group, suggested naming for the movie itself shall follow the same procedure (i.e. Movie.Name.Year.Source.Codec-Group.avi, Movie.Name.CD1.Year.Source.Codec-Group.avi). - Releases that are more than 1 CD will follow these specs: - MUST be named CD1, CD2, CD3 and so on. ('disc1', etc will NOT be allowed). - There MUST be a SFV included for each CD. - Rars MUST be broken into 2 or more CD volumes. (78 rars of a 2 disc title will NOT be tolerated) [ NOTES TO THE RULES ] Source related notes: - Source shall be DVD Only, no exceptions! - DVD Screeners shall be clearly marked in the directory name and the nfo shall contain presence of studio watermarking, or lack thereof. Ripping related notes: - Maximum VIDEO bitrates are covered by length rules. - Movies should be ripped in their most widescreen format available. - Multi-language audio tracks are allowed. - Multiple languages should be interleaved into the AVI, with a graphedit filter for each appropriate audio stream. - Movies that would ordinarily fit on one CD should not be made into 2 CD releases on the basis of additional audio tracks. - Multi-language audio CANNOT be used as a basis for a dupe. - Multi-language subtitles CANNOT be used as a basis for a dupe. - AVI and not BIN/CUE: - Some people burn to archive and play on a computer at a later time, BUT since there is no outside purpose other than playing on the computer, there is NO need to be packaged as BIN/CUE. - Group Watermarks WILL NOT BE ALLOWED IN ANY CASE. - NO intros, outros, betweenos, or any other form of defacement of the movie will be tolerated. - Movie container MUST be AVI. OGG, OGM, MCF, Project Theora, MP4 are all forbidden due to bugs and usability factors, maybe next year! [ GROUPS & MEMBERS ] TDX 2002 revision was organized by: - E.L. - V. - f3k - Respects to the original TDX, Team DivX, organizers: - krazy8 - RipKord - Wuman - Lava - MaTaN - TDX 2002 has been approved by the following DivX groups: - AEN - DOMiNiON - DVD-R - EPiSODE - EPiC - INCiTE - MDX - - QiX - SChiZO - VCDVaULT - Also signed by: - SATELLiTE - InFuX - aNBc - DEiTY - MEDiAMANiACS - DVL - - CPY - JDX - DDX - REQUiSiTE - SEVcD - FoCUS - - DiSTORTiON - COLLiSiON - ******* STANDARD RIP RULES ******* Standard Rip Rules (S.R.R). In 1998, and again on March 26th 2000, three rip game groups collaborated to bring about rules with the hope of ensuring quality in a constantly evolving rip scene. These rules lasted a long time, but as technology moves forward, so to must the rules governing it. It is time once again for the standards by which the games scene operates to be updated. As we are all aware there have been major developments in the scene. These new rules may seem to be quite radical as a result. Those fearful of change may very well be opposed to them - but let us not forget that had there never been any change, we would not have any of the existing rules in the first place! In lieu of past events, the deciding figures of: Myth, Divine, Vace, and Instinct have converged and agreed upon a new set of rules based on those that came before. These new rules have been updated, modified, and agreed upon by a consensus, and should provide a new standard better suited to the scene in this day and age. These groups have been active participants in shaping the scene in the last six months, and were given active participation in voicing their point of view. These new rules will allow for a fair and competitive scene while ensuring a quality-minded environment for all, bringing game rips forward into a new era and restoring their relevance. It should be noted that CLASS and BACKLASH chose not to attend due to their reduced role within the scene. However former NSA groups (such as CLASS and BACKLASH), who have chosen not to sign up for these new rules, will still be required to abide by the former NSA rules, which they signed. In the past, groups setting the rules have been called the SPA, The Faction, or as in the most recent case the NSA (Network Software Association). Some have claimed the exclusive nature of these organizations have locked them out of the process. Hence from this time forth there shall be no organization dictating to the others. All groups are invited to adopt these rules, and every effort has been made to contact the various players in the games rip scene. These rules shall be identified simply as the Standard Rip Rules (S.R.R). They have been ratified and approved among the four groups and will be recognized and followed immediately on this date and thereafter: March 5th, 2004. The Standard Rip Rules are as follows: 1. Files: The disk limit is as of now 55 x 5,000,000 bytes. This equates to a total of 275,000,000 bytes of compressed data. Groups may not exceed the total size (including when crack.ace or similar files are are needed in the first disk of a release) to prevent any future cheating. Groups caught cheating on file size WILL be nuked! The limit for standard game add-ons is 25 x 5,000,000 bytes for any add-on that includes Music, Speech, Commentary or Play By Play for the original release. Any add-on that does not fit these criteria will be restricted to 15 x 5,000,000 bytes. Only the group that won the game release is allowed to release the add-ons for that game. Due to an increasingly limited number of file names, and the ability of all modern operating systems to handle long file names, it is now permissible to use file names up to a maximum of 12.3 characters (filename/extension). Acceptable compression formats at this time are ACE or RAR or any future compression that supports multiple volumes and long file names, followed by the traditional PKZIPing. The traditional packaging methods (ZIP/DIZ) shall be maintained, with a DIZ file being present in each zip. 2. Proper Rips: To prevent sloppy rips, a re-release of a game is allowed to ensure groups release proper and respectable rips. The following provisions include: it can be ripped in >=7 disks less than the previous release or less than half the size of the previous release by using only lossless compression methods. That means all the essential game data must be still included in the re-release. No essential data is allowed to be removed to be considered a valid re-release. A re- release from a competing group may not use tools, original crack or any other files from the previous release that were modified for the original game rip. A group may NOT use DDS conversion on a proper rip unless used on the original rip. Lossy audio conversion is allowed in proper rips; downsampling is not. The re-release of a rip can be done by any group and must be done within 48 hours of the original rip, as possibly every game is rippable in a smaller size if enough time is spent. 3. Functionality: Every release under this limit MUST be a functional and playable complete game with no essential data missing to finish the game. This means that included will be every component necessary for the successful completion of the game e.g.: - all game executables that are needed, - every level (single AND multiplayer), - every track (including practice), - all actor graphics & models etc, - sound effects - registry settings to play on the Internet (Zone/etc.) - if the serial of the game is checked online thus making it impossible to play online with any possible rip, it is allowed to rip out multiplayer, LAN play should still be fully included if it exists 4. Packers: Any lossless compression method to reduce the size of selected game data is ALLOWED (e.g. uharc). 5. Lossy Compression: Lossy compression is ALLOWED for sound, videos and non- texture graphics (menu screens and loading screens) but lossless compression is encouraged before using lossy compression. Lossy compression of textures is allowed only using DDS. If a game includes separate texture sets for hires AND lowres systems you are allowed to rip lowres only but the game still has to work on all hardware platforms. 6. Sound: Sound effects WILL and MUST be included. To reduce the size of rips when possible, standard wave format files (PCM) should be compressed. If the sound files exist inside a big file it's highly regarded when time is invested to extract those files to compress them. Groups are not required to index big files though. A downgrade of sound quality to sound files to allow the game to fit the limit will NEVER be permitted. Acceptable sound compression formats are: <22/1 <22/2 22-32/1 22-32/2 44-48/1 44-48+/2 (khz/channels) mp3 32 32 48 56 56 112 (kbit) ogg 32 32 48 48 56 64 (kbit) wma8 20 20 20 32 32 80 (kbit) wma9 16 16 16 20 20 64 (kbit) It is allowed to rip music, commentary/speech and ambience files as long as the game remains playable. speech files MUST be included if there exist no on-screen subtitles. Speech can be downsampled, but only to the above SOUNDS quality or to WAV 22.050 quality. No lower. It is okay to remove commentary from a release if size does not permit it. It is highly regarded when all sounds, speech and music are included in a rip and not intentionally put out as add-ons. 7. Movies: Movies (intros, cut scenes) should be removed if they are not game related. Movies must be ripped in a way so that the game play experience is not compromised, e.g. framing of movies is highly regarded. It should always be avoided to create situations in which user-input is necessary on black screens because the video normally shown has been blacked out. Downsampling of Movies is allowed under the following guidelines: Divx 3-5 / Xvid / Original codec (used in game): - Kbit rate: 650 kbit+ - Quality: 93%+ - Quantizer: 4.0 (no more) RadVideo (BIK): - Compress to 50%+ of the original file size. Windows Media Video (WMV) / MPEG2: - Allowed resolution change, but no less than 50% of original resolution (width/height divided by 2). - Allowed recompression to same resolution but with lower kbit rate. *NOTE* Movie conversion on enduser machine is FORBIDDEN. 8. Add-ons: Other allowed add-ons for games include: - cut scenes/movies - commentary/speech - music - editor No more than 2 add-ons should be released for a game release. Intro and Outro add-ons are EXPLICITLY FORBIDDEN. Only the group that released the initial game release can release the above add-ons, unless there is a problem with the release. This is to prevent third party groups that may not understand how to release these properly to correctly support the initial release, and to prevent multiple add-on dupes from appearing. This will be ENFORCED on group SITES! 9. Kiddie: Children's games (aka Kiddie games) and Edutainment software do not qualify under these rules guidelines for acceptable releases. Kiddie games are usually defined via the game target audience of '5-12 years' as stated by the game's producer. Common sense should be applied by all groups to identify what really is a kiddie game. Platform games are not to be considered kiddie games unless explicitly stated by the developer/publisher. 10. Official: Level packs, game add-ons etc. for rips are only allowed if they are officially released/authorized by the same company, developer or publisher that put out the original game. If possible by its size, the add-on should be made as a standalone and not needing the original game release. The original missions may be removed to allow the game add-on to become standalone if not size can not permit the original game. It should be explained in the NFO if and why a game add-on isn't made to be standalone. 11. Dupes: In regard to games distributed in the United States that are LATER distributed in Europe or vice versa under the same or different name/publisher. These games if released AFTER another group's release are counted as DUPES unless it can be proven that there is a clearly noticeable PLAYABLE difference in the latter release (more than just tiny differences in graphics or sound). Differences in file dates and Game Titles between Euro and US releases are NOT a good enough reason to re-release the game. 12. Information: A brief outline of what has been stripped and any explicit lossy compression used should be clearly stated in the game-release in the .NFO or CRACKTRO file. This file should be placed within the first file of a release so everyone knows where to find it. 13. Enhancements: Trainer releases & Update patches: Fully cracked Update Patches and Trainers are highly regarded, though they are not the responsibility of any group (including the group which released the original game title). If 2 trainers from the same or different groups are released for 1 game, this does NOT qualify as a dupe unless the latter trainer provides no new features over the prior trainer. Patches that are the same do qualify as a dupe. Also beta patches fall under the area of betas and should also be nuked accordingly. Even the companies that make beta patches do not support them so, why should the scene? All trainers must work the same on all formats that the game supports. If the game supports W9x/WME/NT4/WXP/W2K3 /WOW64, then the trainer's options must work on all those formats too. No TMK/Magic or trainer making utility releases will be allowed in making trainers. These will be banned as they lack the quality that a real trainer employs and can be unreliable on games that check for these in later levels or situations. Beta update patches will not considered a valid release among any game group. No group shall release a cracked patch for a game if a generic patch exists for a particular game in the scene. If a generic crack exists, a new patch-release must specify that the generic crack does not work anymore. 14. Competition: If two or more rips of the same game get released, the first complete working rip wins. Sites should not nuke any release until the winning rip has been proven to work correctly and follows the above rule set. 15. Stealing: No group shall use another's groups work - be it an iSO crack or tools written by another competing group. Any third party tools are acceptable. A crack from an iSO or past release (even in other languages or iSO's) shall not be used unless permission is given from the cracker or creator of the original release group. This permission can only be given by crackers and not leaders or seniors. Thus making sure crackers control their own cracks and are not dragged into group politics. It should be noted that most iSO cracks are actually cracked by rip group crackers. Thus without permission from the rip group, said crack cannot be used by other groups. Even if no rip currently exists, as that would be stealing. An example of this is groups like TECHNIC who steal cracks all the time and should be banned and nuked on all sites for reasons of quality. If however a group or member makes their said tools/source public, then they loose their right to prevent others using their tools as they have made it public domain. This should act as a deterrent to crackers who wish to brag to everyone as protection companies gain an insight into the scene when people make standard scene tools public. This then in turn hurts the scene when protections get updated. 16. Flaming: While baiting and harping within a groups release has always been a part of the scene, at times groups have taken this too far. This causes all groups to look lame and childish within the eyes of end users; worse still it can lead to security breeches. In order to avoid this being taken too far in the future, direct naming/nicks of individuals (not groups) within NFO files and other materials is STRICTLY PROHIBITED. 17. Ancients: No game can be ripped where the latest file date of a file on the original media (CD/DVD) is older than 6 months prior to the releases of the rip. This is to avoid the emergence of new technologies being employed to resurrect past un-rip able games & create a mess of hundreds of ancient games being released. And to promote faster rips at the time of game release. No rips that were deemed unrippable before the date of March 5th, 2004 shall be released because the new rules deem them rippable! 18. Rules: These rules should be placed in the first zip file of every rip release. It is hoped that this will prevent groups down the line from feigning ignorance of the rip rules. This should also allow these rules to travel far and wide in the hope that all sites/groups will adopt these standards for game rip releases, thus ensuring the quality we have come to expect within the scene. 19. Sites: It is highly regarded for all groups to establish a /GAMERIPS directory on their affiliated FTP sites which will contain game-iso rips and (optionally) DVD rips. Trainers and patches belong to 0day. 20. DVD Amendment Rules: With the advent of games on DVD media, albeit in minor quantities, it has been decided to pre-empt any more rule changes in the future by including the following DVD rules. These rules will be based mostly on the existing rip rules and will allow people to get used to this new and developing scene. a. Installation: The DVD rip release should install from the CD and only run the game from the hard drive. HD running of a game is the goal, not running off CD. This is the usual way with rips. b. Size: The game size for DVD RIPS should be made into a burnable CD iSO format for easy burning and distribution. The .bin and .cue format where possible. The release must not have more than 3CD's of 80mins. Regardless of how many DVD's there were. This should only be the case where the normal rip sizes cannot apply and the original media format was indeed DVD. It should not be used as an excuse to rip down 6 CD releases, as these have been proven to be rippable even under the old rules in the past. c. Format: Release files should be in RAR format or any future compression that supports multiple volumes and long file names, followed by the traditional SFVing. And in also rip sites/places should therefore adjust their scripts to handle the new DVD rip formats as well as the usual ZIP files. Siteops UPDATE your SCRIPTS! d. Valid: A rip release of 55 x 5,000,000 bytes and the release of a DVD rip of the same game, are allowed as they will accommodate to different users. e. Singular: No add-ons are allowed for DVD rips as the current size should be enough. For patches and trainers the current normal rip rules should apply. f. CD/DVD availability: No DVD rip of a game is allowed if a certain publisher releases a game on CD and DVD unless the DVD game increases some game features (like highres movies, etc.). g. General: In general the standard rules should be applied also to DVD rips. If a group removes any allowed data and a competing group can leave the data in and make it the same CD count, their release is considered a proper and is the valid release. It is preferred to include as much data as possible on DVD rips. Only if it is not possible to fit all data on 3 CDs by downsampling and other means of compression it is legit to remove data from the game. This means a 3 CD release with movies included is preferred over a 2 CD release with movies ripped out. Reasons for proper are: A) If a group can rip a game to the same CD count as the previous groups rip by including gamedata ripped out by the previous group. Downsampling IS ALLOWED. The size of the cds do not matter in this case. If a group can get 350mb smaller in size as long as all previous data in rip is included and NO downsampling occurs. C) If a group can get 1 CD smaller in size as long as all previous data in rip is included. Downsampling IS ALLOWED. To cease any confusion examples are provided: Scenario A) If group A releases a 2 CD DVDRip with movies and some audio ripped, and group B releases their rip which is also 2 CD's with all movies/music included but downsampled, group B's is the valid release. Regardless if group B's release has bigger sized cds. Scenario Group A releases a 2 CD DVDRip with everything included, both CD's being 700mb. Group B releases a 2 CD rip with everything included but because of better technique CD1 is 700mb and CD2 is 350mb, hence half a CD smaller as long as movies are NOT downsampled it is the valid release. Scenario C) Group A releases a 3 CD DVDRip, 2 CD's being 700mb, CD 3 being 200mb. Group B releases a 2 CD rip with everything included from previous rip, because of better technique or downsampling it is the valid release. This is true regardless of the size of the last CD, be it 700mb or 10mb. S.S.R. March 5th, 2004 Signed and ratified by Leaders & Council Members of the following groups: Myth, Divine, Vace, Instinct, Dynasty, Oceanine, Cubic, Delice, Bowling, NLrip and Storm. Link to comment Share on other sites More sharing options...
tumkes Posted September 21, 2007 Share Posted September 21, 2007 boringgggggggggggggggggggggg Link to comment Share on other sites More sharing options...
iNSPiRE Posted September 21, 2007 Share Posted September 21, 2007 ahh, a velha Bíblia há uns tempos que não me deparava com isto Link to comment Share on other sites More sharing options...
Luke Posted September 21, 2007 Author Share Posted September 21, 2007 Continuando .... ************ DVDR SUMMARY ************ These are the official release scene rules for dvdr releases. Release size must be at least 4.15 Gb unless source is dvd5 PAL after NTSC and NTSC after PAL is allowed CCE must be used for all re-encoded streams REmpeg is not allowed Minimum bitrate must be 3000 kbit (2800 kbit for tv shows) If minimum bitrate can not be achieved the explanation must be specified below or equal 100 Minutes 4 or more passes Movies over 100 Minutes 5 or more passes If audio is stripped from a dvd9 disk, higher bitrates must be kept over lower bitrates (if a disk has 5.1 and 6.1 audio, 5.1 would be stripped in favor to 6.1) For non-English Movies, original audio track must be kept English Audio track must be kept if present Other audio tracks are at ripper’s discretion If English subtitles are present, they will be kept under ALL circumstances If the disk contains three or less subtitles all will be kept unless the video bitrate is compromised If the disk contains more than three subtitles, rippers will decide which will be kept. Its advised to keep most common used language subtitles Menus MUST be included, unless the average bitrate is compromised Menus on TV Show disk must be kept at all costs. Extras are an added value but not needed. DVD Limitations: Macro vision must be removed All user limitations and restrictions must be removed Releases must be made region free ******* DVDR 2002 ******* THE 2002 DVDR RELEASING STANDARDS VERSION 2.0.3 General: . Release size must be at least 4.15 Gb unless source is dvd5 . PAL after NTSC and NTSC after PAL is allowed Video: . Re-encoding: . CCE must be used for all re-encoded streams . REmpeg is not allowed . Minimum bitrate must be 3000 kbit (2800 kbit for tv shows). If minimum bitrate can not be achieved the explanation must be specified in the nfo. . Passes: . Movies below or equal 100 Minutes: 4 or more passes . Movies over 100 Minutes: 5 or more passes Audio: . If audio is stripped from a dvd9 disk, higher bitrates must be kept over lower bitrates (if a disk has 5.1 and 6.1 audio, 5.1 would be stripped in favor to 6.1) . For non-English Movies, original audio track must be kept. . English Audio track must be kept if present. . Other audio tracks are at ripper’s discretion Subtitles: . If English subtitles are present, they will be kept under ALL circumstances. . If the disk contains three or less subtitles, all will be kept unless the video bitrate is compromised. . If the disk contains more than three subtitles, rippers will decide which will be kept. Its advised to keep most common used language subtitles. Menus: . Menus MUST be included, unless the average bitrate is compromised . Menus on TV Show disk must be kept at all costs. Extras: . Extras are an added value but not needed. DVD Limitations: . Macro vision must be removed . All user limitations and restrictions must be removed . Releases must be made region free Packaging: . All releases must use .img for imaging, .iso, .nrg not allowed . Releases must be broken up into rars of 50,000,000 bytes. . Recovery records must be used. . SFVs and NFOs MUST be included. NFO Must include the following: . Groups name . Title . US theatrical release date . Regions, NTSC or PAL . Bitrate used when re-encoding . Audio streams, and subtitles included . What has been stripped, extras, menu, etc. . IMDB, or similar link . Number of rar files. Samples: . Samples are required. Minimum size shall be 30mb. . Samples must be put in a separate sub directory, labeled 'Sample' . Vobs may be cut and used as sample, or renamed to mpg . Samples must be from actual packed vob. Separate encodes are not allowed. Directory Naming: . Directory names shall NOT exceed 64 characters . ALL releases are to include production year . Directory name must include Disktype (NTSC/PAL) . Acceptable characters are as follows: ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789 . -_ . DVD-5, and DVD-9 COMPLETE will be named as follows: Movie.Title.Year.COMPLETE.Disktype.DVDR-Groupname . Non-Complete DVD-9 releases must be named as follows: Movie.Title.Year.Disktype.DVDR-Groupname . Sub directories must be labeled DISK1, DISK2, DISK3, etc CD1, DVD1, will NOT be tolerated Propers: . Propers will ONLY be released if previous had technical flaws such as menu errors, bad quality, etc. . Propers based on previous releases having improper dir names will not be tolerated. . If previous release was not region free, a patch must be used, NOT a proper. . No Propers on releases before 2002 DRS. Other Notes: . Source will be from DVD Only. No re-encoded VHS or TV sources . Intros and outros are not tolerated. . Group watermarks in any part of the dvd are STRICTLY forbidden The DVDR Releasing Standards Written and Organized By: AUK . SOUL . JR . MAH . PURP . CONE . MSR Signed and approved by FallingUpward . Zorlac . TmN . tNB . DNA . LotM SNATCH . EFTERLYST . ASZEON . DrDVD . ESVCD LiON . DDX . SuBLiME. iNTL . XluSiV . TRiAD ****** 2003 DVDR ****** THE 2003 DVDR RELEASING STANDARDS .. JUST A FIRST DRAFT .. [ 19JUN2K3 ] let's see how the overall response is to this draft and what needs to be adjusted and voted upon. please take time to read everything over. suggestions are VERY much welcome. that's what we're here for. ;p General: . Release size must be at least 4.15 Gb unless source is DVD5. . PAL after NTSC and NTSC after PAL is allowed. Video: . Re-encoding: . CCE version 2.50+ must be used for all purposes where the transcoding (re-encoding) of the video stream is required. Other encoding programs such as: REmpeg and TMPGenc, etc. are NOT allowed in any circumstances. . Automated Programs that perform DVD9>DVD5 rips are FORBIDDEN, e.g. InstanCopy, DVDXCopy, etc. . Minimum average bitrate allowed is 3000 kbit/s (2800 kbit/s for tv shows). If minimum average bitrate cannot be achieved, a valid explanation is required in the nfo. . Passes: . Movies below or equal 100 Minutes: 5 or more passes. . Movies over 100 Minutes: 6 or more passes. . Extras: If transcoded, 5 or more passes. . Note: The initial 1st pass that encodes the .vaf file in CCE is NOT considered a pass in any circumstance. Audio: . Dolby Digital is considered the standard audio format and is required in ALL releases. . DTS is not considered a standard audio format and is NOT a reason to proper/dupe an existing release. DTS-only releases are also strictly FORBIDDEN as valid releases. . If audio is stripped from a DVD9 disk, higher bitrates must be kept over lower bitrates (if a dvd has 2.0 and 5.1 audio, 2.0 would be stripped in favor to 5.1) unless their is a valid reason, e.g. significantly reduces bitrate. However in regards to DVDs that contain both DTS and 5.1, 5.1 must be kept. The inclusion of a DTS stream is up to the ripper's discretion. . For non-English movies, the movie's original language audio stream must be kept unless it is not contained in the retail. In the circumstances that a reissue/new edition dvd contains an original language audio stream, a re-release of the movie is valid. . For ALL English movies, the English audio stream MUST be kept. . The inclusion of other audio streams are at ripper's discretion whether they are foreign or commentary. Source: . Releases MUST be from either SCREENER or RETAIL dvds. Other sources are not allowed, e.g. PDVD, VHS, TV, TS, TC, CAM, etc shall not be tolerated. . Region duping (differs from PAL/NTSC duping), i.e. R1, R2 are not permitted unless there were problems with the first release (problems need to be stated regarding 1st release). . Releases from reissues/superior editions of previous released DVDs are only valid for: Criterion Ed. and DVDs which do markedly improve upon the initial release, i.e. contains a 5.1 stream comparitive to an inferior stream in the previous release. Authoring: . Authoring in both Scenarist and DVD Maestro are allowed. However, users of DVD Maestro need to be aware of the problem which doesn't check that if the total bitrate exceeds 9800kbit/s. Rippers should be aware that the MAX bitrate is 9800kbit/s for both audio and video streams. Subtitles: . If English subtitles are present, they will be kept under ALL circumstances. . If the dvd contains no more than three subtitle streams, all will be kept. If the dvd contains more than three subtitle streams, it's ripper's discretion which subtitles should be kept. Its advised to keep the most common used language subtitles. Menus: . Menus MUST be included. . The menu must be in English and not foreign, unless they are aimed for non-English endusers. . Menus on TV Show disk must be kept at all costs. Extras: . Extras are an added value but are not needed. Extras are allowed to be transcoded with a minimum average bitrate of 1700kbit/s. DVD Limitations: . Macro vision must be removed. . All user limitations and restrictions must be removed. . Releases must be made region free. Packaging: . All releases must either use .IMG or .ISO. Other formats NOT allowed. . Releases must be broken up into rars of 50,000,000 bytes. . Solid Archive and Recovery Record MUST be used. . SFVs and NFOs MUST be included. . NFO must include the following: . Groups name. . Title. . US theatrical release date. . Regions, NTSC or PAL. . Number of Passes and Bitrate used when re-encoding. . Audio streams, and subtitles included. . What has been stripped, extras, menu, etc. . IMDB, or similar link. . Number of archive files. Samples: . Samples are required. Minimum size shall be 30mb, but must be no more than 50mb. . Samples must be put in a separate sub directory, labeled 'Sample'. . Vobs may be cut and used as sample, or renamed to mpg. . Samples must be from actual packed vob. Separate encodes are not allowed. Directory Naming: . Directory names shall NOT exceed 64 characters. . ALL releases are to include production year. . Directory name should include Disktype (NTSC/PAL) . Acceptable characters are as follows: ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789 . -_ . DVD-5, and DVD-9 COMPLETE are recommended to be named as: Movie.Title.Year.COMPLETE.Disktype.DVDR-Groupname . Non-Complete DVD-9 releases must be named as follows: Movie.Title.Year.Disktype.DVDR-Groupname . Sub directories must be labeled DISK1, DISK2, DISK3, etc CD1, DVD1, will NOT be tolerated. ` Propers: . Propers will ONLY be released if previous had technical flaws such as menu errors, bad quality, etc. No dupes/propers if the previous release was not COMPLETE. . Propers based on previous releases having improper dir names will not be tolerated. . If previous release was not region free, a patch must be used, NOT a proper. Other Notes: . Intros and outros are not tolerated. . Group watermarks within the DVD are STRICTLY forbidden. The DVDR Releasing Standards Originally Written and Organized By: AUK . SOUL . JR . MAH . PURP . CONE ******* SVCD ****** The SVCD Releasing Standards 2002 [ RELEASE RULES ] PROPERS: - No previous releases may be propered based on audio or video bitrate. - Propers will be allowed in the case of technical problems, bad aspect ratio, sync problems, skipping/freezing, interlaced, bad ivtc, etc VIDEO: - Must be at least 1750kbit average, with a maximum of 2450kbit. - TMPGENC: 2 pass minimum - CCE: 4 pass minimum - Menus allowed. (see notes) - Subtitles allowed (and encouraged for foreign releases) AUDIO: - Minimum 224kbit @ 44.1khz (regardless of source) - Secondary tracks shall be 224 or LESS PACKAGING: - All releases must be BIN/CUE. (remove path from cue files) - Must be packed with RAR, compression is NOT ALLOWED and broken into 15 or 20 MB volumes - Recovery record recommended. - Must have SFV - Must have NFO - NFO MUST INCLUDE: Group name Title Actual SVCD release date DVD release date US theater release date Audio bitrate Video minimum/average/maximum bitrate Movie runtime/length IMDB/adultdvdempire link Number of rars per cd (eg. 44x15MB) SAMPLES: - REQUIRED - Minimum 30 seconds, maximum 1 full minute in length and in separate folder marked 'SAMPLE'. - MUST be taken from the movie - NOT encoded separately. DIRECTORY NAMING: - Directory names shall NOT exceed 64 characters. - All releases are to include production year. - DO NOT indicate Ripping method (CBR/VBR/CCE/TMPGENC and so on), WS (widescreen), DVD/SVCD release DATE, GENRE or anything else in the directory name (ONLY within the NFO). - Acceptable characters in naming a directory include (NO spaces or double dots - single dots or underscores ONLY): ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789 . -_ - All Release directories, regardless of year, shall be named according to Movie.Name.Year.Source.Codec-Group (i.e. Movie.Name.Year.DVDRip.SVCD-Group) - Releases that are more than 1 CD will follow these specs: - MUST be named CD1, CD2, CD3 and so on. ('disc1', etc will NOT be allowed). - There MUST be a SFV included for each CD. [ NOTES TO THE RULES ] Source related notes: - Source shall be DVD Only, no exceptions! - DVD Screeners shall be clearly marked in the directory name and the nfo shall contain presence of studio watermarking, or lack thereof. Ripping related notes: - Movies should be ripped in their most widescreen format available. - Group Watermarks WILL NOT BE ALLOWED IN ANY CASE. - NO intros, outros, betweenos, or any other form of defacement of the movie including possible menus will be tolerated. [ GROUPS & MEMBERS ] SVCD 2002 revision was organized by: - vimVam - ne14a69 - Respects to the original SVCD council organizers: iV - V4F - 4HM - XPD - DvCS - PTi - TBH - TWiLiGHT SVCD 2002 has been approved by the following groups: EPiC - V4F - aNBc - DEiTY - TheWretched - iFO - WiDE DvCS - PMM - TBH - SChiZO - ESVCD - PTi Also signed by: DMR - VCDWS - tNB - SportsVCD - iNFiNiTY - NAPALM - TmN Special thanks to the TDX 2002 rules for their layout and guidelines. **** MORE FROM 2002 RULES **** - All Release directories, regardless of year, shall be named according to Movie.Name.Year.Source.Codec-Group, suggested naming for the movie itself shall follow the same procedure (i.e. Movie.Name.Year.Source.Codec-Group.avi, Movie.Name.CD1.Year.Source.Codec-Group.avi). - Releases that are more than 1 CD will follow these specs: - MUST be named CD1, CD2, CD3 and so on. ('disc1', etc will NOT be allowed). - There MUST be a SFV included for each CD. - Rars MUST be broken into 2 or more CD volumes. (78 rars of a 2 disc title will NOT be tolerated) [ NOTES TO THE RULES ] Source related notes: - Source shall be DVD Only, no exceptions! - DVD Screeners shall be clearly marked in the directory name and the nfo shall contain presence of studio watermarking, or lack thereof. Ripping related notes: - Maximum VIDEO bitrates are covered by length rules. - Movies should be ripped in their most widescreen format available. - Multi-language audio tracks are allowed. - Multiple languages should be interleaved into the AVI, with a graphedit filter for each appropriate audio stream. - Movies that would ordinarily fit on one CD should not be made into 2 CD releases on the basis of additional audio tracks. - Multi-language audio CANNOT be used as a basis for a dupe. - Multi-language subtitles CANNOT be used as a basis for a dupe. - AVI and not BIN/CUE: - Some people burn to archive and play on a computer at a later time, BUT since there is no outside purpose other than playing on the computer, there is NO need to be packaged as BIN/CUE. - Group Watermarks WILL NOT BE ALLOWED IN ANY CASE. - NO intros, outros, betweenos, or any other form of defacement of the movie will be tolerated. - Movie container MUST be AVI. OGG, OGM, MCF, Project Theora, MP4 are all forbidden due to bugs and usability factors, maybe next year! [ GROUPS & MEMBERS ] TDX 2002 revision was organized by: - E.L. - V. - f3k - Respects to the original TDX, Team DivX, organizers: - krazy8 - RipKord - Wuman - Lava - MaTaN - TDX 2002 has been approved by the following DivX groups: - AEN - DOMiNiON - DVD-R - EPiSODE - EPiC - INCiTE - MDX - - QiX - SChiZO - VCDVaULT - Also signed by: - SATELLiTE - InFuX - aNBc - DEiTY - MEDiAMANiACS - DVL - - CPY - JDX - DDX - REQUiSiTE - SEVcD - FoCUS - - DiSTORTiON - COLLiSiON - **** 2004 SWESUB SVCD **** ----------------------[- SWESUB STANDARDS 2004 -]------------------------------- .1- ---| Aspect Ratio PAL 576x480 / NTSC 480x480. ---| Only FS 4:3 and WS 16/9 are allowed. Not anamorphic ws becouse they ---| dont work 100% on all standalone dvdplayers. ---| Telecid should be turned on to get ultimate quality ( if movie is interlaced ) ---| Never release a movie if less bitrate then 1674 or highest 2450 +-1% ---| Examples below ---| ( 104Min 74Min=2CDS = 1702 Bitrate ) ---| ( 112Min 80Min=2CDS = 1708 Bitrate ) ---| ( 156Min 74Min=3CDS = 1702 Bitrate ) ---| ( 168Min 80Min=3CDS = 1708 Bitrate ) ---| MAX Bitrate 2496 MIN Bitrate 1554 use 120 or more from MIN/MAX AVG bitrate ---| else cce/tmpgenc can fail ---| Never use less PASS then below and always use Varible Bitrate. ---| Tmpgenc: 2 PASS VBR (Min) ---| Cinema Craft Encoder: 4 PASS MVBR (Min) ---|----------------------------------------------------------------------------- .2-[ViDEO+SOUND] ---| PEAK Video + Audio ---| Bitrate on video max avg 2450 + Sound 224kbs 44.1Khz = PEAK at MAX 2674 AVG ---| Bitrate on video min avg 1674 + Sound 224kbs 44.1Khz = PEAK at MIN 1898 AVG ---| So never go less then 1898 AVG. and never go higher then 2674 AVG ---|----------------------------------------------------------------------------- .3-[AUDiO] ---| 224Kbs 44100Khz STEREO ---|----------------------------------------------------------------------------- .4-[sUBTiTLES] ---| Subtitles should be as on DVD. / alternative at one 16/9 movie 50/50 on bottom ---| border if subtitles 100% is in the picture. ---| Only Permanent subtitles allowed. ---| Fonts should be ( Verdana ) they are easiest to read. ---| Subtitle color should be white. ---|----------------------------------------------------------------------------- .5-[sAMPLE] ---| Sample should be 1Min no more or less. ---|----------------------------------------------------------------------------- .6-[PACKAGiNG] ---| All releases must be BIN/CUE. ---| Must be packed with RAR, compression is NOT ALLOWED and broken into 15MB volumes ---| If 2/3/4 CD release last CD shouldnt be less then 44/45X15MB = 650MB+ ---| Must have SFV ---| Must have NFO ---| Directory names shall NOT exceed 64 characters. ---| Another.Movie.SVCD.DVDRip.SWESUB.YEAR-GROUP : Example what should be in one dir ---| Allowed disc dirs CD1 CD2 CD3 Sample not Cd1 Cd2 Cd3 or Disc1 Disc2 Disc3 ---| Always use small letters in the .rar archive and .nfo ---| Nfo file another.movie.svcd.dvdrip.swesub.year-group.nfo : Example ---| If its possible please use SVCDINFO.TXT its one proof of the svcd quality ---| FS = 4:3 and WS = 16/9 and if movie is STV or LiMiTED you need to have that info ---| in .NFO or DIRNAME. ---| On movies from .SE .NO .DK .FI should movie be named like retail/theater title ---| from that country. ---| On other movies use .US retail/theater title. ---| Acceptable characters in a directory ---| ABCDEFGHIJKLMNOPQRSTUVWXYZ ---| abcdefghijklmnopqrstuvwxyz ---| 0123456789 . -_ ---|----------------------------------------------------------------------------- .7-[MENUES/INTRO] ---| Menu is allowed if they are like source. ---| Never use intro/cd change pictures ---|----------------------------------------------------------------------------- .8-[PROPERS] ---| No previous releases may be propered based on audio or video bitrate. ---| Propers will be allowed in the case of technical problems, bad aspect ---| ratio, sync problems, skipping/freezing, interlaced, wrong placed subtitles, ---| other font colour then allowed and bad .rar archives,, or stolen sourches. ---|----------------------------------------------------------------------------- .9-[DUPES] ---| FS = 4:3 Dupes WS = 16/9 ---| Wierd proper reasons ---| Retail subs never dupe Custom sub.... ---|----------------------------------------------------------------------------- .10[REENCODE] ---| Dl a dvdr and encode to svcd its NOT oké... And if its one COMPLETE DVDR ---| (not encoded movie) then you need to have PERMISSION from the group that ---| released it to make svcd swesub from that.. or else its STOLEN. ---| Simple honor by thiefs..... ---|----------------------------------------------------------------------------- .11[THEATER?] ---| What is limited and stv? ---| An limited movie has 1-499 (SCREENS) .US and 1-299 (SCREENS) .UK ---| A stv never hit one public theater and got straight to video ---| If movie is Festival it will go like limited. ---| You can find all info at www.imdb.com ... ---|----------------------------------------------------------------------------- -----------------------------[- SiGNED BY -]------------------------------------ BBSvCD - PWRSVCD - CaKe - PiTch - iNSANE - DiTS -------------------------------[- 2004 -]--------------------------------------- Updated 2004-01-26 Fim ??? ***** 0 DAY ***** 0DAY: Dupes: We can be very quick with this one, below an example (The "CuNT" release is a real dupe) 2002-10-20 Jack.The.MP3.Ripper.v1.0.cracked-DiCK 2002-10-30 Jack.The.MP3.Ripper.v1.0.incl.keygen-CuNT But a Jack.The.MP3.Ripper.v1.0.keygen.only-CuNT is allowed! Nuke reason: dupe.<yyyy-mm-dd>.<group> Mu: In general we handle a MinorUpdate period of 14 days! If you release a new version of a program with in 14 days of the last program release , but 14 days from the last release out no matter if its nuked for MU or not. Example: 2002-10-10 Jack.The.MP3.Ripper.v1.0.cracked-DiCK 2002-10-15 Jack.The.MP3.Ripper.v1.1.incl.keymaker-CUNT <- (nuked for MU) Next version is allowed on 2002-10-29 AND NOT on 2002-10-24, coz we count 14 days from the last release, no matter if its nuked for MU or not. Additionally to bring some more clearness: 2002-10-10 Jack.The.MP3.Ripper.v1.0.cracked-DiCK 2002-10-14 Jack.The.MP3.Ripper.v1.0.keymaker.only-CUNT So v1.0 cracked gets released on 10th of oct. and the keymaker.only on 14th then the next release is allowed on 2002-10-24, no matter what time the keymaker.only was released. coz we always count 14 days of the release that included the setup-file of the software itself. The following groups have agreed to comply to these rules (ask handymen to add ur group here): LAXiTY/ACME/DWP Nuke reason: mu.<yyyy-mm-dd>.<group> Release Name creation: <PROGRAM NAME>.vX.XX.<opt. options>-<GROUP NAME> <PROGRAM NAME>_vX.XX_<opt. options>-<GROUP NAME> Examples: The.true.story.by.php.monkey.v1.4-D2D The_true_story_by_php_monkey_v1.4-D2D Nuke reason: bad.dir File naming: Files should be named as stated in the 8.3 notation. And disk size should be between 720 KB and 5 megs. It also has to include a .diz and .nfo file Example: lxtd2d2.zip Nuke reason: bad.pack Size: Maximum size of 0day release should be 300 MB Nuke reason: oversized Keygen rules: A keygen is a standalone program which calculates serials based on pc name/company/user name etc etc. When a serial algo uses fixed chars on certain positions and your "keygen" fills the other positions with random data it's NOT a keygen. When a keygen is not sufficient and a crack is required, the dir name should include this "incl.keygen.and.patch" Nuke reason: not.a.valid.keygen Theft: Using a keygen/serial/crack with out permissions of the owners (other groups for example) is not legit. A group which is cought 2 times with stealing will be banned here aka being auto nuked (ofcourse if there is good evidence) Nuke reason: stolen Repack: Fucked up releases can be re-released by doing a repack. Dir should contain ".repack.". The previous (bad) release will be nuked Nuke reason: get.repack Trade/pre faults: Trade faults ("detecting macro monkeys" dirs for example), pre tests or fake things will not be counted as a legit release. Nuke reason: crap Free software: Software which is freely available is not allowed. "Free" on d2d means that it costs around $0.00. "Cardware" or "free-registration" is. There are 2 exceptions there is, if a upgrade/update is not publicly available. And free updates/upgrades which will render the crack/serial/keygen of the previous version unusable (ie. they blacklisted stuff) Nuke reason: free Newer out: When a group releases a v1.02 of a program and the new version v1.03 is already out for more then 3 days, it's a nuke. The grace period is 3 days. Only exception COULD be an util group having a hard to get program (thus means not publicly downloadable) and they release it when there's just a new version out, if this happens (unlikely:D) tell so in info file Nuke.reason: newer.out.v<x.xx> Crack malfunction: If a crack/serial/keygen is not working 100% it's a nuke! This could mean a keygen without a server patch, a keygen which doesn't accept certain basic chars "A-Z,a-z,0-9" and ofcourse spaces (only when the program accepts these chars!) or a crack with missed checks having removed. Nuke reason: bad.crack Group request: If a group really thinks they fucked up a release badly then they can do a group request. The release will be nuked then. Nuke reason: grp.req Beta software: Betas / builds / rc are allowed only it's not an hidden beta/build/rc, means the word "Beta", "build" & "RC" has to be in directory name. Nuke reason: hidden.beta Types Allowed: - ALL languages (Dutch, German, Chinese, Italian, Polish, etc etc) - ALL platforms (PC, MAC, Linux, Solaris, OS/400, Windows, etc etc) - Bookware - HW required software (GSM & Telephone programs) - Kiddie (some people have kids here, hi fanny:) ) - Addons (all types of addons for utils/games) - Commerical fonts - Screensaver - Porn - Different kind of flavors (Standard, prof, premium are ALL allowed) ***** 0DAY AMENDMENT ***** In April 2002 groups across the 0day scene united to update the current rules to better shape todays scene. Below is detailed information on updated rules as well as new rules. These rules must be recognized and followed immediately on this date, April 12, 2002. 1. Max one version per application / 14 days. 2. 0day rips should not contain free software which can be downloaded from the web, such as DirectX/Acrobat Reader. 3. To prevent sloppy rips, a re-release of a 0day application is allowed to make groups release proper and respectable releases. In order to be considered as legit, the re-release must be at least 15MB smaller than the previous release. The following provisions include: a) No essential data is allowed to be removed to be considered a valid re-release. A re-release from a competing group may not use tools, cracks nor any other files from the previous release that were modified for the original rip. The re-release of a rip can be done by any group and must be done within 48 hours after the release of the original rip. 4. Rips created with another groups ISO are to be nuked unless the ISO group have given it's permission to have their iSO ripped. All appointed HQ (Headquarters) should abide by these rules to the fullest extent permutable. Any group that competes in the 0day rip scene will and must abide by the above rules to allow fair competition among all competitors. Take into account that these rules do not apply to nor concern the game rip scene. Signed, Leaders, Council Members and Seniors of Blizzard, Caudex, Core, Digital Factory, Oddity, Orion, The Millenium Group, Epsilon, Eclipse, Embrace, Renegade, Intension, Paradox, Prime, Among others! ******** PDA ***** ___ ___ _ ___ _ _ ___ ____ ___ _ ___| __| __(_)/ __(_)__ _| | | _ \ _ \ / _ \ _ _ _ _| |___ ___ / _ \ _|| _|| | (__| / _` | |__ | _/ |_) | _ | '_| || | / -_|_-< \___/_| |_| |_|\___|_\__,_|____| |_| |____/|_| |_|_| \_,_|_\___/__/ cREATION dATE : [14]-[APR]-[2002] ____/\_____/\_____/\_____/\_____/\_____/\_____/\_____/\_____/\_____/\____ |___> <___> <___> <___> <___> <___> <___> <___> <___> <___> <___| \/ \/ \/ \/ \/ \/ \/ \/ \/ \/ RELEASE-NAME-CREATION : *********************** <program name>.vX.xx.<optional Language>.PalmOS.<cracktype>-<groupname> <program name>.vX.xx.<optional Language>.Machine-Type.SymbianOS.<cracktype>-<groupname> Machine-Type : e.g. N9210 or N9210i (Nokia Communikator) <program name>.vX.xx.<optional Language>.CPU.OP-SYS.<cracktype>-<groupname> OP-SYS can be CE that is CE 2.0 PPC that is for WinCE 3.0 but its not called CE, 99runs also on new ARM machines with PPC2002 HPC2000 that is a HandheldPC with keyboard (no pen) only ONE from HP existing PPC2002 that is successor of PPC now most common and runs only on ARM machines CPU types can be SH3 is SH3 CPU MIPS is MIPS CPU ARM is STRONG ARM CPU IPAQ is NOT a cpu but runs ARM , there are progs that run only on IPAQ so IPAQ has to be named as CPU For future extensions : If there is a program version for a special machine then name the machine type instead of the cpu ( see the IPAQ example above ! ) or use underscores if you like: <program name>_vX.xx_<optional Language>_PalmOS_<cracktype>-<groupname> <program name>_vX.xx_<optional Language>_ALL_OP-SYS_<cracktype>-<groupname> <program name>_vX.xx_<optional Language>_SymbianOS_<cracktype>-<groupname> <groupname> has to be <name>pda to part the pda section !! Examples: WOMAN.v1.4.JAPANESE.PalmOS.Regged-GROUPpda WOMAN_v1.4_JAPANESE_PalmOS_Regged-GROUPpda WOMAN.v1.4.JAPANESE.ARM.PPC2002.Regged-GROUPpda WOMAN_v1.4_JAPANESE_ARM_PPC_Regged-GROUPpda WOMAN_v1.4_JAPANESE_SymbianOS_Regged-GROUPpda optional language tag should only be used on NON english releases... EBOOKS : ******** <ebook name>.<Edition>.<optional Language>.OP-SYS.-<groupname> Edition : Bookversion or Edition OP-SYS : OperatingSystems eg. PalmOS, PPC CRACKTYPES : ************ can be : Regged serial data is included in nfo Cracked the program file has been altered to register the proggy. The program is then "Preregistered", "any name and/or serial can be entered" or "nags/trials removed" Incl.Keymaker if keymaker is included in package Incl.Keymaker.Patch if program is patched and shows correct serial relating to the hotsyncname(palmos,ppc) after program start or after entering any serial Incl.PalmOS.Keymaker if keymaker for PalmOS is in the package (if you wanna use some kind of plugin system for your keygen you HAVE to incl. the plugin-proggy too (not only the plugin)) Incl.WinCE.Keymaker if keymaker for WinCE is in the package (if you wanna use some kind of plugin system for your keygen you HAVE to incl. the plugin-proggy too (not only the plugin)) Incl.Java.Keymaker if keymaker comes via java applet, the java applet has to be delivered with a name.html file that loads the java app. if a Keymaker is only in the package then a url to get the prg has to be included in nfo ! if a Serial (HOTSYNC independent!) is only in the package then a url to get the prg has to be included in nfo ! Allowed are : Keymaker.Only JAVA.Keymaker.Only PalmOS.Keymaker.Only OPL.Keymaker.Only (Epoc16) OP32.Keymaker.Only (Epoc32) CPU.OP-SYS.Keymaker.Only Keymakers can be written in : Dos, Win32, PalmOS, WinCE, Java ( with start.html ) RELEASE RULES : *************** Release format/size : If a release is bigger than 1.44 mb then it has to be parted in 1.44/2.88 MB packages ( ISO can be packed with rar (most common) ) Keygens: A keymaker is allowed to be only (re-)released 1) when a major version hop of the application occurs i.e. 1.xx -> 2.xx 2) when the key algo changes. An algo-change has to be announced by including READ.NFO in dirname AND a short description in the nfo (for example: "Keygenalgo changed ...") 3) when there has not been a re-release within a 1 year. Example(1) : Keymaker released first time for v1.43 . The first time it can be replaced for not being a dupe is when the version changes to v2.xx or if the keyalgo changes. So also in v1.44 Example(2): Prog.v1.1.incl.Keymaker-GRP released 01/01/2000 the next allowed release date for Prog.v1.11.incl.Keymaker-GRP would be 01/01/2001. Its (of course) not allowed to release the SAME version again after a 1 year Keymaker.Only releases are allowed, but then include the url where where to download the program in the nfo. Keygenpatch: A Keygenpatch is a patch that alters the program that it shows the right serial for the actual hotsync (and which regs it of course). Keygenpatches are like Keygens (same rules here) with one difference: Its allowed to release a Keygen after a Keygenpatch (even for the same version) Cracks: Cracks in form of patched programs can be released for every version UNTIL they got keygened or a serial is released. If a keygen or serial gets invalid for some reason a new crack can be released. Regged: Can be a serial or name + serial. (hotsync id independent) (Serial) Same rules as for keygens apply here (major version hops, serial change, 1 year rule...) Retail: A retail is treated like a crack with these exceptions: - You are allowed to release a retail after a serial/crack/keygen/keygenpatch IF (!) there's something special added (some kind of extra stuff that you dont have in the shareware/ demo version). If thats the case you have to add a READ.NFO to the dirname and list whats the additional stuff. Normally retails should be released when its not possible to download an uncrippled version which can be regged/keygenned. All releases must be (zip-)packed with the necessary files for the release and a .nfo and .diz from the group. IMPORTANT INFO TO SITEOPs : *************************** As we have seen in the past, there are some rules which prevent groups releases being nuked on an affiliate site. We think that if a valid nuke reason applies to any release, it should be nuked on all sites - affil or not. ->>> AFFIL PREVENTS NOT FROM BEEING NUKED !! << RULES SIGNED BY -+-+-+-+-+-+-+-+- APR 2002 -- COREpda APR 2002 -- UFCpda APR 2002 -- BLZpda APR 2002 -- NLPDA ***** 2003 TV ***** R E L E A S E R U L E S v1.5 (11/16/02) Nuking has always been an issue in the TV scene. So here is the ruleset that tries to cover up the mess a little. DIGITAL CAP: This includes any real digital source that didn't pass through any analog interface between the source (Sat/Antenna/Cable) and the file on your computer. This includes ATSC off-air antenna signals carrying MPEG2 Transport Streams (using cards such as MyHD/Hipix/WinTV-HD), DirecTiVo MPEG2 Streams (not standard TiVo!) and DVB Stream Capture cards. *HDTV* (High Definition Televison): Digital recording from a source stream at either 1080i or 720p at a bitrate from 19,39mbps or higher. *PDTV* (Pure Digital Television): Other resolution digital recor- dings from source streams at a bitrate of 10+mbps or higher. - This includes digital recordings from digital C-Band and DVB. *SDTV* (Standard Digital Television): Digital recording or capture from a source stream at any resolution with bitrate under 10mbps. - This includes DirecTiVo but also captures from digisat or digicable with analog capture cards. note: For SVCD, analog cable and antenna caps are not allowed, so SDTV is the lowest allowed source and will have no label. See NAMING below. note: HDTV and PDTV rips are digital recordings, although PDTV was labeled wrongly in the past by some groups (TiVo is NOT PDTV). ANALOG CAP: This includes any source that went through at least one Digital -> Analog -> Digital process. This includes Standard TiVo, any MPEG2 capture card, any DV source (unless you're releasing your home videos that were actually shot on a DV camera) or any other standard capture card. PDVTV and HDTV is NEVER captured in analogue, on the other hand a SDTV cap can be both. COMMENTS: For SVCD/DivX, any video, regardless of Analog or Digital should be converted to 23.976fps (NTSC) or 25fps (PAL) "Progressive Film" for correct encoding. A LOT of group don't bother with this step and thus their encoding quality suffers, regardless of their source quality. Even if your source video comes as Progressive 59.976fps (as it can with ATSC sources), you must still convert to the proper frame rate or your video will be jerky or waste bits. For any NTSC encode (other than live shows like the "Tonight Show") the video must be converted to 23.976fps through the use of IVTC or duplicate frame elimination (for ATSC 59.976fps progressive sources) prior to SVCD encoding. And once encoded, you must enable the 3:2 pulldown flag to enable playback at 29.976fps (even though the sour- ce still remains at 23.976fps). Analog Cable or Analog Antenna rips on SVCD are NOT allowed. DUPE RULES: - SVCD Releases: . HDTV: - DUPE if there was a PDTV or a HDTV release. - NO DUPE if there was only a SDTV or a VCD version. . PDTV: - DUPE if there was a PDTV or a HDTV release. - NO DUPE if there was only a SDTV or a VCD version. . SDTV: - Obvious. DUPE if there was previous release without technical issues. - NO DUPE if there was only a VCD version. . Widescreen does NOT dupe Fullscreen and vice versa. - VCD Releases: . No matter what source, the first release wins. Every other VCD release is a dupe. - DivX/Xvid Releases: . HDTV: - DUPE if there was a PDTV or a HDTV release. - NO DUPE if there was only a SDTV or an analog cap. . PDTV: - DUPE if there was a PDTV or a HDTV release. - NO DUPE if there was only a SDTV or an analog cap. . SDTV: - DUPE if there was already a analog cap. technical issues. . Analog cap: - Obvious. DUPE if there was previous release without technical issues. . Widescreen does NOT dupe Fullscreen and vice versa. NUKE RULES: - A release is considered as a NUKE, if: . It's a DUPE. . It has technical issues. . Wrong or no source/cap information is specified in the .nfo. NAMING RULES: The following tags are used for SVCD releases: - "HDTV" for HDTV caps. - "PDTV" for PDTV caps. - "SDTV" or nothing for SDTV caps. . VCD releases don't need to be tagged. . Widescreen releases are tagged with "WS", otherwise they are supposed to be fullscreen. PROPER RULES: - A PROPER is only valid when the previous release has technical issues. A HDTV after a PDTV rip is no reason to dupe and there- fore no reason for a PROPER if the previous release was ok. **** 2003 MUSIC VIDEO **** Music Video Council 2.0 FINAL This document is designed to resolve problems with dupes, propers, REAL_PROPERS, etc.. and to ensure that only quality releases are released to the MV scene. The following groups have agreed to follow these guidelines: FSPViDZ GOD kvz MiLF mkv mv mVa mVi mVz pHViD rHViD SE UVZ VME wcs Index 1) Encoding 2) Releasing a) Dirname/Filename Logos c) Concerts & Live Performances d) NFO 3) Propers & Dupes 1) Encoding Two formats will be allowed: SVCD and VCD. - This means that any other format, such as: XVCD, XSVCD, nVCD, DIVX, XVID, DVDR/DVDS will not be allowed. If you must, keep them INTERNAL. VCD Audio - MPEG-1 Layer 2 44.1KHz 224kbps - Replacing audio on VCD rips is RECOMMENDED, but not required. VCD Video: - PAL - 1150kbps CBR, 352x288, 25 fps. - NTSC - 1150kbps CBR, 352x240, 29.970 fps. - NTSC-FILM - 1150kbps CBR, 352x240, 23.967 fps. (via IVTC) SVCD Audio - Audio must be replaced on all SVCD music videos. Replacement audio must be from a CD, or from a high bitrate MP3 (192kbps+) ripped from a CD. All video soundeffects must be inserted into the replac- ement audio * If replacement audio *DOES NOT EXIST* for videos older than 1998, then you can release with normalised tv audio, AND, IF REPLACEMENT AUDIO BECOMES AVAILABLE, it's a PROPER * Vinyl ripped MP3s are not to be used. Replacing less-than-cd-quality with less-than-cd-quality is pointless. * Use uncensored audio. If you use censored audio, prepare to be propered. - Live rips (concerts, performances) use normalised audio from source. If source is 48KHz, downsample to 44.1KHz. SVCD Video: - PAL - Should be inverse 2:2 pulldown manually, if possible. (This is also known as manual-deinterlace) - NTSC - Should be inverse 3:2 pulldown manually, if possible. (This is also known as IVTC). If 3:2 pulldown is not possible, then inverse 2:2 pulldown manually, if possible. (This is also known as manual-deinterlace) - Interlaced videos will not be allowed. - Video and audio bitrate MUST be within SVCD standard. For maximum player compatibility, it is STRONGLY RECOMMENDED that the video bitrate does not exceed 2496 kbps. - SVCD rips must not be ripped from VHS or SVHS source, due to the sub-SVCD specs of both formats. VHS resolution (analogue) approx 240 lines of resolution. SVHS resolution (analogue) approx 400 lines of resolution. VCD resolution = 352x240(NTSC), 352x288(PAL) SVCD resolution = 480x480(NTSC), 480x576(PAL) VHS/SVHS is only sufficient for VCD rips. SVCD rips from VHS/SVHS must be kept INTERNAL. 2) Releasing 2a) Dirname/filename - Directory name is decided by the group. However, the following naming scheme is STRONGLY RECOMMENDED: Artist_name-Song_title-extra_info_here-FORMAT-YEAR-GRP Example: Britney_spears-Baby_one_more_time-Live_in_london_01_03-SVCD-2003-GRP - SFV and NFO are required. - The standard extension is .mpg for both VCD and SVCD releases. However, it doesn't matter, so groups decide to use .mpg or .m2v as extension. 2b) Logos - Including an intro/outro is NOT RECOMMENDED. Advertisements in your videos is not what the MV scene is about... if you must spam, then do it your NFO file. However, intro/outro will not be banned, and propering a video with a logo will not be permitted. - Watermarking on videos is NOT ALLOWED. This is the same situation as intro/outro - nobody wants to stare at your spam while watching your rips. It's already bad enough that tv stations do it. Videos with watermarks can be propered. For letterboxed videos, covering a TV station logo that is entirely in the letterbox is RECOMMENDED. However, propering because of tv-station-not-covered will not be permitted. 2c) Concerts and Live Performances - Concerts involving one artist must be released as one release. This means, for example, that if you rip a concert of Linkin Park at the Royal Albert Hall, you CANNOT release each song as a release. - You should include the main introduction and any other introductions between songs, as the point in ripping a concert is to have a COMPLETE copy of the concert. - The ripper decides to rip as separate tracks or as full CDs. If you rip as separate tracks, DO NOT PUT A LOGO ON EACH TRACK. Single-tracks ripped concerts should be packaged in ONE release, similar to a mp3 album: Artist-concert_title-svcd-2002-group/00-artist-concert_title.nfo Artist-concert_title-svcd-2002-group/00-artist-concert_title.sfv Artist-concert_title-svcd-2002-group/01-artist-introduction.mpg Artist-concert_title-svcd-2002-group/02-artist-song1.mpg Artist-concert_title-svcd-2002-group/03-artist-song2.mpg If you rip as full CDs, it is recommended that you use multipass VBR to make it fit evenly on one or more CDs. Also package it as a BIN/CUE, and release it the same way VCDs are: 15mb rars, and a 1 minute sample: Artist-concert_title-svcd-2002-group/CD1 Artist-concert_title-svcd-2002-group/CD2 Artist-concert_title-svcd-2002-group/Sample Artist-concert_title-svcd-2002-group/nfo_file.nfo - Non-concert live performances with more than one song, such as those on TOTP, awards shows, etc. should be released as individual videos with any intermediate footage (interviews, presentations, etc.) cut out. Also, include the date and the name of the show in the dirname. - COMMERCIALS (such as Britney Spears' Pepsi) are not music videos, so they will not be allowed. Keep non music video rips INTERNAL. 2d) NFO - Your NFO should contain: - Artist and Title - Format (VCD/SVCD, and PAL/NTSC/NTSC-FILM) - Video source - Audio source - Deinterlace type - Size - Genre (This is nice for sites with scripts that search NFOs for genre) - Video Year - Live videos MUST include the show it is from and the date it was aired. - If you are propering, you MUST include the reason for proper, and the name/date of the release being propered. - Other useful information to include in your NFO, optionally, is: - Length in min:sec - Bitrate of video and audio streams - Album name - Description of video - Fullscreen or Letterbox (FS or WS) - Source (Name of DVD or name of TV station) 3) Propers and Dupes Propering because of SLIGHT quality increase is not acceptable. If the original rip was very bad, then proper, but un-neeeded propers will be nuked ! - PAL & NTSC NTSC and PAL dupes will NOT BE ALLOWED. Keep PAL/NTSC dupes INTERNAL. Releases of lower quality are dupes of higher quality, as decided by the following list, which is in order of lowest quality to highest: CONVERT TV-Rip, CONVERT DVD-Rip, NATIVE TV-Rip, NATIVE DVD-Rip Native: This means progressive. NTSC produced video is native to NTSC broadcasts, and PAL produced video is native to PAL broadcasts. Native NTSC broadcast means IVTC-able NTSC or progressive NTSC. Native PAL means progressive PAL. Convert: This also means deinterlaced. A PAL produced video, broadcast in NTSC, is converted before it's bradcasted. A NTSC produced video is converted to PAL before it's broadcasted. These converts cannot be reversed to progressive, and must be deinterlaced. Hence, it is not a good idea to release pal-ntsc converts of top 50 videos, because a native rip will be released. - Widescreen/fullscreen dupes will not be allowed. Keep WS/FS dupes INTERNAL. - The following are reasons for you to release a PROPER: - Desync - Incomplete - Improper inverse 3:2 or 2:2 pulldown - Lack of inverse 3:2 or 2:2 pulldown (when possible) - Out-of-spec rips - Massive frame drops - Very bad quality (includes low bitrate on high motion videos) - Rips without replaced audio (Concerts/performances excluded) - Native video with correct picture aspect is broadcasted - Logo included more than once in a concert release - Watermarked video - Censored replacement audio - Improper multiplexing (such as underflowed audio) It is vitally important that you state which release you are propering and your reasons in your nfo, and as well make sure to put -proper- in your dirname. - It is STRONGLY RECOMMENDED that you demux with M2 edit, and remux with bbmpeg, to avoid improper multiplexing errors. - No propering of releases previous to MV COUNCIL will be allowed. If you want to release a better version of an OLD video, keep it INTERNAL ! - MV COUNCIL 1.0 FINAL begins on 01 OCTOBER, 2002. - MV COUNCIL 2.0 FINAL begins on XX XXXXXXX, 2003. **** 2002 MUSIC **** Release Rules 1. No Dupes ! We check complete albums/releases, not single tracks. So a release is not a dupe if it has different or more tracks. Exceptions: 1. It's also a dupe if the complete release is included in a previous one. For example CDM is released, now someone releases the CDS and all tracks of the CDS were already included on the CDM (exactly the same). 2. You are allowed to create a duplicate release from a release that has a source of lower quality (not lower bitrate! (see rule 11)). Example: if vinyl is out then a CD-release is allowed. If you do that then please add this info to NFO and dirname. 3. All MIXED cds should be ripped as one track supplied with a .cue. If they are not, they may be duped by another group that releases it as one track with a .cue supplied. 2. An .SFV and .NFO file must be included in every release. 3. Directory name must at least contain: Artist Name - Title - Published Year - Group name (extra info is allowed of course) 4. Filename must at least contain: Track Number - Song Title If it's an album with different artists then you must add the artist name as well. Make sure that your filename is unique otherwise some sites might dupeskip it. (You can search for filenames here as well) 5. Files/directories must only contain characters; a-z A-Z 0-9 _ . - () This is to avoid problems with windows/linux-filesystem and ftp-servers. 6. No self made compilations A selfmade compilation is when you select tracks from other sources, put them together and release that as something new. A self-made MIX is allowed if it's good. Sites decide if it's shit by nuking it. We won't nuke/unnuke such a release. 7. The entire CD,Vinyl,etc. must be released (not individual tracks) If you think it's too much work to rip all tracks you better don't rip at all. Releasing the complete CD/Vinyl is necessary because otherwise it would be possible to make several (different) releases of the same cd/vinyl/etc.. Exception: If an album has been released in different editions and the only difference is one or more bonus tracks then it's allowed to release the bonustrack(s) only. For example album released in US with 10 tracks, Japanese edition with 11 tracks (1 bonus track). then you can release the jap bonus track only (without including previously released tracks of the US album). Of course it's not allowed to re-release the full japanese edition then. You can do either the full album including the bonus track or only the bonus track, but not both. You must release ALL additional tracks in one release (not one release per track or side). 8. Current maximum directory/filename-length is 128 characters because of limitations on windows cd-filesystem (linux has 256char-limit) and about 99% of the people here use either windows or linux. Directory names longer than 64 chars are marked to make it easier for people using joliet-filesystem which officially has a 64-char-limit (but most of the cd-writing-programs ignore that and windows is able to read it up to 128 chars). 9. No fake-releases 10. A bad rip/release must be reported by either 3 independent people (from different groups) or the group which released it (release-comment or web board). If you re-release something that hasn't been nuked/marked yet then add this info to your nfo-file. Otherwise it will get nuked as dupe. 11. Quality current minimum bitrate is 160kbit it's not allowed to re-release something in 192kbit (or higher) because a previous release was only 160kbit. 12. Promos If a release is considered not to have every track from the source then it must be labelled as a promo and can be duped by any legitimate retail release that DOES contain all tracks. The legitimate release can be identified by the CAT number, or more suitable proof. Promos do not have to contain track listings, they are promotional material, they are not considered legitimate releases, and are still governed by quality rules. 13. Re-encodes are strictly forbidden. **** 2000 MP3 UNOFFICIAL **** MP3 Council (un)Official Scene Releasing Standards 2000 1. An .SFV file must be produced for verifying every release. 2. An .NFO file must be produced for every release. The NFO file must feature at least: - Title - Artist Name - Label - Release Date - Tracks - Genre - Encode Bit rate - Source - Encoder Nfo must contain as much information about the release as possible, a recommendation is that you place a release notes section in the NFO 3. Directory standard The following are the standards for directory naming: Directories must only contain characters; a-z A-Z 0-9 _ . - ( ) The filenames cannot contain () through artist neither in dir nor in filename All release data will be held within one release directory; no CD1, CD2 directories Various Artist releases must start with "VA", soundtracks with "OST". Underscores and singular periods will be used. No double periods, i.e. ".." Length of ALL directories/filenames must no exceed 64 characters. Directory naming will follow this format (spaces are used to better display the format): Artist Name- Title - Additional Information - Published Year - Group name i.e. "artist_-_title-4cd-2000-group" Additional information tags are (suggestions): VLS - vinyl single (1-2 tracks) EP - vinyl maxi-single (2-5+ tracks) LP - vinyl full-length album CDS - cd single (1-2 tracks) CDM - cd maxi-single (2-5+ tracks) MD - minidisk Promo - promotional XX-import RETAIL - retail ... etc. 4. Filename standard Files must only contain characters; a-z A-Z 0-9 _ . - () Dots are not allowed as replacement for spaces in filenames because it slows down windows File naming will follow this format (spaces are used to better display the format): Track Number - Artist - Song Title - Additional Info - Group.mp3 Track numbering example: Single CD Release, or non CD and less than 2 sides, cds, etc... 01-... (track 1) 02-... (track 2) etc. Multi CD Releaes, or non CD and more than 1 side, cd, etc... 101-... (track 1 from cd 1) 102-... (track 2 from cd 1) 201-... (track 1 from cd 2) 202-... (track 2 from cd 2) etc. For vinyl releases you may also use the naming scheme a1, a2, b1, b2, etc... 5. Encoding One of the following encoders MUST be used: - Fraunhofer HQ - LAME - http://www.sulaco.org/mp3/ Encode Bit rate: Only 160JS or 192FS (Not 160FS or 192JS). For comedy or lower quality sources 160JS. Encode Bit rate from a quality source 192FS should be used. 6. No dupes! You are not allowed to create a duplicate release from any other source if the original CD has already been released. You are allowed to create a duplicate release from a source of lower quality. (not allowed: vinyl after CD release - allowed: CD after vinyl release) A release is a dupe if the complete release (all tracks) is included in ONE previous release. Futhermore if a release is different because it has less tracks it is not allowed to be released when a release previous to it contained all the tracks from this release. 7. Mixes must include track listing (in NFO) and a .CUE file if possible (N/A for live mixes). 8. No self made compilations. (YES DJ Mixes r still allowed) 9. All ID3 tags must be generated correctly (appropriate information in the correct fields). 10.The entire CD,Vinyl,etc. must be released (not individual tracks). 11.Live recordings (from radio) must contain a date when they were broadcast. 12.Including covers or CD-Extra tracks (videos, etc...) in a release is optional. This Document was signed & approved in August, 2000 by the following individuals, representing their respective groups: crayfish(CMG) fido(AMOK) deepdown(NBD) azmd(MOD) wonder(UBE) fastjack(STAR) luna6(NuHS) karmacoma(kW) hopkin(sb) xtream(SS) uforia(eMission) atg(ATR) wezel(HS) eminenz(cnmc) trax(trbmp3) trancer(tclub) stryker(OZM) Luke Link to comment Share on other sites More sharing options...
Prince Posted September 21, 2007 Share Posted September 21, 2007 Boas...Que curioso...ainda ontem estive no site da thescene e estive a ler isso.... mas ja agora Luke...de onde tiraste estas regras? Me parece que já estão desactualizadas....o divx já foi banido...pelas regras de 2005. Mas de qualquer maneira é sempre bom saber o porque das coisas ;) e que há pessoal interessado...Fiquem! Link to comment Share on other sites More sharing options...
Luke Posted September 21, 2007 Author Share Posted September 21, 2007 Acho que estas regras são as actualizadastb não as li todasVou ver se saiu uma versão + recente :y:Luke Link to comment Share on other sites More sharing options...
Elf Eyes Posted September 21, 2007 Share Posted September 21, 2007 Luke, podias ter formatado um pouco o texto e simplificado... tem muitos termos tecnicos...Cumpz Link to comment Share on other sites More sharing options...
iNSPiRE Posted September 21, 2007 Share Posted September 21, 2007 Luke, se calhar mais valia colares o link de onde estás a copiar isso ;) só uma ideia, visto que a apresentação não está muito apelativa lol Link to comment Share on other sites More sharing options...
sosia Posted September 21, 2007 Share Posted September 21, 2007 (edited) http://datuve.lv/faili/Scene.Rules.Courtesy-FSC.nfo.txtAchei que era mais fácil meter o link, não Lunke? :funny: Edited September 21, 2007 by sosia Link to comment Share on other sites More sharing options...
Prince Posted September 21, 2007 Share Posted September 21, 2007 Boas...Ainda relativamente a isto: alguém me pode explicar porque os dvdrips não aparecem com resolução 720 x 576, uma vez que até são múltiplos de 16, e estariam dentro das regras?Fiquem Link to comment Share on other sites More sharing options...
iNSPiRE Posted September 21, 2007 Share Posted September 21, 2007 Boas...Ainda relativamente a isto: alguém me pode explicar porque os dvdrips não aparecem com resolução 720 x 576, uma vez que até são múltiplos de 16, e estariam dentro das regras?Fiquemporque um width acima de 640 provoca um bitrate de video baixo demais que, por sua vez, resulta em pior qualidade de imagem (para 700 MBs) Link to comment Share on other sites More sharing options...
Luke Posted September 21, 2007 Author Share Posted September 21, 2007 Pois :- Parece que ha regras mais actuais The DVDr scene rules 2007 The Game-Rip scene rules 2004 The XViD scene rules 2005 (Rebuttal) The x264 scene rules 2007 v2 The 0day-UTiL scene rules 2002 The MDVDr scene rules 2007 The TV x264 scene rules 2007 The PDA Trainer scene rules 2005 The MViD scene rules 2006 Better ??? Mas se quiserem mais basta ir ao Google e por scene rules :kiss: Luke Link to comment Share on other sites More sharing options...
Prince Posted September 21, 2007 Share Posted September 21, 2007 (edited) Boas...porque um width acima de 640 provoca um bitrate de video baixo demais que, por sua vez, resulta em pior qualidade de imagem (para 700 MBs)Thanks Dark...agora entendi....é pena... rips com resolução de dvd's seriam muito bons ;)Fiquem!Luke: Parece que ha regras mais actuais, mas o que conta é a boa intenção k tiveste, certo ? ;)Fiquem! Edited September 21, 2007 by Prince Link to comment Share on other sites More sharing options...
gosma25 Posted September 22, 2007 Share Posted September 22, 2007 Quem não tiver nada de útil a acrescentar fica melhor é caladinho... Link to comment Share on other sites More sharing options...
Bollycao Posted September 22, 2007 Share Posted September 22, 2007 Boas...porque um width acima de 640 provoca um bitrate de video baixo demais que, por sua vez, resulta em pior qualidade de imagem (para 700 MBs)Thanks Dark...agora entendi....é pena... rips com resolução de dvd's seriam muito bons ;)Fiquem!o que não falta por aí são rips com a resolução do DVD, só que não saem na 'scene' nem tão pouco são postados nas news. são as chamadas releases AFR's que, consoante o filme, vêm num ficheiro .avi de 1.45 GB (1/4 DVD), 2.18 GB (1/2) ou mais raramente 2.9 (2/3) . Tens é que utilizar outras vias (nomeadamente o emule)...tens aqui um exemplo ;) Link to comment Share on other sites More sharing options...
brook Posted September 22, 2007 Share Posted September 22, 2007 ..rips com resolução de dvd's seriam muito bonsÉ a lógica da batata. É impossivel garantir um DVDRip com uma resolução dessas mantendo a mesma relação qualidade / tamanho, devido à regra do tamanho: é obrigatório manter o máximo de 700MB, e, por causa disso, não fazia sentido baixar o bit rate só para aumentar a resolução. Caso isso acontecesse o resultado final ia ser muito pior. Como disso o Bollycao, há certas versões com essa resolução, mas ao excederem o tamanho máximo permitido, não "contam". As versões que podem garantir uma resolução, e que se encontram dentro das regras são as HDRip (x264), mas essas já não têm como fonte original um DVD, mas sim um Blu-Ray / HD-DVD. Link to comment Share on other sites More sharing options...
Evil_Djinn Posted September 22, 2007 Share Posted September 22, 2007 Melhor que saber as regras era saber os FTPS onde sacar as releases :- Link to comment Share on other sites More sharing options...
iNSPiRE Posted September 22, 2007 Share Posted September 22, 2007 Melhor que saber as regras era saber os FTPS onde sacar as releases :-:clap: leecher alert! Link to comment Share on other sites More sharing options...
wazzuup Posted September 22, 2007 Share Posted September 22, 2007 não sabia destas novas do x264, obrigado Link to comment Share on other sites More sharing options...
Golden_Ace Posted September 22, 2007 Share Posted September 22, 2007 N se admirem que daqui a algum tempo saiam regras para HD-DVD e Blue-ray... Já se começam a ver nos hiper... e, como é normal, nos países mais desenvolvidos já se começa a tratar desse assunto. Boa iniciativa Luke. N conhecia a nova bíblia, apenas a versão q colocaste inicialmente. Link to comment Share on other sites More sharing options...
KilL_MaSTeR Posted September 22, 2007 Share Posted September 22, 2007 Nota: No primeiro post do luke deve ler-se Proper e não Propper Link to comment Share on other sites More sharing options...
wazzuup Posted September 23, 2007 Share Posted September 23, 2007 N se admirem que daqui a algum tempo saiam regras para HD-DVD e Blue-ray... Já se começam a ver nos hiper... e, como é normal, nos países mais desenvolvidos já se começa a tratar desse assunto. Boa iniciativa Luke. N conhecia a nova bíblia, apenas a versão q colocaste inicialmente. :lol: Link to comment Share on other sites More sharing options...
Golden_Ace Posted September 23, 2007 Share Posted September 23, 2007 N se admirem que daqui a algum tempo saiam regras para HD-DVD e Blue-ray... Já se começam a ver nos hiper... e, como é normal, nos países mais desenvolvidos já se começa a tratar desse assunto. Boa iniciativa Luke. N conhecia a nova bíblia, apenas a versão q colocaste inicialmente. :lol: Ou pensas q os gravadores chegam cá assim q saem? Era bom, era. Fora que lá n apanhas com os preços exorbitantes q te pedem cá. Portugal n é propriamente o centro das tecnologias. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now