Page 1 of 2
Railroad Tycoon 2
Posted: Sun Mar 21, 2010 1:28 pm
by TAurus
I'm trying to dump Railroad Tycoon 2 but I'm not able to get a consistent gap detection in EAC.
In the cue sheet generated by CloneCD I get 1.74 for all tracks.
I've also attached subs.
Thank you for your help.
Re: Railroad Tycoon 2
Posted: Sun Mar 21, 2010 1:29 pm
by TAurus
... and second sub
By the way, is there a guide available on this forum or anywhere on the internet on how to analyze the subs ? I want to learn so not to upload subs anytime I have this kind of issues.
Thx.
Re: Railroad Tycoon 2
Posted: Sun Mar 21, 2010 10:24 pm
by themabus
hi TAurus
basically you would have to read
ECMA-130 (chapters: 20, 21, 22) and examine .sub with
Subcode Analyzer
here's a brief example with Mode 2 section (most often cause) affecting EAC's gap size detection
Re: Railroad Tycoon 2
Posted: Fri Apr 02, 2010 8:15 am
by TAurus
I did not have the time to study the documentation, so I appreciate if someone can analyze the subs.
Thank you.
Re: Railroad Tycoon 2
Posted: Tue Apr 06, 2010 12:07 pm
by TAurus
UP
Re: Railroad Tycoon 2
Posted: Tue Apr 06, 2010 12:28 pm
by themabus
which are problematic tracks?
briefly checking 1st file it looks like data->audio gap = 2s; audio->audio gaps = 1.74s
which is not uncommon pattern
btw for some reason RAR complains about unexpected end of archive for those attachments
Re: Railroad Tycoon 2
Posted: Tue Apr 06, 2010 2:02 pm
by TAurus
The problematic track is the first one (data->audio). I get 2.74 or 1.74. I've attached again the subs.
Re: Railroad Tycoon 2
Posted: Tue Apr 06, 2010 2:03 pm
by TAurus
second sub
Re: Railroad Tycoon 2
Posted: Tue Apr 06, 2010 2:06 pm
by TAurus
The files gets corrupted when attached to forum.

(
Using a
2.74 sec gap I get
-588 write offset.
If I use
3sec gap I get
0 write offset.
Re: Railroad Tycoon 2
Posted: Tue Apr 06, 2010 5:39 pm
by TAurus
I finally read the documentation and did a check with subcode analyzer and I get 2.0 sec for the first track and 1.74 for the rest of them. The problem now is that I have only zero's if I go back 2.0 seconds. I need to get back at least 2.74 to find some data. This is with a +667 drive. If 2.0 sec is the real gap I suppose I need a drive with even larger read offset... Is this correct ?