Thread: feature request: encode after all tracks ripped

My Plextor CD-RW drive seems to spin up to some ridiculous noisy speed whenever ripping of a track begins. Instead of ripping one, encoding one, etc., it would be great if EAC would rip the whole disc, then encode it.

It'll take more hard disc space, but that's cheap & plentiful.

Eventually, I'd love for EAC to queue encoding so it would let me rip a whole bunch of discs, changing them much quicker than if I had to wait for encoding, and encode them while I sleep.

I'd use RazorLame to drive LAME after ripping to WAV, but I can't figure out how to preserve all information that EAC+LAME puts so nicely in the tags for my iPod.

I'll make this request by postcard too as I'm not "registered" yet.

EAC is amazing, by the way!

-Morgan

as so many features, EAC already provides what you describe here.. ,-)
just check the option "make all compression tasks sleep" in the compression queue control center. rip all day long, before you go to bed, uncheck, and compression jobs are processed.
i think, this is implemented VERY WELL in EAC. since i use it, i NEVER ever had any probs doing it this way.. even after rebooting the comp, the jobs are still in queue. skipped or otherwise incomplete tracks drop out of the queue, which is highly desired.. i sometimes pile up as much as 300 compression tasks without any probs... another positive effect is, that ripping has much less cpu consumption (if using DMA mode) so i have no performance probs using the pc. whereas lame uses almost 100% which makes it virtually impossible to use the pc for other purposes in the meantime..

cu

whereas lame uses almost 100% which makes it virtually impossible to use the pc for other purposes in the meantime..

Not if you use a frontend like RazorLame :-).

Originally posted by wyhiwyg
whereas lame uses almost 100% which makes it virtually impossible to use the pc for other purposes in the meantime..

Not if you use a frontend like RazorLame :-).

what makes the actual difference? the job to be done should be the same, i thought the only difference is, that the frontend provides a GUI...
as far as i know, compression speed varies very much with the version of lame used... some are really fast, some other apply routines that slow down the process

which lame version does your frontend use?
i use 3.90.3/ the hydrogenaudio.com-compile
which is generally considered to yield highest quality.

however, i don´t care if it is 100% or less, because i trigger compression before i go to bed.

After I check "make all compression tasks sleep" EAC still compresses immediately after ripping

Windows 2k, EAC 0.95 pb4, LAME

Nevermind. I figured it out.
To rip and then compress separately:

1) Need to have "On extraction, start external compressor queued in the background" (Use 1) checked located in EAC Options->Tools.
2) Check "Make all compression tasks sleep" located in Database-> Compression Queue Control Center
3) Rip the songs
4) after you are done ripping all the songs, goto Database-> Compression Queue Control Center, uncheck "Make all compression tasks sleep" and press OK....it will start compressing the songs you ripped

whereas lame uses almost 100% which makes it virtually impossible to use the pc for other purposes in the meantime..

Use task manager to set the process priority to something lower than "Normal"

Originally Posted by yyz77

whereas lame uses almost 100% which makes it virtually impossible to use the pc for other purposes in the meantime..

Use task manager to set the process priority to something lower than "Normal"

why should I? my PC is pretty much bored when I´m sleeping, working off 500 compression jobs overnight is exactly what it needs.... *G*

It would be nice to just be able to tick one box that says 'Encode after all tracks are ripped' as well as having the current feature.