2,301 (edited by sarami 2019-12-08 16:49:50)

user7 wrote:

I have redumped yet another one, https://drive.google.com/file/d/1oq0uz4 … sp=sharing

iso size is full disc, but data should only be about 34gb

Detected Anchor Volume Descriptor Pointer: LBA 22024943

Last sector is 22024944.
Iso size is 22024944 * 2048 = 45107085312

    <rom name="ps4 idu 2018 summer refresh gamestop.iso" size="45107085312" crc="f43ae860" md5="1dcd29f7b5a4704a724d01aebf7fa685" sha1="27004b46ac4049e44b9f977177aa63b501a7fb5f" />

size matches.

2,302

Sure, I understand that, but that's about 10GB of unused data in the disc image. Does that seem right?

All my posts and submission data are released into Public Domain / CC0.

2,303

user7 wrote:

but that's about 10GB of unused data in the disc image.

Zero padding? I don't know. Anyway, the last 16 sectors are used as several descriptors.

Questions.
1. How many sizes are displayed in the property of drive when the disc is inserted?
2. How many sizes are displayed when used Isobuster?

2,304 (edited by user7 2019-12-09 03:11:44)

Sorry, I got confused. This is the entry for the isobuster dump: http://redump.org/disc/64427/

Size is much closer.

If you believe the dic dump is correct, I will ask Enker to update.

All my posts and submission data are released into Public Domain / CC0.

2,305

user7 wrote:

Size is much closer.

isobuster dump is bigger by 16 sectors.
Please upload the last 16 sectors of isobuster dump.

2,306 (edited by user7 2019-12-10 03:44:14)

How do I extract certain sectors? Thanks.

All my posts and submission data are released into Public Domain / CC0.

2,307

1. Use Isobuster if you've registered it.
2. Use Binary Editor.

2,308 (edited by user7 2019-12-10 15:51:52)

The additional sectors are just 0's.

All my posts and submission data are released into Public Domain / CC0.

2,309

user7 wrote:

The additional sectors are just 0's.

I doubt it's isobuster's bug. You can report it to isobuster's author if you want.

2,310 (edited by user7 2019-12-10 17:26:21)

Even in the dic dump there are some 0's at the end. Isobusters just go for longer.

Submit the dic dump?

All my posts and submission data are released into Public Domain / CC0.

2,311

sarami, could you please change the order of cuesheet tags:

http://forum.redump.org/post/75216/#p75216

to this:

CATALOG
TITLE
PERFORMER
SONGWRITER

REM SESSION
REM LEAD-IN
REM PREGAP

REM SINGLE-DENSITY AREA
REM HIGH-DENSITY AREA

FILE
TRACK
TITLE
PERFORMER
SONGWRITER
ISRC
FLAGS
INDEX

REM LEAD-OUT

PX-760A (+30), PX-W4824TA (+98), GSA-H42L (+667), GDR-8164B (+102), SH-D162D (+6), SOHD-167T (+12)

2,312

user7 wrote:

Even in the dic dump there are some 0's at the end.

Are there some 0's in your dump?

iR0b0t wrote:

sarami, could you please change the order of cuesheet tags:

OK, but I want to know too the cuesheet of Isobuster and CloneCD.

2,313

sarami wrote:

Are there some 0's in your dump?

Yes, both dic and isobuster. isobuster has additional 0's though.

All my posts and submission data are released into Public Domain / CC0.

2,314

There are 2 types in your bd-r dumps.

1. Only ISO9660 --- PS4 IDU 2015 Summer Refresh Standard
2. Only UDF --- ps4 idu 2018 summer refresh gamestop, 2019 Summer Refresh - Game 89

1 uses "Volume Space Size". If the last sector is all zero, it's no problem. Perhaps DIC and Isobuster match.
2 uses "Anchor Volume Descriptor Pointer". This sector is non-zero. Isobuster overdumps by 16 sectors? I'm not sure yet.

If you have ISO9660 + UDF hybrid bd-r, please upload logs and tell me the last sector.

2,315

Regarding the dic logs for the disc we're discussing: https://drive.google.com/file/d/1oq0uz4 … xyYF5/view

