Workflow: ripping a CD

[michael....@gmail.com]

Hi everyone,

I started using beets only recently, however, I've been using abcde[*] to rip CDs for more than a decade. The two work together, of course, but it feels like I'm doing redundant work. First, I rip and tag with abcde, then I import and tag again with beets (I don't yet let beets rename and move files).

I'd prefer to have a simple, integrated way to rip a new CD, tag it (or have it tagged), have beets import and move it to the appropriate place.

How are you ripping CDs?

Michael

[*] https://code.google.com/p/abcde/ , http://www.andrews-corner.org/abcde.html

[Johan Helsingius]

> How are you ripping CDs?

I use morituri (http://thomas.apestaart.org/morituri/trac/).
Written in python, supports MusicBrainz and AccurateRip (and
uses cdparanoia for the ripping).

[michael....@gmail.com]

I had a look at it earlier and it didn't tempt me at all. Is there a good reason, why things have to be so complicated?

Michael

[Johan Helsingius]

> I had a look at it earlier and it didn't tempt me at all. Is there a good
> reason, why things have to be so complicated?

Complicated? You just go "rip offset find" the first time to find the
offset of your CD drive (and that is something you have to do with every
program), and then just go "rip cd rip". Is that complicated?

Julf

[michael....@gmail.com]

Is that all there is? I didn't look again, but it seemed more involved. Anyway, I don't remember having to care about offsets before. Well, I'll have another look.

Michael

[Johan Helsingius]

> I don't remember having to care about offsets before.

Well, as with other programs, you don't have to care about it
unless you are obsessive about bit-perfect rips - and that
part is handled by cdparanoia, the underlying library of most
other serious ripping programs.

Julf

[michael....@gmail.com]

cdparanoia is also used by abcde (the tool I've been using for ripping for the past decade) and still I've never got the slightest hint that I'd have to care about offsets.

Be that as it may, I'd like to get back to my original question: Exactly how are you (actually anyone in here) using a ripper in conjunction with beets? In particular, how do you do the tagging?

Michael

[Johan Helsingius]

> cdparanoia is also used by abcde (the tool I've been using for ripping for the
> past decade) and still I've never got the slightest hint that I'd have to care
> about offsets.

Check out the -O (or --sample-offset) option of cdparanoia. In many
cases you can ignore it (and you can ignore it with morituri too),
depending on your drive, but morituri allows you to check the precise
offset for your specific drive.

> Be that as it may, I'd like to get back to my original question: Exactly how are
> you (actually anyone in here) using a ripper in conjunction with beets? In
> particular, how do you do the tagging?

I rip with morituri, and because it already uses musicbrainz, it gives
reasonable tagging as-is, but I then retag when importing with beets.
I don't see the 2-step process as a major issue, especially as I often
rip on my workstation but store the music on a server.