So I put Linkin Park Hybrid theory (which is a key disc) and configured my settings so that I got wav files which were accurately ripped. Then with the same settings, instead of ripping the tracks seperately I clicked make image and got a wav + CUE, then mounted this with DAEMON and when I open EAC (with the virtual drive selected) the accurate rip thing comes up saying that I have a key disc with an expected offset of 0, then I click then I click continue and I get an error telling me that the image does not match the one which is in the database.
Is this the right way to go about making an image which will rip correctly with AccurateRip,
then the next step is how do I this while Losslessly compressing the audio?
Nope. Do it the other way round!
The crucial part is the actual ripping from the physical disc. And since AccurateRip only works with seperate tracks, you have to rip to seperate tracks.
After that you can still losslessly convert the single tracks to a valid single image + cue sheet with a tool called CUETools. All you need for this conversion to work are the seperate tracks and a non-compliant cue sheet (EAC->Action->Create CUE Sheet->Multiple WAV Files With Gaps... (Noncompliant)".
Then you can compress the image file on-the-fly with CUETools or using a command line encoder... Wavpack, FLAC even Monkey's Audio (APE) all come with a CLI encoder. Have a look around the forum or ask here if something's unclear.
The crucial part is the actual ripping from the physical disc. And since AccurateRip only works with seperate tracks, you have to rip to seperate tracks.
After that you can still losslessly convert the single tracks to a valid single image + cue sheet with a tool called CUETools. All you need for this conversion to work are the seperate tracks and a non-compliant cue sheet (EAC->Action->Create CUE Sheet->Multiple WAV Files With Gaps... (Noncompliant)".
Then you can compress the image file on-the-fly with CUETools or using a command line encoder... Wavpack, FLAC even Monkey's Audio (APE) all come with a CLI encoder. Have a look around the forum or ask here if something's unclear.
QUOTE (Fandango @ Dec 22 2006, 20:58) 
Nope. Do it the other way round!
The crucial part is the actual ripping from the physical disc. And since AccurateRip only works with seperate tracks, you have to rip to seperate tracks.
After that you can still losslessly convert the single tracks to a valid single image + cue sheet with a tool called CUETools. All you need for this conversion to work are the seperate tracks and a non-compliant cue sheet (EAC->Action->Create CUE Sheet->Multiple WAV Files With Gaps... (Noncompliant)".
Then you can compress the image file on-the-fly with CUETools or using a command line encoder... Wavpack, FLAC even Monkey's Audio (APE) all come with a CLI encoder. Have a look around the forum or ask here if something's unclear.
The crucial part is the actual ripping from the physical disc. And since AccurateRip only works with seperate tracks, you have to rip to seperate tracks.
After that you can still losslessly convert the single tracks to a valid single image + cue sheet with a tool called CUETools. All you need for this conversion to work are the seperate tracks and a non-compliant cue sheet (EAC->Action->Create CUE Sheet->Multiple WAV Files With Gaps... (Noncompliant)".
Then you can compress the image file on-the-fly with CUETools or using a command line encoder... Wavpack, FLAC even Monkey's Audio (APE) all come with a CLI encoder. Have a look around the forum or ask here if something's unclear.
well I just did a test doing what you sugessted
1) CD-->mp3
2) CD-->wav-->mp3
3) CD-->FLAC-->mp3 (didnt try this but assuming same result)
in comparing these 2 mp3's they audio data itself appears to be exactly the same but the headers and end of file are differnt see below [Is there a switch to preserve the tags??]
see essentially I want gapless playback, and it looks like I get that (unless foobar is just special
)I dont see what the need for the cue sheet is then if i dont mount anything
with regards to the image below, I have no idea waht those 'x's' mean as i just googled and downloaded the first progam I found
Honestly I'm confused now and don't know what you actually want to achieve. I thought you wanted to create an image (single WAV file) out of seperate tracks that were approved by AccurateRip and then encode this image with a lossless codec...
But if it's only seperate MP3 tracks that you want then you don't need any image rips at all (and of course no cue sheets either). Just rip to seperate tracks (compressed) and everything should be fine. There are tons of threads describing how to set up EAC for this task... and I think you already did it right (that would be your test #1 - the one with the tags, right?).
PS: The recommended LAME version is now 3.97, 3.90.3 was yesterday.
But if it's only seperate MP3 tracks that you want then you don't need any image rips at all (and of course no cue sheets either). Just rip to seperate tracks (compressed) and everything should be fine. There are tons of threads describing how to set up EAC for this task... and I think you already did it right (that would be your test #1 - the one with the tags, right?).
PS: The recommended LAME version is now 3.97, 3.90.3 was yesterday.
*EDIT-reword
I think I understand why gaps ocurr in mp3's, because of the time-->frequncy domain conversion, [well the reverse transorm rather] brings data from before and after, thus creating extra space at the begning of the track [and end?], so by this argument, lossles doesn't experience this (as it relies on functions to represent the data)
so I would hope that the creation of the data for solving the lossy gap problem purely relies on the start of a lossless file
Thus eliminating a need for image, cue's... then if thats the case why do people use image-cue combos?
I think I understand why gaps ocurr in mp3's, because of the time-->frequncy domain conversion, [well the reverse transorm rather] brings data from before and after, thus creating extra space at the begning of the track [and end?], so by this argument, lossles doesn't experience this (as it relies on functions to represent the data)
so I would hope that the creation of the data for solving the lossy gap problem purely relies on the start of a lossless file
Thus eliminating a need for image, cue's... then if thats the case why do people use image-cue combos?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.