Tag Archives: ripper

tuxrip: If I only had a DVD around here somewhere …

Now I find myself in the same odd situation as I did around the beginning of the year, with a potential DVD ripper in hand, and no DVD to test it.

tuxrip is about a decade beyond its last release. But considering it’s just a bash script that works the strings between mencoder, vorbis-tools, libogg and a few other fundamental libraries, I am not surprised that it still seems to work.


The first time you run it you’ll need to configure it for your machine, and the tuxrip --config wizard will guide you through that. If you make a mistake, I would suggest just hand-editing the .tuxriprc file it creates, which will save you time over re-running the setup.

After that though, I’m afraid I can’t be of much assistance. I see by the home page that there are still a few steps beyond what you see in the screenshot and actually ripping a DVD, to include managing quality settings and a bit more.

I have no doubt that it works, although I wonder if between now and 2005, there haven’t been some advances in both DVDs and encoding that might make tuxrip seem quaint. And I fear it might require a little work to bring it into line with, for example, Blu-ray Discs or x265, just to name one or two off the top of my head.

Already some of it is showing its age: the AUR package installs all the dependencies but you’ll still have to add in mencoder, which isn’t part of mplayer now. (I don’t see a Debian version.)

All that is … assuming it works like it still did. You’ll have to run it through to the end and tell me how it goes. I suppose I should hunt down a real DVD, just for times like this. … 🙄

rubyripper: The options continue to multiply

I should apologize for the gap in communications for a few days this week. I was preoccupied with some personal events, and as luck would have it, I find I am also beset with computer issues. More on that later.

For now, rubyripper is next on the Master List.

2014-04-13-6m47421-rubyripper-01 2014-04-13-6m47421-rubyripper-02 2014-04-13-6m47421-rubyripper-03

We just saw ripit a week ago or so, and while it’s true that there’s only so much you can do with a console-based CD ripper utility, rubyripper seems quite competent.

True, it doesn’t seem to have as many low-level controls as ripit, but there are distinct audiences among computer users, and for some, a simpler, quicker interaction (notice I didn’t say “interface”) is better.

So much as you can see above, rubyripper has options to rip to flac, ogg or mp3, with command-line flag controls manually edited. Suffice to say, if you don’t know what the controls are for lame, you’ll probably just want to keep the defaults. 😉

One thing I like about rubyripper is the default rip location. Without any prompting, rubyripper dropped the resulting tracks into a folder called “vorbis,” which kept them from polluting my home directory. My OCPD thanks you, rubyripper.

abcde is my first-line pick for console CD ripping, but rubyripper has its charms. Following the theme I mentioned with ripit though, sometimes it’s not so much about the overarching program as the underlying support software.

A sad note: It seems the author has drifted away from the project, citing a lack of need to rip CDs any longer, since online services are quicker and easier. Much like I have said several times over, there doesn’t seem to be much call for CD conversion, and I don’t even know how many of my friends own CDs any longer. 😦

It’s the circle of life.

One last bonus with rubyripper: Install ruby-gtk2 and get … a graphical interface!


I don’t see rubyripper in Debian, which is a bit of a shame. So … Arch 🙂 Debian 😦 That could always change though. 😉

ripit: For precise, exacting CD conversions

Among CD ripping tools, I have to say that ripit seems to have its stuff together.


Granted, like some other rippers for the console, ripit primarily relies on some underlying utilities. Depending on your preferences, you can relegate the actual ripping process to cdparanoia, cddda2wav or some other tools.

But ripit has a fantastic number of other options available to it, in addition to the flags passed through to the background utilities. I daresay if you really are keen on controlling the finer points of converting CDs to audio files, ripit might be one of the best choices.

The Arch version, as you can see above, found my optical drive without coaxing, and dashed off to cddb to check the title data.

I did notice that -o flag, which declares a target directory, requires an absolute path, or it assumes you’re ripping to the root directory. By default ripit will leave the target files in your $HOME.

At the end of the day I’m still stuck in an odd place though, in that I don’t have any CDs left and I don’t believe anyone around me still buys them. My homemade backup CD works great with ripit, but after that I’m out of test discs.

But I am sure the worldwide departure from CD-based audio is not over yet. 😉

mp3c: And so it begins

I’m behind the power curve again today, mostly because of oddball computer issues that took up much of my day yesterday.

I got a secondhand HP G60-125NR from a friend for a very decent price, and was astounded when Arch Linux rolled over and barfed when I tried to use it.

Disappearing mouse control. Sketchy video playback and overheating issues with nouveau driver. Even sketchier playback with the proprietary driver, and no framebuffer support. Endless kernel messages about /dev/sdb1 so long as the ums_realtek module was inserted, which spawned endless confusion between sdb and sdc when an external drive was plugged in. Freezing screens and system lockups with x264 videos.

The list goes on. Oddly enough, most of that disappeared with Linux Mint and the nvidia-319 package out of the Mint/Ubuntu repositories. I didn’t plan on running Mint 24/7 on it, but what works is what works.

All that is neither here nor there, since the application of the day (for yesterday) is (was) mp3c.


mp3c made me happy again, just by being itself. 🙂 A fullscreen, command-line application with a good dose of workability.

In-program help screens, extensive options menu, smart enough to find the CD drive and connect to cddb. Good visibility and decent colors, and my only complaint is that it might be out of date.

