Ripping speeds of cds

[fayeanddavid]

We are (I am) in the process of ripping all our cds to iTunes, so far it has amounted to 25GB!!

Ripping everything at 320kps, I've noticed that the ripping speeds (is that the word?) can vary between 3.0x and 10.0x, some download at 10, some between 3 and 5, and most at 7 to 8x

Is this a function of disk technology due older disks ripping slower than newer, or is it the amount of information to be ripped or ..........?

Thanks

 

[Anonymous]

Ripping speed will vary due to the speed of the cd (8x,16x,32 max etc) being read, and the position on the cd of the track being ripped.

I'd expect ripping speeds to be 7-8x at the centre increasing to around 40x (or whatever max speed of cd/player - whichevers the lowest) as it approaches the outer edge.

Ripping a cd normally takes around 2-2.5min. Very old cds tend to be slower.

 

[Diamond Joe]

TechMad:
Ripping a cd normally takes around 2-2.5min. Very old cds tend to be slower.

I wish! My laptop can take up to 8 mins per CD.

 

[fayeanddavid]

Diamond Joe:TechMad:
Ripping a cd normally takes around 2-2.5min. Very old cds tend to be slower.

I wish! My laptop can take up to 8 mins per CD.

Yes, hence my question.....................I'm talking one minute plus per track, so 8-12 minutes per cd at a rip of 320kps

 

[davejberry]

As mentioned above and as i understand it, depends on position on CD, complexity of information and the ability of your system to convert the CD audio to the compressed format. I have a dual core processor running at 2.2 GHz. Typically ripping a 4 minute CD track to flac takes about 12 seconds. Transcoding flac to WMA lossless takes about 3 seconds using dBpoweramp.

 

[fayeanddavid]

davejberry:
As mentioned above and as i understand it, depends on position on CD, complexity of information and the ability of your system to convert the CD audio to the compressed format. I have a dual core processor running at 2.2 GHz. Typically ripping a 4 minute CD track to flac takes about 12 seconds. Transcoding flac to WMA lossless takes about 3 seconds using dBpoweramp.

davejberry

I read it, but I'm not getting it?

I have an HP Pavilion dm4 with i5 processing (up there with the new stuff I believe), I an ripping directly into iTunes at 320kps, and it takes on average a minute a track with a variable download speed for each track, not during the track, and I'm baffled (and somewhat bored, but it is a one off job)

 

[Anonymous]

Dont select error-correction when importing in ITunes - it takes forever.

If u want to ensure bitaccurate rips of cds use something like dbpoweramp.

For comparision trying to rip a cd to 320 AAC took me...

12min 40 secs Itunes (Error Correction ticked),

2min 50 secs in Itunes (Error-correction not ticked),

2min 20 secs bitaccurate in dbpoweramp.

 

[fayeanddavid]

Techmad,

I'll give it a go right now, thanks (I hope)

 

[fayeanddavid]

Right, error correction not selected, nor has it been but did note three additional options for AAC 320, they are

VBR

HE for High Efficiency encoding

and something re voice enhancement

VBR is the default tick box which I have left as such, could it be this??

 

[davejberry]

Sorry I couldnt give you a response more tailored to your set up, just hate i-tunes and avoid it like the plague. I was just trying to give you an idea what you could achieve. My system is about 4 years old, the only recent change is an upgrade to W7 and some more RAM. It may slower because you are compressing your music to a lossy format, are using i-tunes as opposed to any other ripper. I know that dBpoweramp is built for use on dual core systems and is faster at ripping to WMA lossless that WMP12 for example, its also better at getting metadata too.

VBR as I understand it means that the software will drop the bit rate from the maximum during quieter or less complicated parts of the track, saving you a bit of disk space and processor power.

 

[fayeanddavid]

All very confusing, hopefully someone can shed some light?

Thanks for the input though, appreciated

 

[manicm]

TechMad:

Dont select error-correction when importing in ITunes - it takes forever.

If u want to ensure bitaccurate rips of cds use something like dbpoweramp.

For comparision trying to rip a cd to 320 AAC took me...

12min 40 secs Itunes (Error Correction ticked),

2min 50 secs in Itunes (Error-correction not ticked),

2min 20 secs bitaccurate in dbpoweramp.

That's not been my experience with iTunes. Have you checked the speed limit in iTunes?

 

[fayeanddavid]

No doubt a dumb question, but where do I find the speed limit?

 

[Cofnchtr]

Hi,

I don't think there is an import speed for iTunes?

There is one when you burn a CD though.

Glad to be proven wrong though.

Cheers,

Cofnchtr.

 

[Anonymous]

If you want it to be a one time job I would not rip it to a lossy format to begin with.,,

 

[manicm]

Yeah, sorry, I think the speed adjustment is for burning only.