Search options (Page 48 of 61)

Nexy, also different models?

>>> 4) If your drives don't support over-reading you should dump the audio tracks once with over-read enabled and once with over-read disabled. If your dumping results are equal after that, then your dump should be okay. Best, you use two different drives with different read offsets, though!

Please post both EAC dumping logs (over-reading on / off) even if they seem to match.

To be honest the logs are a little bit confusing.

Not sure what to believe.

If perfectrip dump reports a 2:00 audio pregap and cdmage reports an error on the last sector, this seems okay to me. But looking at your other isobuster log from the same PX-716A drive, it shows no ECC data on the as last calculated data track sector, which should actually be the pre-last one according to perfectrip log.

146824 should be the first audio frame if you tick it in isobuster
going back 150 frames would lead you to 146674, not 673.

Might be a TOC vs. SUB desync.

LG drives are pretty good, for dumping data only discs at least.

There are 2 dumps with audio tracks and 1 without in the database by now. Blue Shift is SecuROM protected, and this protection includes one MODE2 sector which is in the very end of the data track. Your drive might have an issue extracting different DATA MODE TYPES inside of a single track. So yeah, try an other drive ))

Version 0.10 might be a demo.

Parent/Child relationship can be between the 1st master and remasters (re-releases) of the "same" title and region.

What you are talking of is "grouping" of discs with similar contents

Using a "cloneof"-attribute in this case sounds wrong IMHO, but if this is the way clrmamepro works to group similar items then its fine i guess ))

There is no value for layer breaks stored on the disc, just layer length for the first layer, and layer break is calculated by that, layer0's length + 1. Isobuster creator probably just forgot to add an extra digit, it happens sometimes ))

Should be fixed within the next release i guess, if somebody will be pointing him out to that fact.

http://forum.redump.org/topic/2620/drea … tructions/
it has been discussed here, please read you through and you will find your answer ))

To make it short:
SD card method can be used on titles with 3 tracks. The 2nd track has to be dumped on an ordinary cd-rom drive with offset correction, preferably with over-reading into lead-in, for that please read the cd-rom dumping guide.

track length is miscalculated and perfectrip throws an error because it detects different track modes in the second track. there might be audio silence in-between both data tracks as well.

I began to work on a "pakkman" tool, which was supposed to manage updates from older datfile to the new one, with full image names instead of generic once.

>> pakkiso - for compression purposes only.
>> pakkman - file manager, the idea was/is:
1. to sort out all not matching titles.
2. after comparing the hashes renaming them without(!) a decompression, which works already fine here.
3. for titles where hashes changed or are not matching try an auto-fix, this is the most complicated part, as it has to be done in the proper order, but it is to manage 
4. if the first three steps failed, delete or move those to a storage folder.
5. create a log file with all the changes!

that's it! 
i hope to finish it someday