Redump Forum — how custom Disc number field is meant to be?

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Sat, 22 Aug 2009 18:05:56 +0000

Third: it's quite obvious I mistook title and that I've said the same about US release but that disc 2 is not a game disc (or it's a game disc?)

Re: how custom Disc number field is meant to be?

null@example.com (iR0b0t) — Sat, 22 Aug 2009 15:42:55 +0000

First: The game is titled "God of War II"

Second: US version was released in 2-Discs-Pack, both discs are numbered

Re: how custom Disc number field is meant to be?

null@example.com (F1ReB4LL) — Sat, 22 Aug 2009 15:07:35 +0000

I don't know about God of Wars II, but all the Saturn CDs have their CD/volume numbers in the header (except the audio and non-Saturn bonus ones). I don't like a standalone game cd entry, if it has "CD-1/2" in the header.

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Sat, 22 Aug 2009 14:45:16 +0000

I was not contradicting if you read well, I said we have to find a standard for those discs (however all info has to be in DB).
In my opinion Disc 1,2,3 etc. should be added only for game discs, all bonus discs should be set apart even if they are labelled as Disc # or have CDn/n in header.
I give you another example: God of Wars II (USA) (Disc 1) (Disc 2) ---> Disc 2 is not a game disc and Euro release doesn't have it (probably also Jap, I have to open it to see), it can confuse people.

Re: how custom Disc number field is meant to be?

null@example.com (F1ReB4LL) — Sat, 22 Aug 2009 14:13:03 +0000

Rocknroms wrote:

F1ReB4LL wrote:
I'd vote for Disc A, Disc B, etc., but only when it's needed. If it's written on the CD - why not?
I agree if we have this situation:
Disc 1 ---> "Install Disc"
Disc 2 ---> "Disc A"
Disc 3 ---> "Disc B"
if they are only "Disc A" & "Disc B" it's good as themabus did adding it in the comment.

IMO, CDs should be named either by header or by CD labels. Disc A, Disc B - by CD labels. You're basically offer to name them according to the header here, ok, but:

Rocknroms wrote:

Moreover I would like to split game disc with bonus or omake that are labelled as disc #, this could be added in notes, for example:
Sengoku Blade: Sengoku Ace Episode II (Japan) (Disc 1) ---> Sengoku Blade: Sengoku Ace Episode II (Japan)
Sengoku Blade: Sengoku Ace Episode II (Omake CD) (Japan) (Disc 2) ---> Sengoku Blade: Sengoku Ace Episode II (Omake CD) (Japan)

You contradict yourself here. This Omake CD has "CD2/2" in the header, so it acts as a 2nd CD.

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Sat, 22 Aug 2009 13:55:54 +0000

r09 wrote:

By the way, I think there's something wrong with the naming of the discs in the PC USA version of Final Fantasy VII. "Disc 1" is actually the install disc, and discs 2, 3 and 4 should be 1, 2 and 3, respectively.

This is one of the situation I said above, it could be renamed like this:

Final Fantasy VII (Install Disc)
Final Fantasy VII (Disc 1)
Final Fantasy VII (Disc 2)
Final Fantasy VII (Disc 3)

By the way we have to write down some standards to avoid future discussions about these matters.

Re: how custom Disc number field is meant to be?

null@example.com (r09) — Sat, 22 Aug 2009 13:28:33 +0000

By the way, I think there's something wrong with the naming of the discs in the PC USA version of Final Fantasy VII. "Disc 1" is actually the install disc, and discs 2, 3 and 4 should be 1, 2 and 3, respectively.

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Sat, 22 Aug 2009 13:13:04 +0000

F1ReB4LL wrote:

I'd vote for Disc A, Disc B, etc., but only when it's needed. If it's written on the CD - why not?

I agree if we have this situation:

Disc 1 ---> "Install Disc"
Disc 2 ---> "Disc A"
Disc 3 ---> "Disc B"

if they are only "Disc A" & "Disc B" it's good as themabus did adding it in the comment.

Moreover I would like to split game disc with bonus or omake that are labelled as disc #, this could be added in notes, for example:

Sengoku Blade: Sengoku Ace Episode II (Japan) (Disc 1) ---> Sengoku Blade: Sengoku Ace Episode II (Japan)

Sengoku Blade: Sengoku Ace Episode II (Omake CD) (Japan) (Disc 2) ---> Sengoku Blade: Sengoku Ace Episode II (Omake CD) (Japan)

This because sometimes they label them with numbers / letters and sometimes not: we have to choose a standard also because sometimes those discs are added wrongly (they may have a number but dumper doesn't care, or the opposite).

At all we need more fields to add infos that stay only in DB and not in dats.

Re: how custom Disc number field is meant to be?

null@example.com (F1ReB4LL) — Sat, 22 Aug 2009 12:58:58 +0000

I'd vote for Disc A, Disc B, etc., but only when it's needed. If it's written on the CD - why not?

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Sat, 22 Aug 2009 12:54:10 +0000

I didn't suggest anything, I simply said that "Disc A", "Disc B", etc. are disc names / not disc numbers and I said that "adding them in the appropriate field will be redundant". So at least I suggest the opposite: - avoide tosec shitness -. It's quite obvious that Disc A is Disc 1 and so on.
Moreover tapes are not discs so you have to label "Side A" and "Side B", this are common names on every old tape.

Re: how custom Disc number field is meant to be?

null@example.com (Dremora) — Sat, 22 Aug 2009 12:23:55 +0000

"Disc 0 of 4" would look quite strange, but as we don't write total discs number to the filename, any custom numbering scheme can be used.

Re: how custom Disc number field is meant to be?

null@example.com (themabus) — Fri, 21 Aug 2009 02:18:04 +0000

in TOSEC it's alike to what Rocknroms suggests:

The TOSEC Naming Convention v1 wrote:

* (Disk/File/Tape x of y Side A/B)
This field is used if the game spans more than one disk, or is comprised of
multiple files. When there are 9 or less disks, the format of (Disk 1 of 3)
is used. If there are 10 or more disks, then the entry needs to change to
(Disk 01 of 13) to maintain consistency. In cases where double sided tapes
or disks are involved, the "Side A/B" entry is also included.
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(File 1 of 2)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(File 2 of 2)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 01 of 11)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 08 of 11)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 10 of 11)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2 Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2 Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 1 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 1 of 2 Side B)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 2 of 2 Side A)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Tape 2 of 2 Side B)"
** NOTE: In cases where multi-file zips are used, the parent's zipname should
reflect the contents of the zip.
The files :
"Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2).bin"
"Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2).bin"
would be included in the zip called:
"Legend of TOSEC, The (1986)(DevStudio)(US)[2 Disks].zip"
* (disk label)
If the disk label is known, this field following the (Disk x of y) entry
should contain it. This is mainly used when save, program, install, or
other custom names might be requested by the game itself. (Disk 2 of 3) is
not useful by itself when the program asks you to "Insert Character Disk".
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 1 of 2)(Program)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2)(Data)"
Ex: "Legend of TOSEC, The (1986)(DevStudio)(US)(Disk 2 of 2)(Disk B)"

