CD ripping

[GoogleCodeExporter]

It would be very nice if beets could import directly from CD to flac or mp3 or 
whatever.

Original issue reported on code.google.com by fil...@gmail.com on 22 Jun 2011 at 9:44

[GoogleCodeExporter]

Preferably, this should invoke some other tool (such as cdparanoia) rather than 
reimplementing the whole ripping process.

Original comment by adrian.sampson on 25 Jun 2011 at 3:33

• Changed title: CD ripping
• Changed state: Accepted
• Added labels: Type-Enhancement, Priority-Medium, Milestone-1.1, Component-Importer

[GoogleCodeExporter]

xld (http://tmkk.pv.land.to/xld/index_e.html) is both cli and gui. maybe cd 
ripping should be implemented as a plugin rather than being a part of beet's 
core code.

Original comment by lnietham...@gmail.com on 26 Jun 2011 at 6:18

[GoogleCodeExporter]

I made a tool for myself for this purpose, and I'm trying to pluginify it after 
my exams (July 5th) :)

Original comment by fil...@gmail.com on 26 Jun 2011 at 8:00

[GoogleCodeExporter]

Great! Good luck on the exams, and let me know if you need any tips.

Integrating with something like abcde (with CDDB lookup turned off) may be 
another good shortcut for good CD ripping.
http://lly.org/~rcw/abcde/page/

Original comment by adrian.sampson on 26 Jun 2011 at 10:08

[GoogleCodeExporter]

just realised that XLD is mac only :( nmy link's not very helpful then.

Original comment by lnietham...@gmail.com on 26 Jun 2011 at 10:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Morituri seems quite nice: https://thomas.apestaart.org/morituri/trac

A command line tool, that aims for EAC-like perfection. It'd be great to be 
able to do an "Add perfect rip to database" in beets, which invokes morituri 
and does all the tagging and naming afterwards.

Mhhh....

Original comment by amselfelder on 28 Jun 2011 at 8:40

[GoogleCodeExporter]

I really wonder if we should do this. Why not just let people rip their stuff 
and have them run a `beet import` over the the output folder of their ripping 
program?

My main issue with this would be that we'd be tying in beets with a very 
specific way of doing rips, tied in to that exact piece of software. Beets is 
supposed to be a library manager and it's pretty good at being exactly, and 
just, that.

Second, people rip stuff in a lot of different ways. My rips happen in FLAC 
which then get transcoded to 4 formats and the format I give beets to import is 
V0. It's going to be very difficult and quite laborious to accommodate every 
audio-freak's own very special unique way of doing this which is why I think 
this should not be tied into beets but left with the end-user to handle with 
their tools as they see fit.

Though in plugin-form, I guess anyone can just enable/disable it.

Original comment by daniele.sluijters on 28 Jun 2011 at 9:45

[GoogleCodeExporter]

Much like the previous commenter I believe beets should do one thing and do it 
really well (it's well on its way!). Perhaps a plugin for morituri that can 
update the beets database as it encodes an album would be beneficial similar to 
the plugin for MPD that is available now. I can even envision a plugin that 
invokes beets to tag an album, although I'm not sure of its usefulness given 
that most taggers, EAC specifically, tag albums as they rip given the available 
data.

Original comment by David.Ve...@gmail.com on 28 Jun 2011 at 9:56

[GoogleCodeExporter]

Morituri is a very nice find. It looks ideal.

I agree that the complexities of CD ripping should definitely be left to 
another program. (I have no desire to get involved in the myriad ways that 
people like to rip stuff from CDs.) We have the luxury of possibly doing 
nothing, as the solution you described (rip using any tool and then run "beet 
import") will always work.

But we can also do something very simple to streamline the process -- even just 
a "beet rip" command (provided by a plugin, of course) could runs Morituri with 
user-specified command-line flags followed by an import and cleanup of the 
intermediary files. No need to get involved in what those command-line flags 
mean -- just pass them along (and provide a sensible default).

Original comment by adrian.sampson on 28 Jun 2011 at 11:32

[GoogleCodeExporter]

The benefit I see in combining beets and with a ripper(-plugin) is that tagging 
is more centralized. Also I'd really like a once-and-for-all tool to handle my 
library, and the most common way to expand it is (for me) to throw a cd into my 
PC.

Original comment by fil...@gmail.com on 29 Jun 2011 at 7:27

[GoogleCodeExporter]

We could perhaps also consider an alternative route, but it is a bit more 
complicated. Instead of tying in beets with whatever program we could provide a 
generic rip-interface which could then be configured by the user to call 
whatever program with the necessary parameters, a bit in the spirit of the 
"external commands" idea.

Original comment by daniele.sluijters on 29 Jun 2011 at 8:34

[GoogleCodeExporter]

Original comment by adrian.sampson on 19 Feb 2012 at 10:46

• Removed labels: Milestone-1.1

[untitaker]

Do not comment here, but on sampsyo/beets#139