why are cd-roms with redbook audio split into tracks
Re: why are cd-roms with redbook audio split into tracks
oic, i'm ripping a cd for the first time in EAC in a week or so. i just put it in three times and got different values for gaps each time lol
All my posts and submission data are released into Public Domain / CC0.
Re: why are cd-roms with redbook audio split into tracks
That can happen if the cd is scratched. Beyond that make sure your gap detection is set to 'secure' and try the all the gap detection methods (A,B,C) and see if one of the other ones gives better results. If that doesn't help it may be a drive issue.
Re: why are cd-roms with redbook audio split into tracks
yes indeed it was scratched. greynol from hydrogen audio explained that regardless of what gap time is detected, the final output will be the same. in other words whatever the subchannel data says in relation to gap times, the final output (and checksum) will be the same. at this point i wonder if subchannel data has any relevance at all.
All my posts and submission data are released into Public Domain / CC0.
Re: why are cd-roms with redbook audio split into tracks
the gaps determine the individual track sizes..
at this point i wonder if this thread has any relevance at all.
at this point i wonder if this thread has any relevance at all.

Re: why are cd-roms with redbook audio split into tracks
maybe this thread doesnt and i'm just failing to understand something, however this is the issue as i see it.
1. different gap sizes can occur for the same cd/cd-rom
2. ripping tracks individually will result in size deviation between multiple rips if gaps deviate (according to Jackals post above), however according to greynol, if gaps deviate, this has NO effect on the end result/checksum (see: http://www.hydrogenaudio.org/forums/ind … opic=72969 )
3. ripping the cd-rom as a single image will not influence size (even if gap sizes deviate), thus are more likely to be correct dumps
maybe i'm just overthinking this or inserting a problem where it is not necessary. i didnt start this thread as a criticism by any means and maybe this issue is only relevant with scratched CDs, however after reading fireball and themabus's 2/3 page argument on subchannel accuracy, i became curious on the effect of mismatching gap size on the accuracy of dumps.
dude, cd-roms are an asspain!
1. different gap sizes can occur for the same cd/cd-rom
2. ripping tracks individually will result in size deviation between multiple rips if gaps deviate (according to Jackals post above), however according to greynol, if gaps deviate, this has NO effect on the end result/checksum (see: http://www.hydrogenaudio.org/forums/ind … opic=72969 )
3. ripping the cd-rom as a single image will not influence size (even if gap sizes deviate), thus are more likely to be correct dumps
maybe i'm just overthinking this or inserting a problem where it is not necessary. i didnt start this thread as a criticism by any means and maybe this issue is only relevant with scratched CDs, however after reading fireball and themabus's 2/3 page argument on subchannel accuracy, i became curious on the effect of mismatching gap size on the accuracy of dumps.
dude, cd-roms are an asspain!
Last edited by user7 on Wed Jun 24, 2009 4:52 pm, edited 1 time in total.
All my posts and submission data are released into Public Domain / CC0.
Re: why are cd-roms with redbook audio split into tracks
Generally no, fireball and themabus's discussion regards the question of wether an improperly mastered disc with subcode that indicates the wrong gaps should be 'corrected' by rounding to get back the expected pre-mastering tracks. If one of these incorrectly mastered discs is read multiple times it would show the same gaps (just arguably incorrect ones).1. different gap sizes can occur for the same cd/cd-rom
This only applies to older systems that had this issue. (i.e. Sega CD).
According to greynol in regards to weather CRC with be different:2. ripping tracks individually will result in size deviation between multiple rips if gaps deviate (according to Jackals post above), however according to greynol, if gaps deviate, this has NO effect on the end result/checksum (see: http://www.hydrogenaudio.org/forums/ind … opic=72969 )
Gaps won't effect track crcs if "No use null samples for CRC calculations" is checked in EAC, so long as the gap isn't so far off as to push data past the track boundary. We want track timing to be correct as well as the track data, so we include the leading and trailing zeros in our Hash calculations.Depends on what you're telling EAC to do with gaps.
True, but the track timing will deviate resulting in an incorrect gap structure in the cue. In essence the important data on a cd consists of the data and audio tracks and the subcode that indicates track gaps.3. ripping the cd-rom as a single image will not influence size (even if gap sizes deviate), thus are more likely to be correct dumps
Since the subcode can't reliably be dumped with matching crcs we use EAC or other methods to get the track layout and store that information in the cue file. In other words the .cue file captures all the important information from the subcode. Dumping with no gap detection would result in repeatable data and audio track dumps, but we would permanantly lose the subcode information.
Re: why are cd-roms with redbook audio split into tracks
alright, i think i understand after than explanation. thanks.
edit: i found out that EAC has an option to "securely" detect gaps. it keeps testing them until they get 3 matches
edit: i found out that EAC has an option to "securely" detect gaps. it keeps testing them until they get 3 matches
Last edited by user7 on Sat Jun 27, 2009 12:00 am, edited 1 time in total.
All my posts and submission data are released into Public Domain / CC0.