I couldn’t get it to do any actual reading or ripping, probably because it seeks out cdda2wav, which doesn’t seem to be part of cdparanoia — at least in the Arch version. Maybe it was, once long ago. (Edit: I found it. It’s in cdrkit, cdrtools and dvdrtools. Not cdparanoia, even if mp3c’s home page suggests that.)

I think if I stuck with it long enough I could configure it to use another ripper, and it probably wouldn’t take much more than a substitution for proper tool.

I leave that to later though; I don’t have any CDs aside from the homemade one I use for testing. If you still use them, this might be useful for you. 😉

Now I have to go back to ripping the guts out of Linux Mint. And what’s with these 8200M cards, anyway? Nvidia is out to get me, I swear. … 👿

crip: Picking up what others leave out

I showed cdparanoia a few days ago, and mentioned that it deliberately leaves out access to online databases, for reasons they can explain.

crip adds that back into the scheme, and does a few other things automatically too.

2013-09-26-4dkln41-crip-01 2013-09-26-4dkln41-crip-02

As you can see, it prompts for missing information (because of course, my homemade CD isn’t in the database), genre, and so forth.

I believe it only does ogg encoding, which is what I prefer, so I’m fine with that. If you’re an mp3 (or another format) fan, you might need a different program.

On the other hand, crip will automatically convert international characters, normalize or adjust gain, trim digital silence and some other nifty tricks.

Aside from that, crip has cdparanoia as its backend, so if you’ve seen it in action, much of what crip does will look familiar.

cdparanoia: Nothing to fear

Among CD rippers for the console, cdparanoia might be one of the easiest to remember.


Not just for the clever name, but for the ubiquitous emoticons it uses as status indicators. They’re even listed in the Wikipedia article.

It also strikes me as unusual for eschewing a CDDB interface. I’ll let them explain their rationale for that.

My favorite point of cdparanoia is its ability to analyze a drive for caching and reading behavior, etc.

That’s what you see in the image above; cdparanoia is double-checking the optical drive on this machine, and making sure it’s performing as expected. (It’s fine, in case you were worried.)

Not that I really know what most of that stuff means, but knowing it’s “OK with Paranoia” is good enough for me.

For the audiophiles in the crowd, I don’t have any advice on sound quality. If this does a better job than abcde, or perhaps acripper, that’s something you’ll have to investigate on your own. 😉

avidemux and handbrake: Video, sans video

This may be one of the weirdest long-shot posts I have to offer, but I’m going to do it anyway.

On my megalist of terminal-based applications, I have both avidemux and handbrake.

2013-08-15-v5-122p-avidemux 2013-08-15-v5-122p-handbrake

You might know either as video editing and conversion tools. I’ve used them both at one time or another, and they’re effective at what they do.

I’ve just never used text-only versions, that’s all. 😐

Listing them as console applications or even cli applications might seem like a stretch.

But maybe not. After all, they do both have extensive help flags and man pages, with every combination and detail listed.

I daresay anything you wanted to do in the graphical version — of either program — is possible from the command line. It might take a little longer to set up, but I think it would work.

And for what little I could try them, they both seemed quite functional in spite of lacking a proper graphical interface.

So maybe it’s not as far-fetched as it sounds, to list a pair of video editors as candidates on a video-less system.

Take a look, and find out. Get it? “Take a look?!” 😆 🙄 Aw, come on. Everybody loves a pun. …

acripper: Does its job, in a manner of speaking

I am biased — severely biased — with regard to CD ripping software, and I don’t just mean text-based ones.

I have, in the past, thrown out graphical CD rippers and gone back to abcde, which is what I know and like best.

acripper was new to me, and I will blame my aforementioned bias for my less-than-stellar opinion of it.


For a project that dates back to 2007, I can find almost no information on acripper.

It comes in a single tarball off Sourceforge, with no other web page that I know of. Oddly, that file decompresses into a folder that is misnamed “acriper.”

The question marks continue: The README file suggests the software needs compiled, but the Makefile doesn’t seem to work, and the acripper executable included in the tarball is a bash script.

To complicate things, there are almost no flags available to acripper; no man page, and aside from commented lines in the bash script, almost no guidance on how to make it work.

Perhaps I expected too much; it may be that this was just a once-off project for a programmer involved in bigger and better things, and it has stuck around this long just by virtue of being on some CLI app lists.

And really, there’s not much to complain about considering it seems to do its job. True, there’s not much you can manage and its a rather obtuse (and very slow) ripper.

But it does what it claims, and I guess I can’t complain about that. 😐

abcde: As simple as that

I wish I had known more about some of the console tools for CD access, ripping and playback about six or eight years ago, when I actually still had CDs.

Mostly because some of them are better than their graphical counterparts.

abcde is one I did actually try out a few years ago, when I needed to rip out a sizeable stack of CDs from my former office. It’s still maintained, still available, and still working.


(Sorry for the crowded screenshot. It’s at the lower center of the image. 🙄 )

I liked abcde then and I like it now, mostly for subtleties that make it quick and straightforward to use.

It will scan a disc and search online for track data, without much prodding. If it can’t find what it wants, it can drop you into your $EDITOR and let you manage the information directly.

It keeps a progress bar on the screen with smiley faces to show status. No color, but that’s okay.

It can use cdparanoia or a couple other CD access tools. It can encode to ogg, mp3, flac and others.

And while it’s ripping, it will split out a process for encoding. On a fast machine, that might actualy save you some time. On this one … not much.

I suppose if you keep CDs then abcde might still be useful from time to time. And it’s always aptly named … “a better CD encoder.”