Redump Forum

sarami wrote:

F1ReB4LL wrote:Yes, it's an ISRC sector. https://redump.info/disc/28248/ -- for this disc it gives me ISRCs for the first 6 tracks only.

I got Valis II (FFTHTJ10529-3FFTH   Z5W8). But this disc don't exist ISRC sector. Please wait..

Do the tracks match my dump? I can give you a .sub, so you could burn it and dump with your tool to check the decoding.

F1ReB4LL wrote:Do the tracks match my dump? I can give you a .sub, so you could burn it and dump with your tool to check the decoding.

Tracks match your dump except track 1.
uploads cue, log, sub
http://www.mediafire.com/download/639b2 … ValisII.7z

sarami wrote:Tracks match your dump except track 1.

Yours matches TruRip dump, compared with mine - 2 bytes difference (0x00 in 2 places in your dump, 0xFF in mine, the rest is the same), so they are different dumps and different masters.

When device open fail error occurs, this is all I get.
There is no log

Nexy wrote:When device open fail error occurs, this is all I get.

Code: Select all

DiscImageCreator BuildDate:[Apr  7 2013 14:53:45]
OS
        MajorVersion: 6, MinorVersion: 1, BuildNumber: 7601
Start -> 2013-06-09(Sun) 23:30:04
Device Open fail
End -> 2013-06-09(Sun) 23:30:05

There is no log

Thx. Additionally, please tell me the all command arguments when an error occurs.

This is the command I'm using from .bat

I think the problem is exclusive access is needed, IsoBuster was open but not doing anything. It worked again after I closed IsoBuster.

Upload 20130619 ver.

F1ReB4LL wrote:"03 00 00 00 00 00 00 00 00" should be decoded as "ISRC 000000000000" and you just skip those, it's wrong.

added "isrc" argument.
Generally, "ISRC 000000000000" or "0001Q0000000" is invalid. (https://isrc.jmd.ne.jp/about/error.html) But ISRC of track1-6 is valid in case of Valis II. So supported.

You could check the bad sectors in cdmage to see if they contain the 0x55 pattern?
If not, then changing those sectors to 0x55 should match up Nexy's dump if it's the same.

Question.
Should bad sector be padding in 0x55 pattern (for SafeDisc)? If app can't read sector, it is padding a sector in 0x00 at the present.

In plextor it is dumping bad sectors as audio and they seem to match every time.  Don't know if data is correct or not, but I assume so...

for non plextor yeah 55 like clonecd and ddump. or maybe a switch to specify.

Anyone tried a PX-116A2? I can't seem to get it working with DIC