but it makes more sense there, since 1st field always denotes medium from a set - it has a different meanig
here it's only a counter: A, B, C or 0, 1, 2 or I, II, III can be a counters too
so in TOSEC also Enemy Zero would be with labels

(Disc 1)(Disc A) and (Disc 1)(Disc 0) overlap, but (Disc 1) does not express this situation fully, imho,
(Disc 1 of 2)(Disc A) would, as would (Disc A) <- not as complete as previous one though, but that's what we got
also it's the same with (Disc 1 of 4)(Disc 0) and (Disc 0), though 1st is more descriptive again, both are fine, imho

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Thu, 20 Aug 2009 19:31:05 +0000

F1ReB4LL wrote:

New dump(s) http://redump.org/rss/recentdumps : [PC CD][NEW] test (Asia) (Disc A) <http://redump.org/disc/8539/>
so looks like it's not only numerical.

So this disc is named wrong (disc name instead of disc number. I meant it's wrong not it's not possible), the field says "disc number" so it refers to progressive numbers.

Re: how custom Disc number field is meant to be?

null@example.com (F1ReB4LL) — Thu, 20 Aug 2009 19:16:14 +0000

New dump(s) http://redump.org/rss/recentdumps : [PC CD][NEW] test (Asia) (Disc A) <http://redump.org/disc/8539/>

so looks like it's not only numerical.

Re: how custom Disc number field is meant to be?

null@example.com (Rocknroms) — Thu, 20 Aug 2009 19:14:16 +0000

Disk number field is not custom, it's only numerical. "Disc A" or "Disc B" are disk names but adding them in the appropriate field will be redundant.
About Enemy Zero it's quite obvious that naming disc in a different way will make confusion (it's the only exception until now).