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: Incomplete WAVs from EAC (Read 2513 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Incomplete WAVs from EAC

I'm in the process of ripping my entire CD collection to FLAC using EAC and AutoFLAC.

EAC is able to read tracks from a few damaged CD's (light surface scratches) but occasionally a track on one such CD will take a long time.

My only PC is a laptop (with external CD drive and external hard disc for my media) that I also use for work and I often need to take the laptop out with me.

I currently have a track that has been ripping for 3 days. It's currently up to around 4 mins of a 6 min long track, and is now progressing at the rate of around one second every two hours. But tomorrow I'll need to take the laptop out, and will have to cancel EAC.

The previous times I have done this, I've ended up with a large wav file of the ripp so far, which won't play in any of the software I have (WMP, Real Player, etc) or open in Audacity. (Although Tag & Rename does display a correct bit rate and duration for these incomplete files.) So my questions are:

1) Is there anyway I can come back to ripping the track later, and get EAC to continue from where it left off (rather than starting over again, as it does now.

2) Is there anyway I can open the incomplete wav files. (Having 4 mins of a 6 min tack is better than not having it at all. I could always add an end fade with Audacity.) I'm assuming that it won't play or open because some kind of header or tag is not written until the end. Is there any way I could manually add one to make it usable.

Incomplete WAVs from EAC

Reply #1 –
If I were you I would simply accept that this track cannot be ripped in secure mode and move on. Rip it in burst mode and accept (or fix manually) any audible defects.

If you continue to do what you are doing then your drive will suffer an early death.

Incomplete WAVs from EAC

Reply #2 –
Since you haven't mentioned this option yet I'd like to make sure you have the "Allow speed reduction during extraction" setting unchecked, found in the "Offset / Speed" tab of the drive options. The laptop's optical drive might be unable to spin up to full speed again after encountering an error, hence prohibiting it to slow down could solve this issue. Note that doing so will seriously impact its abilities to correct reading errors, i.e. it might be reasonable to check the option again after trying this out.

At least I for my part keep the speed reduction thingamabob unchecked for one of my PC's two drives, since it takes ages for ripping erronous tracks as well, simply because it doesn't speed up after the error correction process.

If this doesn't help do as the above poster suggested. Burst mode is a quick and often more reliable ripping alternative for problematic tracks. In case this didn't work as well the only option left would be to carefully listen to the track on playback and record it if there were no audible errors, though it's unlikely that this would lead to satisfying results.