https://github.com/saramibreak/DiscImag … r/releases
*2019-12-23
- added: output cue file if 2nd language code of CDTEXT exists
- changed: ISRC position of cue file
- fixed: fail to XBOX/XBOX 360 dumping from 2019-11-16
- fixed: main channel buffering (ROM^2 Karaoke Volume 5 [PCE])
- improved: UDF logging => support detecting the size of DVD-RE, BD-R, BD-RE
451 2019-12-23 14:30:46
Re: DiscImageCreator (3,493 replies, posted in General discussion)
452 2019-12-22 07:06:40
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Which is correct?
Perhaps it's IsoBuster.
dic: doesn't match db (1 error)
No C2 error, no sub error. I have no idea about it.
453 2019-12-21 15:18:46
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Still doesn't work
Fixed UDF http://www.mediafire.com/file/eq80y20l9 … st.7z/file
454 2019-12-20 05:23:42
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Xbox 360 DVD dumping is broken
Fixed http://www.mediafire.com/file/eq80y20l9 … st.7z/file
Track 3 didnt start dumping
Track 4 didnt start dumping
Track 5 didnt start dumping
Weird. TOC is hacked? I don't know...
455 2019-12-16 14:13:21
Re: DiscImageCreator (3,493 replies, posted in General discussion)
when i try dump only track 1 with isobuster it stops at sector 97208 (93%) with Error: 03/11/05
Then, do you dump only track 2, 3, 4 and 5 by Isobuster?
456 2019-12-16 02:59:56
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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?
457 2019-12-15 17:11:22
Re: DiscImageCreator (3,493 replies, posted in General discussion)
i have a problem dumping a disc it stop with this error
Try other app (isobuster, clonecd, etc.)
458 2019-12-14 18:43:14
Re: DiscImageCreator (3,493 replies, posted in General discussion)
http://www.mediafire.com/file/eq80y20l9 … st.7z/file
sarami, could you please change the order of cuesheet tags:
- fixed: cuesheet order
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
459 2019-12-12 17:45:10
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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.
So dic dump is confirmed good?
I think so.
460 2019-12-11 16:06:10
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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.
461 2019-12-11 08:23:22
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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.
462 2019-12-11 04:41:53
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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.
463 2019-12-11 00:59:46
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Even in the dic dump there are some 0's at the end.
Are there some 0's in your dump?
sarami, could you please change the order of cuesheet tags:
OK, but I want to know too the cuesheet of Isobuster and CloneCD.
464 2019-12-10 16:10:35
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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.
465 2019-12-10 12:31:55
Re: DiscImageCreator (3,493 replies, posted in General discussion)
1. Use Isobuster if you've registered it.
2. Use Binary Editor.
466 2019-12-09 05:36:21
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Size is much closer.
isobuster dump is bigger by 16 sectors.
Please upload the last 16 sectors of isobuster dump.
467 2019-12-09 02:42:42
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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?
468 2019-12-08 16:49:15
Re: DiscImageCreator (3,493 replies, posted in General discussion)
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.
469 2019-12-07 16:51:38
Re: DiscImageCreator (3,493 replies, posted in General discussion)
ROM^2 Karaoke Volume 5 (Japan)_2.rar
Uploaded http://www.mediafire.com/file/eq80y20l9 … st.7z/file
EDIT:
Re-uploaded due to removing the debug log
470 2019-12-07 08:33:28
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Yes. How about Isobuster size?
471 2019-12-06 09:49:03
Re: DiscImageCreator (3,493 replies, posted in General discussion)
It looks like no UDF disc.
http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: Use "Volume Space Size" if there is not UDF (when disc is BDR, BDRW, DVDRW).
472 2019-12-06 02:08:16
Re: DiscImageCreator (3,493 replies, posted in General discussion)
It's written in "Logical Volume Integrity Descriptor"
========== LBA[000273, 0x00111]: Logical Volume Integrity Descriptor ==========
Minimum UDF Read Revision: 0x250
Minimum UDF Write Revision: 0x260
Maximum UDF Write Revision: 0x260
473 2019-12-05 02:30:17
Re: DiscImageCreator (3,493 replies, posted in General discussion)
http://redump.org/disc/66810/ - why was the 2nd track misdetected as audio? Marked as data in the subs as usual, TOC in disc.txt also says the track type is Data.
Try to use latest test version.
474 2019-12-04 10:02:10
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Your disc is UDF 2.50
UDF 2.50 says
NOTE: An AnchorVolumeDescriptorPointer structure shall be recorded in at
least 2 of the following 3 locations on the media:
• Logical Sector 256.
• Logical Sector (N - 256).
• N
N is last sector.
_disc.txt
Detected Anchor Volume Descriptor Pointer: LBA 16669398
Perhaps, last LBA is 16669398 (size is 34138929152).
475 2019-12-03 07:51:15
Re: DiscImageCreator (3,493 replies, posted in General discussion)
Thank you, I've redumped with updated firmware and new DIC as well as IsoBuster https://drive.google.com/file/d/15PSYB6 … sp=sharing
dic size: 34,139,484,160 bytes
isobuster: 34,138,947,584 bytes (same size as before)
http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- added: Detect Anchor Volume Descriptor Pointer