Sony PlayStation 3 Moderation Guide

From Redump Wiki

(Difference between revisions)
Jump to: navigation, search
(Fields)
(Fields)
(One intermediate revision not shown)
Line 13: Line 13:
'''Internal Serial'''
'''Internal Serial'''
:Internal Serial for PS3 is taken exactly as contained in the PS3_DISC.SFB file at the base of the disc and is usually something like "BLES-02156" which would go into a submission as [T:ISN] BLES-02156.
:Internal Serial for PS3 is taken exactly as contained in the PS3_DISC.SFB file at the base of the disc and is usually something like "BLES-02156" which would go into a submission as [T:ISN] BLES-02156.
-
:Usually, the PARAM.SFO serial matches this, but there are occasions where it either differs, or where the disc is a compilation disc and each game within carries its own separate internal serial inside PARAM.SFO. In these cases, the main Internal Serial will be taken from PS3_DISC.SFB, but the additional internal serials can be specified in the comments.
+
:Usually, the PARAM.SFO serial matches this (except there is no hyphen in the PARAM.SFO serial), but there are occasions where it either differs, or where the disc is a compilation disc and each game within carries its own separate internal serial inside PARAM.SFO. In these cases, the main Internal Serial will be taken from PS3_DISC.SFB, but the additional internal serials can be specified in the comments.
-
:Historically, the internal serial was taken from PARAM.SFO, so there may be entries in redump that need updating over time.
+
:Historically, the internal serial was taken from PARAM.SFO, so there may be entries in redump that need updating over time.  These should be relatively obvious as the internal serials taken from PARAM.SFO have no hyphen in them.
'''Version'''
'''Version'''

Revision as of 12:48, 29 January 2024

Contents

Ringcodes

In general, the rule for adding a new line to the ringcodes field is that this should only be done when a new mastering code or mastering SID is present. For PS3, however, there are two exceptions to that rule:

Australia / Europe

Australian releases often share the same mastering code and SID as their European counterparts, but have a unique pattern for mould SID and toolstamp which differentiates them. Where an Australian disc has a toolstamp A00, B00, C00 etc. and/or a mould SID of the pattern IFPI 65xx (compared to the usual IFPI 94xx for EU releases), then this should be added as a separate line.

See http://redump.org/disc/31402/ for an example

Fields

Internal Serial

Internal Serial for PS3 is taken exactly as contained in the PS3_DISC.SFB file at the base of the disc and is usually something like "BLES-02156" which would go into a submission as [T:ISN] BLES-02156.
Usually, the PARAM.SFO serial matches this (except there is no hyphen in the PARAM.SFO serial), but there are occasions where it either differs, or where the disc is a compilation disc and each game within carries its own separate internal serial inside PARAM.SFO. In these cases, the main Internal Serial will be taken from PS3_DISC.SFB, but the additional internal serials can be specified in the comments.
Historically, the internal serial was taken from PARAM.SFO, so there may be entries in redump that need updating over time. These should be relatively obvious as the internal serials taken from PARAM.SFO have no hyphen in them.

Version

Version numbers are taken primarily from PS3_DISC.SFB (for multi-game / compilation discs), and secondarily from PARAM.SFO if not in the SFB file (most single-game discs).
Version numbers are entered for PS3 exactly as listed, including the 0 which is often at the beginning.
For example, if it is "VERSION: 01.01", then 01.01 is entered in redump for the version (not 1.01).
When two different numbered versions of a given disc exist, both entries get the version number placed into the datname. This also applies to v1.00 discs.
If viewing the PARAM.SFO manually, this will be the last element of the file, toward the very end. CAUTION: there are two different version elements in the file. Use the last one, not the earlier one.
If you don't have PARAM.SFO file and the game was dumped with MPF & DIC, you can typically get this information from the bottom of the *_disc.txt file from logs. It will look like "VERSION: 01.01" and is the version after/under the TITLE ID as presented in the log (please note, this may not be accurate for multi-game / compilation discs).

Volume Label

Many PS3 discs have a generic volume label such as "PS3VOLUME" and those are typically omitted from redump.
However, if the Volume Label is unique / different from that, it can go in the comments - for example, [T:VOL] ACIII (Assassin's Creed III example).

Disc ID

Generally, the Disc ID goes into the "Disc ID" field in the Extras section, and many times the Disc ID's are common across discs. However, different regions and/or some verifications can have a separate Disc ID that is also valid. These go in the comments - for example: Additional Disc ID: 00000000000000FF00020001XXXXXXXX
There isn't a specific rule on which ones goes into the main Disc ID field - usually it is the first one dumped.

Version (datfile)

Standard

For rereleases, if there is another difference suitable to maintain filename separation (e.g. different languages between original and rerelease), no datfile version is required.

If there is no other difference and this would result in a duplicate filename, there are two potential scenarios:

  • Same game, different edition, different version, no languages listed -- use the serial number as the datfile version
  • Same game, different edition, different version, same languages listed -- use the version (e.g. v01.01) as the datfile version

Worked examples

http://redump.org/disc/67446/ and http://redump.org/disc/98611/, as they have no languages listed, would both end up with a datfile name of "Bioshock (Japan)", resulting in a duplicate filename.

In this case, as neither has any languages listed, we follow the logic in the first bullet point above and these become "Bioshock (Japan) (BLJS-10041)" and "Bioshock (Japan) (BLJS-10189)" respectively.

http://redump.org/disc/8998/ and http://redump.org/disc/52546/ have a similar problem, although in this case both have the same languages listed so we differentiate here by version, giving us "inFamous (USA) (En,Fr,Es) (v01.00)" and "inFamous (USA) (En,Fr,Es) (v02.00)" respectively.

Misc notes

BD-Rs may need to be dumped with /avdp flag to report proper size in DIC, needs confirmation. -- http://forum.redump.org/post/101468/#p101468

BD-R PICs need to be added to comment field as the length is longer than standard PICs and gets cut off by the site.

Personal tools