CD ripping

[ghost]

This issue was automatically migrated from Google Code. Original author: fil...@gmail.com (June 22, 2011 09:44:56) Original issue: https://github.com/google-code-export/beets/issues/207

[JDLH]

I second the idea of calling on morituri to do the ripping. One area of overlap between management (beets) and ripping (morituri) is in identifying which Musicbrainz Release entry corresponds to a particular CD. It can be that a CD discid maps to multiple Releases (different countries, labels, release dates, etc.) Often the human is required to choose the correct entry. I'd like to have to do this only once, and have beets know the result. Also, I want the discid to be stored with the metadata, and that requires access to the CD, which the ripper will have.

[tlc]

I'm a happy user of morituri, but I think it's a bad idea to integrate it.

Some things to consider about integrating them:

• Morituri is a pain to configure -- discovering and storing the drive offset, patching cdparanoia.
• Morituri is slow (because it does perfect rips). Some won't appreciate that.
• Morituri leaves multi-disc albums in different directories. Really, it rips discs.
• Morituri creates files for "empty" hidden tracks.
• Morituri creates (per disc) .cue and .m3u files that will break if things are renamed, that should be moved if there's a move, that should be rebuilt if multi-disc albums are joined.
• Morituri guesses the musicbrainz selection. For example, it thought my disc of "A Hard Day's Night" was one of the 13 CD set "The Beatles in Mono". I'm new to beets, but I believe there are settings where it guesses too?
• Morituri gives up when it can't read a CD perfectly. If your disc is scratched, you'll only get the tracks before the scratch.

Again, I really like morituri. Some of the issues above are only issues w.r.t. beets integration. Others are worth working around for perfect rips.

[holms]

Talking about CDripping, I'm for example quite serious about this. Like some torrent trackers only accept certain rips from certain software. For example in mac it's http://tmkk.undo.jp/xld/index_e.html it's opensource so you can build it or use it whatever you like. If I were you I'd stay away from cdripping. this is really unneeded in my opinion. Or it's should be done as scene standarts requires or just don't do it, or make another tool for this if you need those mp3's so much.

[filmor]

Just wanted to ping this, I'm the original author of this issue. Has anyone taken this over yet? Is there any decision on how to approach this?

[sampsyo]

Nope—it's wide open if you'd like to take ownership.

[ArchangeGabriel]

Note that morituri has been forked into https://github.com/JoeLametta/whipper, where devs are actively reworking the whole things. Integrate beets and whipper with each other could be a good idea.