>If you have ISO9660 + UDF hybrid bd-r, please upload logs and tell me the last sector.

Both dic and isobuster dumps end in 0's

Here are the final bytes from the DIC dump https://mega.nz/#!cvAHDYJZ!2ofFgyO2YJOh … ToQR34tBKQ


Thanks smile

All my posts and submission data are released into Public Domain / CC0.

2,316

user7 wrote:

Here are the final bytes from the DIC dump https://mega.nz/#!cvAHDYJZ!2ofFgyO2YJOh … ToQR34tBKQ

This is certain "Anchor Volume Descriptor Pointer". This is the last sector.

2,317

https://mega.nz/#!a9pDAK6R!lic1WG0clvNK … VWKbX13RpQ

    TITLE "Track 1 (CD Text in Japanese only)"
    PERFORMER "Artist CD Text in Japanese only"

Are these strings really encoded as CD Text? Not replaced by DIC?

2,318

F1ReB4LL wrote:

https://mega.nz/#!a9pDAK6R!lic1WG0clvNK … VWKbX13RpQ

    TITLE "Track 1 (CD Text in Japanese only)"
    PERFORMER "Artist CD Text in Japanese only"

Are these strings really encoded as CD Text? Not replaced by DIC?

Reference https://www.gnu.org/software/libcdio/cd … ormat.html
There are 2 language codes in this disc.

This is the raw format written in ccd (If you see readable format, see _disc.txt)

[CDText]
Entries=21
Entry 0=80 00 00 80 00 00 82 63 82 62 00 00 00 00 00 00
Entry 1=81 00 01 80 00 00 82 63 82 92 82 81 82 8d 82 81
Entry 2=81 01 02 85 82 62 82 63 00 00 00 00 00 00 00 00
Entry 3=8f 00 03 80 00 01 01 00 01 02 00 00 00 00 00 00
Entry 4=8f 01 04 80 00 00 00 00 00 00 00 03 05 0e 00 00
Entry 5=8f 02 05 80 00 00 00 00 69 09 00 00 00 00 00 00
Entry 6=80 00 00 10 54 69 74 6c 65 20 43 44 20 54 65 78
Entry 7=80 00 01 1c 74 20 69 6e 20 4a 61 70 61 6e 65 73
Entry 8=80 00 02 1f 65 20 6f 6e 6c 79 00 54 72 61 63 6b
Entry 9=80 01 03 15 20 31 20 28 43 44 20 54 65 78 74 20
Entry 10=80 01 04 1f 69 6e 20 4a 61 70 61 6e 65 73 65 20
Entry 11=80 01 05 1f 6f 6e 6c 79 29 00 00 00 00 00 00 00
Entry 12=81 00 06 10 41 72 74 69 73 74 20 43 44 20 54 65
Entry 13=81 00 07 1c 78 74 20 69 6e 20 4a 61 70 61 6e 65
Entry 14=81 00 08 1f 73 65 20 6f 6e 6c 79 00 41 72 74 69
Entry 15=81 01 09 14 73 74 20 43 44 20 54 65 78 74 20 69
Entry 16=81 01 0a 1f 6e 20 4a 61 70 61 6e 65 73 65 20 6f
Entry 17=81 01 0b 1f 6e 6c 79 00 00 00 00 00 00 00 00 00
Entry 18=8f 00 0c 10 80 01 01 00 06 06 00 00 00 00 00 00
Entry 19=8f 01 0d 10 00 00 00 00 00 00 00 03 05 0e 00 00
Entry 20=8f 02 0e 10 00 00 00 00 69 09 00 00 00 00 00 00

From Entry 0 to 5 are 1st language code.
[Entry 0]
1st byte shows Album.
5th byte is 0 => Album Name is null.
From 7th to 10th are "82 63 82 62". => Song Name is "DC"

[Entry 1, 2]
1st byte shows Performer.
5th byte is 0 => Album Performer is null.
From 7th to 16th of entry 1 are "82 63 82 92 82 81 82 8d 82 81" => "Drama"
From 5th to 8th of entry 2 are "82 62 82 63" => "CD"
  => These are concatenated as "DramaCD"


