Re: The Releasing Standards
Re: The Releasing Standards
Re: The Releasing Standards
Quote:
Originally Posted by {I}{K}{E}
http://www.1go.dk/webhotel/404.php
Re: The Releasing Standards
Quote:
Originally Posted by Samurai
copy/paste the link :)
Re: The Releasing Standards
Quote:
Originally Posted by {I}{K}{E}
Quote:
Originally Posted by Samurai
copy/paste the link :)
It doesn't work in Opera. I've uploaded it to ImageShack if you want to replace it so others don't have the same problem... you can credit it to the same site if you want to.
Code:
http://img499.imageshack.us/img499/6963/mp3rules1pj.png
Re: The Releasing Standards
all this is jargon to me. but trying to understand.
Re: The Releasing Standards
have the 2k6 standards not surfaced yet?
Re: The Releasing Standards
Code:
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
b) 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.
Old MViD?
Re: The Releasing Standards
Code:
___ ___ _ ___ _ _ ___ ____ ___ _
___| __| __(_)/ __(_)__ _| | | _ \ _ \ / _ \ _ _ _ _| |___ ___
/ _ \ _|| _|| | (__| / _` | |__ | _/ |_) | _ | '_| || | / -_|_-<
\___/_| |_| |_|\___|_\__,_|____| |_| |____/|_| |_|_| \_,_|_\___/__/
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 :P
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
PDA
Re: The Releasing Standards
Code:
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.
B) 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 B)
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.
scene ripping rules (srr.nfo)
Re: The Releasing Standards
this really doesn't need to be posted at all
Re: The Releasing Standards
