Just starting with "Digitization"

To many ads? Support ODJT and see no ads!
Dec 22, 2008
2,473
12
52
Roseville, CA
www.sounds2go.com
I am going to be starting the process of converting my library to digital... Any tips, hints, tricks, things to avoid, must-do's etc?

I have read Rick's site and plan to do it slow, tag it right, and use that nifty BPM software that's on there for the tagging...

One thing though... I have used Audio Grabber quite a bit, and I am wondering... does anyone else have a problem with problems with ripping... namely "skips" in the finished file?

I did a bunch of individual songs from different discs tonight, in 320 MP3 and they all had little skips in them, many right around the 40 second-or-so mark... kinda odd.

Ripping to WAV seemed to get rid of it...

I have been using CD-DA X-Tractor a lot longer, and it seems to be a lot more stable on the ripping side and doesn't have this problem on the same discs with the same tracks, but the tagging/ID3 in it stinks.

Any ideas? I want to do my homework now before I have countless hours invested in ripping and tagging only to find my rips are not stable.

Thanks!
 
I had that problem, but it all went away when I started using Media Monkey. But it was ages ago when I started using MM.... Audiograbber is faster than MM.... i wonder if that may be an issue.
 
Justin,

1st, you'll need to get rid of the comment on your website that says you don't use mp3's for sound quality purposes! : )

I don't know how many cd's you have to rip, but, I bought an automated robotic arm cd ripper that had a bin that would run through 25 discs at a time, rip them, name and tag them, even while I was asleep. I went through more than 5,000 discs using that machine and re-ripped my entire cd collection from 256 to 320 kbps.

Make sure you are using a lame encoder. Don't use Blade.

Also, the "blip" you mentioned may have something to do with a buffer underun. Is the machine that you are ripping with being used ONLY for ripping? I would not multi-task while ripping.
 
I used EAC when I redid my library. It provides a report on whether there were problems in a track. You can then listen to the song at the times it reported problems at to see if they are audible or not. I ended up with a lot better quality rips using EAC, there were very few with problems reported.

Before EAC I used Audiograbber and wound up with clicks and pops, not anymore. Plus, the best part, it's free.
 
Lane,

Actually I am intending to rip everything in WAV's, but am just getting familiar with the software and tagging, which is why I was experimenting with the MP3's...

But you're right... If I did sell my soul to the devil and decide to go with an inferior format, I will have to scrub my site for any hypocritical references! :sqlaugh:

It just has me concerned because it actually happens at the SAME POINT (ie 39-44 sec window) in EACH TRACK I ripped... using different discs... so it almost seems to me to be an issue with the application itself. I can understand data errors on discs, multi-tasking/CPU/buffering issues placing random glitches in files, but in the same place on all of them? I'm just wondering if wiping out AG and doing a fresh install of it might fix the issue.

Thanks!
 
If you rip direct to WAV, you shouldn't see that issue.

If you rip direct to MP3 using Lame as the encoder, AG has to call the Lame DLL, and at that point, AG is probably reading faster then Lame can encode, hence the burp around the same time.


I've been re-ripping my entire collection over the last week or so, and not even a blip (I'm ripping direct to WAV). I'm getting speeds of about 25-40x on the rips.

Now, when I encode to MP3, the data is already there, and there is no conflict between the ripping speed, bus speed, and the encoder speed :)
 
EAC will rip to wav....then convert to mp3...and delete the wav (if you want..)....I've never had a glich with EAC/Lame

So does AG.... but, what Rick advocates is ripping to wav then doing a bulk convert to mp3... saves time on the rip process and can be done over night.

Keeping the wav file for archiveal purposes.

But, alas I don't so I'm SOL if a better format comes along.
 
Just an FYI...

I haven't played with EAC for a bit, so thought I'd give it a try again for S&G.

My security software is blocking access to their download because of embedded malware, and is also blocking portions of their site.
 
If you rip direct to WAV, you shouldn't see that issue.

If you rip direct to MP3 using Lame as the encoder, AG has to call the Lame DLL, and at that point, AG is probably reading faster then Lame can encode, hence the burp around the same time.


I've been re-ripping my entire collection over the last week or so, and not even a blip (I'm ripping direct to WAV). I'm getting speeds of about 25-40x on the rips.

Now, when I encode to MP3, the data is already there, and there is no conflict between the ripping speed, bus speed, and the encoder speed :)


WooHoo... Sounds like my theory was correct..... go me, go me.... :sqlaugh:
 
WooHoo... Sounds like my theory was correct..... go me, go me.... :sqlaugh:

OMG, the kid's head is going to explode... :sqlaugh: :rofl:


Basically, what this comes down to, is a two step process -- copy the file from the CD, then encode it to MP3.

You don't want to do both concurrently, because they are two separate processes, that are both CPU intensive. The encoding part is generally the most intensive part of the equation, so should not be done at the same time as the rip.

My analogy:

Brick laying (since I'm a Mason).

The guy that lays the bricks, does not go get the bricks, he has a helper that does that. Another helper often mixes the mortar. They are 3 distinct tasks, and work well when each task is done by a dedicated worker.

You can accomplish the same thing with one computer, without error -- IF, you separate each task, and don't attempt to do both at the same time.


I ripped about 50 CDs in the last couple hours, while goofing around here, chatting in Hank's Lounge, and ordering dog food. The reason the rips went fast and error free, is because it was just a copy into WAV format. I wouldn't be doing all that stuff during encode though... ;)
 
Wow, this has really taken off - thanks guys.

Okay, so Two-Part process if I want to go MP3:

1. Rip to WAV
2. Do a batch/bulk convert to MP3

What application is recommended for helping with tagging of files or is this just a manual process you'll have to do as you go?

Ideally I would like to go with WAV, but seems from my limited experience and research that tagging options for WAV is virtually non-existent, and can even be problematic?

(heard mumblings online in various places about ID3 tags breaking the containers on WAV files, etc.)

Any validity to all that?

I may be forced to go to MP3 just for the comprehensiveness of the tagging options available on the format unless a similar level of detail can be achieved with WAVS?

Thanks again to all.
 
What application is recommended for helping with tagging of files or is this just a manual process you'll have to do as you go?

Ideally I would like to go with WAV, but seems from my limited experience and research that tagging options for WAV is virtually non-existent, and can even be problematic?

(heard mumblings online in various places about ID3 tags breaking the containers on WAV files, etc.)

Any validity to all that?

I may be forced to go to MP3 just for the comprehensiveness of the tagging options available on the format unless a similar level of detail can be achieved with WAVS?

Thanks again to all.

If you go WAV I believe AG can attach tags to the wav file which it then uses later for tagging the MP3 file, but if you want to stick with WAV then Rockit is probably your best bet for playback since it can read the psudo tags AG puts on WAV files....

Otherwise ya it's most likely a one by one process.... save yourself the trouble and just go mp3 at 320 and set the WAV files aside for later conversion to newer better formats as they come out.
 
Yeah I've decided to use Rockit for sure. I just downloaded a trial last night. I need to do my research on controllers now too.

But don't necessarily want to muck up this thread with that as Im sure there are other relevant threads on that in this topic - I just havent started poking around this part of the forum yet.
 
Just catching up with this thread..

From before.. I believe in Audiograbber you can select a speed. Default is "fastest", but if your rips (regardless of format) start giving you glitching, I recall adjusting the speed of the rip is possible, and resolved a problem I had years ago.
 
Ideally I would like to go with WAV, but seems from my limited experience and research that tagging options for WAV is virtually non-existent, and can even be problematic?

Sounds,

You don't really want to play WAVs at a gig (maybe at home on yer audiophile system). The WAVs are the intermediary step.


Here's how I do it:

1. Rip each CD in to WAV on a separate drive or folder (AudioGrabber appends basic tag info to end of WAV).

2. Cherry pick songs you might ever play, and move them into an encode folder.

3. Encode the songs into MP3 format (max quality 320 Kbps). AudioGrabber populates the MP3 tags, with the info it saved on the WAVs.

4. Tag everything with album cover art.

5. BPM scan everything.

6. Move all MP3s onto working drive(s).


Your WAV drive becomes your main library -- you can always encode to any format off this library, without ever pulling the CDs again (unless yer like me, and like doing that stuff). Make at least one backup of that drive.
 
Just catching up with this thread..

From before.. I believe in Audiograbber you can select a speed. Default is "fastest", but if your rips (regardless of format) start giving you glitching, I recall adjusting the speed of the rip is possible, and resolved a problem I had years ago.

Not usually an issue Steve, if yer ripping to WAV. I go at full tilt, and have no problems.

If you try to encode at the same time, then you should slow down the rip (not recommended, as it defeats the purpose of the main WAV library, plus the blips in the music).
 
Sounds,

You don't really want to play WAVs at a gig (maybe at home on yer audiophile system). The WAVs are the intermediary step.


Here's how I do it:

1. Rip each CD in to WAV on a separate drive or folder (AudioGrabber appends basic tag info to end of WAV).

2. Cherry pick songs you might ever play, and move them into an encode folder.

3. Encode the songs into MP3 format (max quality 320 Kbps). AudioGrabber populates the MP3 tags, with the info it saved on the WAVs.

4. Tag everything with album cover art.

5. BPM scan everything.

6. Move all MP3s onto working drive(s).


Your WAV drive becomes your main library -- you can always encode to any format off this library, without ever pulling the CDs again (unless yer like me, and like doing that stuff). Make at least one backup of that drive.

Thanks Rick.

Why not WAVs at a gig? They slow down system or something? Potential performance issues?

On tagging and album art... what app to do that part? I've seen the BPM program on your site and will use it if going mp3 for sure.

Thanks again in advance.