From Entry 6 to 20 are 2nd language code.
[Entry 6, 7, 8]
1st byte shows Album.
From 5th to 16th of entry 6 are "54 69 74 6c 65 20 43 44 20 54 65 78" => "Title CD Tex"
From 5th to 16th of entry 7 are "74 20 69 6e 20 4a 61 70 61 6e 65 73" => "t in Japanes"
From 5th to 10th of entry 8 are "65 20 6f 6e 6c 79"                   => "e only"
  => These are concatenated as "Title CD Text in Japanese only"

[Entry 8, 9, 10, 11]
From 12th to 16th of entry 8 are "54 72 61 63 6b" => "Track"
From 5th to 16th of entry 9 are "20 31 20 28 43 44 20 54 65 78 74 20" => " 1 (CD Text "
From 5th to 16th of entry 10 are "69 6e 20 4a 61 70 61 6e 65 73 65 20" => "in Japanese "
From 5th to 9th of entry 11 are "6f 6e 6c 79 29" => "only)"
  => These are concatenated as "Track 1 (CD Text in Japanese only)"

[Entry 12, 13, 14]
1st byte shows Performer.
From 5th to 16th of entry 12 are "41 72 74 69 73 74 20 43 44 20 54 65" => "Artist CD Te"
From 5th to 16th of entry 13 are "78 74 20 69 6e 20 4a 61 70 61 6e 65" => "xt in Japane"
From 5th to 11th of entry 14 are "73 65 20 6f 6e 6c 79" => "se only"
  => These are concatenated as "Artist CD Text in Japanese only"

[Entry 14, 15, 16, 17]
From 13th to 16th of entry 14 are "41 72 74 69" => "Arti"
From 5th to 16th of entry 15 are "73 74 20 43 44 20 54 65 78 74 20 69" => "st CD Text i"
From 5th to 16th of entry 16 are "73 65 20 6f 6e 6c 79 00 41 72 74 69" => "n Japanese o"
From 5th to 7th of entry 17 are "6e 6c 79" => "nly"
  => These are concatenated as "Artist CD Text in Japanese only"


One problem exists. Cue format handles only 1 language code. DIC outputs one-byte-character language.

2,319

sarami wrote:

This is certain "Anchor Volume Descriptor Pointer". This is the last sector.

So dic dump is confirmed good? If so I will submit a fix. Thanks.

All my posts and submission data are released into Public Domain / CC0.

2,320

sarami wrote:
iR0b0t wrote:

sarami, could you please change the order of cuesheet tags:

OK, but I want to know too the cuesheet of Isobuster and CloneCD.

Isobuster uses cdt and doesn't use TITLE, PERFORMER, etc.
CloneCD doesn't use cdt and TITLE, PERFORMER, etc.

I'll change the order of cuesheet tags in the near future.

user7 wrote:

So dic dump is confirmed good?

I think so.

2,321

http://www.mediafire.com/file/eq80y20l9 … st.7z/file

iR0b0t wrote:

sarami, could you please change the order of cuesheet tags:

- fixed: cuesheet order

sarami wrote:

One problem exists. Cue format handles only 1 language code. DIC outputs one-byte-character language.

- added: output the 2nd language code of CDTEXT to _alt.cue

2,322

hey sarami i have a problem dumping a disc it stop with this error

https://i.imgur.com/uPCJViv.jpg

logs https://gofile.io/?c=XI2K6a

2,323

xTMODx wrote:

i have a problem dumping a disc it stop with this error

Try other app (isobuster, clonecd, etc.)

2,324 (edited by xTMODx 2019-12-15 19:35:42)

sarami wrote:
xTMODx wrote:

i have a problem dumping a disc it stop with this error

Try other app (isobuster, clonecd, etc.)

Disc has 5 tracks and also a ring on the data side, isobuster dump takes very long dont know if i have to cancel this

it is this disc https://www.ebay.de/itm/Kommissar-Kugel … 3181902862

but i have this cover https://www.ebay.de/itm/Kommissar-Kugel … 4109801439 but they dont ship outside germany

2,325

xTMODx wrote:

Disc has 5 tracks and also a ring on the data side, isobuster dump takes very long dont know if i have to cancel this

According to the log, LBA 115010 is not a data sector. Do you dump only track 1 by Isobuster?