Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: EAC: Should I manually make it detect gaps before ripping to cuesheet? (Read 4350 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

EAC: Should I manually make it detect gaps before ripping to cuesheet?

Hi everyone,

So, I've recently been following a new guide to setting up EAC.

On the section about gap detection and cue sheets, the author of the guide says to detect gaps first, and then create a cue sheet. It gets a little technical at that part and I got confused, so I realized recently that the first 3 rips I've done, I've done it the opposite way. I created a cue sheet and THEN detected gaps.

I did some more reading about this and I read that in creating a cue sheet, EAC automatically detects gaps if they weren't already detected. However, in the gap section where the song titles are, EAC lists "unknown" for every track's gap until I hit "Detect Gaps" and then, gap lengths appear. Is this an issue?

Thanks in advance for any help.
 

EAC: Should I manually make it detect gaps before ripping to cuesheet?

Reply #1 –
The detection is always done when creating cuesheets. Invoking it manually before that is purely cosmetic.
Quote from: mjb2006 on
Gap detection and other CD subcode scanning is performed automatically when a cue sheet is generated. There is no need to do it manually unless you want to see the gap values in the main window and in the ripping log (where they arguably don't belong, IMHO).
Also, please title and place your threads better.

EAC: Should I manually make it detect gaps before ripping to cuesheet?

Reply #3 –
I'd construe linking to a forum partially dedicated to file-sharing as a TOS#9 violation [edit: already taken care of], even though you only pointed to the ripping guide (which actually came from an even more ridiculously bureaucratic file-sharing venue).

If you are relying on that guide, I assume it's because you want to upload things for their approval. In that case, you need to follow their rules, no matter how misguided they may be. So if they say that in order to avoid having your log file rejected by their dumb scripts, you must detect gaps before ripping, then that's what you have to do.

That guide has other questionable advice in it. I understand the desire to have a single procedure that minimizes the risk of problems, but if you can get AccurateRip or CTDB matches with confidence > 1 with burst mode (clean discs) or secure mode (scratched, etc.), then why wear out everyone's drives and waste time with secure mode (always), detecting gaps twice, defeating caching the drives probably don't do, and avoiding C2 pointers because "most drives have terrible C2 error implementation"?

(rhetorical question; save your responses for another thread)

EAC: Should I manually make it detect gaps before ripping to cuesheet?

Reply #4 –
AR confidence = 1 is just fine; it is the same as T&C.  I suppose you can go farther in an attempt to ensure that your rip is not just being compared against your own submission but that is is still no guarantee since it is possible to re-submit after a change in ID# which is extremely trivial to do.

EAC: Should I manually make it detect gaps before ripping to cuesheet?

Reply #5 –
Quote from: kirbydoo on
Hi everyone,

So, I've recently been following a new guide to setting up EAC.

On the section about gap detection and cue sheets, the author of the guide says to detect gaps first, and then create a cue sheet. It gets a little technical at that part and I got confused, so I realized recently that the first 3 rips I've done, I've done it the opposite way. I created a cue sheet and THEN detected gaps.

I did some more reading about this and I read that in creating a cue sheet, EAC automatically detects gaps if they weren't already detected. However, in the gap section where the song titles are, EAC lists "unknown" for every track's gap until I hit "Detect Gaps" and then, gap lengths appear. Is this an issue?

Thanks in advance for any help.


First create a folder you want your music to go to.

1. Database < Get CD Information.

It will then ask if you want cover art. Skip if you want because I usually get it from Google and try to have at a cover size of 500x500. Skip lyrics unless you want them. You might want to check track titles and so on to make sure they match.

2. Action < Detect Gaps

3. Action < Create CUE Cue Sheet < Multiple WAV Files with Gaps (Noncompliant)

4. Action < Test & Copy Selected Tracks < Compressed

Let it do its thing and usually after a couple of minutes it's done.
Xonar Essence XT + Foobar = heaven on a budget.

EAC: Should I manually make it detect gaps before ripping to cuesheet?

Reply #6 –
What does your post offer to the question that was asked? The OP asked whether detecting gaps is necessary. We have explained that it is not. If the OP wanted a generic guide with no specific reference to their question whatsoever, they could have got one from various other places…which they already did.