![]() ![]() dBpoweramp does everything on the fly, so I switched. But it happens that I don't have sufficient lifetime to fuss over tagging, album art, file rewrites and 20 minutes ripping a CD in Secure Mode (my drive has to defeat audio data cache). Yes, there are millions of configurations and tweaks. And this can really kill your sleep, if you get too paranoid about perfect god-made rips - something always goes out of the pattern. When I start stepping this paranoia OCD I try to make a move out of it, because I realize the music no longer is the important factor or fun to mess with - but the intangible "perfect bytes" no one really cares about. The reason I made this move was the literal paranoia I was getting with EAC. I must say I am quite impressed with the software suite. Have fun testing a bunch of drive read and gap detection methods to optimize a drive. What does that even mean? You have to choose the best one to get the fastest and most reliable gap detection for you drive. Same with gap detection There are A, B, and C gap detection methods. But you have to try them to find the optimal settings for a drive. What is the difference between the MMC read command and MMC1 and MMC2 and D8? I have no idea. To find the best one you have to try each of them. ![]() You need to select the best read command for your drive to get the fastest and most reliable rips. Most people just want a free ripping program that is easy to use.ĮAC also has many options for drive read commands. You insert a CD, make sensible selections in a few drop-down menus, and click the big "Go" button to rip. It doesn't confuse people with unneeded options. I usually recommend CUERipper over EAC because CUERipper is easy to use and only has options that are proper and that you might need. Choosing the wrong options could cause you grief later. Especially options related to gap handling. If you use those options you have to know what you are doing and know why you are choosing those options. Unfortunately many of the possible combinations of options in EAC will result in sub-optimal or incorrect rips. EAC is confusing because it has so many options. I tried Foobar's foo_verifier on the exact same 28 tracks and it gave me this:Ġ1 Accurately ripped with offset: 146(1).Ġ2 Accurately ripped with offset: 146(1).Ġ3 Accurately ripped with offset: 146(1).Ġ4 Accurately ripped with offset: 146(1).Ġ5 Accurately ripped with offset: 146(1).Ġ6 NOT ACCURATE even with offset: 146(1).Ġ7 NOT ACCURATE even with offset: 146(1).Ġ8 Accurately ripped with offset: 146(1).Ġ9 Accurately ripped with offset: 146(1).ġ0 Accurately ripped with offset: 146(1).ġ1 Accurately ripped with offset: 146(1).ġ2 Accurately ripped with offset: 146(1).ġ3 Accurately ripped with offset: 146(1).ġ4 Accurately ripped with offset: 146(1).ġ5 Accurately ripped with offset: 146(1).ġ6 Accurately ripped with offset: 146(1).ġ7 Accurately ripped with offset: 146(1).ġ8 Accurately ripped with offset: 146(1).ġ9 NOT ACCURATE even with offset: 146(1).Ģ0 NOT ACCURATE even with offset: 146(1).Ģ1 NOT ACCURATE even with offset: 146(1).Ģ2 NOT ACCURATE even with offset: 146(1).Ģ3 Accurately ripped with offset: 146(1).Ģ4 Accurately ripped with offset: 146(1).Ģ5 NOT ACCURATE even with offset: 146(1).Ģ6 NOT ACCURATE even with offset: 146(1).Ģ7 Accurately ripped with offset: 146(1).Ģ8 NOT ACCURATE even with offset: 146(1).EAC is powerful because it has so many options. Sorry I am having a tough time at deciphering what's going on, but I have ripped hundreds of discs and will collapse if I have done something wrong.Įven stranger. If the offset is set right in dBp, is cuetools messed up? What is going on? Is my offset wrong? If so, why do the dBpoweramp logs show AccurateRips on all tracks. when I drag the 28 tracks into cuetools (latest version), it gives me this output:Ĭ:\-\Music\Captain Beefheart\Trout Mask Replica (1970)\01 - Frownland.flac: AR: offset 146, rip not accurate (0/1), CTDB: disk not present in database. ![]() ![]() Ultra:: Vary Drive Speed: No, Min Passes: 3, Max Passes: 6, Finish After Clean Passes: 2īad Sector Re-rip:: Drive Speed: Max, Maximum Re-reads: 34Įncoder: FLAC -compression-level-8 -verifyĭSP Effects / Actions: -dspeffect1="ReplayGain=-albummode=" -dspeffect2="HDCD=" Pass 1 Drive Speed: Max, Pass 2 Drive Speed: Max Ripping with drive 'D: ', Drive offset: 6, Overread Lead-in/out: NoĪccurateRip: Active, Using C2: No, Cache: None, FUA Cache Invalidate: No When looking at the log generated at work, I see this:ĭBpoweramp Release 14 Digital Audio Extraction Log from Thursday, Octo02:58 PM I ripped a Captain Beefheart CD at work and allowed dBpoweramp to apply a 6 offset to all my discs. ![]()
0 Comments
Leave a Reply. |