Page 1 of 3
Rhaosody & px_d8 question
Posted: Sat May 08, 2010 9:54 pm
by Specialt1212
I'm having trouble dumping
Rhaosody, I used the following two commands to correct track 1 which matched the database entry
Code: Select all
FPCopy64 -r "track01.bin" -352800
psxt001z.exe --fix "track01.bin"
I used IsoBuster to check the pregap just to make sure that its really 2 seconds and it is, the garbage started 150 sectors back, however the px_d8 log shows msf as 00:02:02. Is the MSF value the pregap because on all the other games I have checked it's listed as 00:02:00?
I can't get track 2 to match even if I add 2 second pregap to track 2.
Code: Select all
C:\z>px_d8.exe e 0
Sector: 0
MSF: 00:02:02
Combined offset: -2468 bytes / -617 samples
Here is the EAC log of track 2 incase you notice anything incorrect in here...
EAC Log
Code: Select all
Exact Audio Copy V0.99 prebeta 4 from 23. January 2008
EAC extraction logfile from 5. May 2010, 21:15
Unknown Artist / Unknown Title
Used drive : PLEXTOR DVDR PX-708A Adapter: 1 ID: 1
Read mode : Secure
Utilize accurate stream : Yes
Defeat audio cache : Yes
Make use of C2 pointers : Yes
Read offset correction : -617
Overread into Lead-In and Lead-Out : Yes
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks : No
Null samples used in CRC calculations : Yes
Used interface : Native Win32 interface for Win NT & 2000
Gap handling : Not detected, thus appended to previous track
Used output format : Microsoft PCM Converter
Sample format : 44.100 kHz, 16 Bit, Stereo
TOC of the extracted CD
Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.00 | 38:15.21 | 0 | 172145
2 | 38:15.21 | 3:07.46 | 172146 | 186216
Track 2
Filename C:\Documents and Settings\Special-T\Desktop\Track02.bin
Peak level 98.8 %
Track quality 100.0 %
Test CRC A912AB5D
Copy CRC A912AB5D
Copy OK
No errors occurred
End of status report
Re: Rhaosody & px_d8 question
Posted: Sat May 08, 2010 10:17 pm
by Rocknroms
MSF has nothing to do with track02 pregap.
Probably your audio track has no pregap (it's 352800 shorter) you have to create a dummy (0x00) 2 sec file and merge it with your track: check "FIXING ANOMALIES" chapter in
SS dumping faq you'll find a package to fix it in 2 secs.
Re: Rhaosody & px_d8 question
Posted: Sat May 08, 2010 10:26 pm
by Specialt1212
Thanks for the quick response,
Is that package included in your post the same thing as generating a 2 second pregap and merging it with the original track 2 to create a new track02good.bin file? See example below.
Code: Select all
psxt001z.exe --gen pregap.bin 352800
copy /b pregap.bin+track02.bin track02good.bin
If it's not the same thing, how would I know when to use the bat files if I'm dumping a new game with the same problem?
Re: Rhaosody & px_d8 question
Posted: Sat May 08, 2010 11:27 pm
by themabus
it could be that some audio data gets cut off along with gap, because of large negative offset.
replacing gap with dummy data isn't 100% safe.
you could take image with IsoBuster on gap sector range and look for 1st byte different from 0x00.
data track image, before gap is removed, might work as well.
Re: Rhaosody & px_d8 question
Posted: Sat May 08, 2010 11:56 pm
by velocity37
Yeah, on negative combined offsets, EAC cuts off data from the beginning of track 2.
In order to combat that, you can dump the track manually in ISOBuster.
For this game specifically, in ISOBuster, right-click extract from-to the 2nd track. First, click the End Address bubble, then subtract 150 from the start LBA. Extract.
Open the resulting file in a hex editor. Insert 2,468 (617*4) bytes of 00 at the beginning, and delete 2,468 bytes from the end.
If you're uncomfortable with hex editors, you can instead:
psxt001z.exe --gen offsetfix.bin 2468
copy /b offsetfix.bin+track02.bin track02good.bin
FPCopy64 -r "track02good.bin" -2468
For other games, there's a couple of precautions to take. Firstly, always calculate the correct number of bytes to shift with offset * 4. The second, and most important, is that if the game has >2 tracks, you have to delete track 3's pregap from the end of the file in addition to some bytes.
The only other precaution I can think of is that ISOBuster will not have error recovery as good as EAC, so if you're going to use this method for a new entry, be sure to dump it a couple of times (preferably in a couple of drives, too).
Re: Rhaosody & px_d8 question
Posted: Sun May 09, 2010 7:03 am
by Rocknroms
Yes Specialt1212, the command is the same. By the way as themabus said you may have some data cut off.
As you have a plextor simply dump it with PerfectRip.
Velocity, Isobuster extracts audio data in unscrambled mode or in wav format, you will get a bad track with your method.
Re: Rhaosody & px_d8 question
Posted: Sun May 09, 2010 1:55 pm
by velocity37
Rocknroms wrote:Velocity, Isobuster extracts audio data in unscrambled mode or in wav format, you will get a bad track with your method.
Not if you use "Extract RAW", which is what "Extract From-To" uses by default.
I have matched dozens of -647 offset tracks from ISOBuster with EAC rips from my GH20NS15 (+667). If this were the case, EAC would also have to give bad data.
Renegade Racers, Track 2 EAC GH20NS15:
Code: Select all
Track 2
Filename C:\!Redump\NotSubmitted\RenegadeRacers\GH\Track02.bin
Pre-gap length 0:00:02.00
Peak level 96.5 %
Track quality 100.0 %
Test CRC 3B68D7A0
Copy CRC 3B68D7A0
Copy OK
Renegade Racers, Track 2 ISOBuster + Hex editor PX-760A:
Code: Select all
Calculating hash of 22127616 bytes file `C:\!Redump\NotSubmitted\!ActuallySubmitted\RenegadeRacers\T2-PX`...
SHA-160 : 032FAB688A27767B20C878DEC7F303275FC65855
MD5 : C4A8A3E3F2D4FE7A0414C9EFB0176591
CRC-32 : 3B68D7A0
Calculation took 0.374 seconds
Re: Rhaosody & px_d8 question
Posted: Sun May 09, 2010 2:54 pm
by Rocknroms
velocity37 wrote:Not if you use "Extract RAW", which is what "Extract From-To" uses by default.
You are right, sorry I was "out of business" for some times
Re: Rhaosody & px_d8 question
Posted: Tue May 11, 2010 8:57 am
by Specialt1212
Thank you all for responding and offering assistance.
velocity37 wrote:If you're uncomfortable with hex editors, you can instead:
psxt001z.exe --gen offsetfix.bin 2468
copy /b offsetfix.bin+track02.bin track02good.bin
FPCopy64 -r "track02good.bin" -2468
Why would I need to resize track 02 by 2468 bytes? I haven't done this on any of my other 2 track dumps?
I usually just do the following when dumping a 2 track disc
Code: Select all
FPCopy64 -r "track01.bin" -352800
(assuming the pregap is 2 seconds)
psxt001z.exe --fix "track01.bin"
psxt001z.exe "track01.bin"
psxt001z.exe --gen pregap.bin 352800
(assuming the pregap is 2 seconds)
copy /b pregap.bin+track02.bin track02good.bin
Should I be using the
FPCopy64 -r "track02good.bin" -2468 command for all 2 track discs?
I tried my normal method of dumping then used the above command to resize track 2 but it still didn't match the database entry.
I tried dumping this disc with Perfect Rip (using the Sega CD guide in the forums) & it matched the database entry exactly. I guess my only question is why can't I get the disc to match the database entry through the normal method of dumping? Are we sure that perfect rip is producing accurate results?
Re: Rhaosody & px_d8 question
Posted: Tue May 11, 2010 11:36 am
by Rocknroms
-2468 are the bytes in offset -617 => 617 x 4. IsoBuster dumps a track with no offset correction, so you do it manually.
You have to dump track with IB, not with normal method.
Now that I read better Velocity method there's a mistake because IB does like CDRwin and attaches gap to previous track. So to get the right track (for a single audio track CD) you have to add also pregap manually.
I suggest to use "remove" to work on those bytes (you can find it in some themabus threads or in the SS faq)
By the way this method can return bad results for tracks with strange sectors like some SS/CD32 disks.
PerfectRip and EAC have their pro and cons this is why it's better to use both (if you have a plextor) along with a subcode analisys when required.