Files
hpr-knowledge-base/hpr_transcripts/hpr1703.txt
Lee Hanken 7c8efd2228 Initial commit: HPR Knowledge Base MCP Server
- MCP server with stdio transport for local use
- Search episodes, transcripts, hosts, and series
- 4,511 episodes with metadata and transcripts
- Data loader with in-memory JSON storage

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-26 10:54:13 +00:00

323 lines
20 KiB
Plaintext

Episode: 1703
Title: HPR1703: Open Source CD Rippers
Source: https://hub.hackerpublicradio.org/ccdn.php?filename=/eps/hpr1703/hpr1703.mp3
Transcribed: 2025-10-18 08:01:25
---
This is HPR Episode 1,703 entitled Open Source CD Rippers.
It is hosted by first time host Kevin and is about 26 minutes long.
The summary is, Kevin takes a look at a variety of CD ripping software available on Linux.
This episode of HPR is brought to you by an honesthost.com.
With 15% discount on all shared hosting with the offer code HPR15, that's HPR15.
Better web hosting that's honest and fair at An Honesthost.com.
Hello, hello and welcome to another episode of Hacker Public Radio.
My name is Kavi and whilst this isn't my very first appearance on Hacker Public Radio,
it is my first attempt at flying solo, so this is a totally new experience for me.
For my first ever episode, I thought I would do a brief round-up of some CD ripping software,
Open Source of course, that is available on the Linux system.
Throughout this episode, I hope to actually look at a variety, so I'm going to look at some dedicated
rippers, graphical and command line, and also take a look at a couple of complete audio
suites, which actually include the ripping abilities, which want to make a brief comment
about each and just compare them. Of course, what I see is very subjectionable.
I mean, a lot of this is down to personal taste, but I'm going to try and give my opinion
and be as balanced as I can.
Now, if you're a regular listener to my show Tux Jam, then you'll also know that I'm a big fan
of Creative Commons music, and I'm not letting you guys off with no music in this episode either.
Throughout the show, we're going to get to when to have some music tracks from 20-pound
sounds and blowing up bridges, so that's look forward to.
But first of all, let's get straight on and take a wee look at the CD ripping software.
This was all ripped on my Debian system using Matty desktop environment.
Nothing too major about the system, it's not cutting-edge,
it certainly isn't bought from the line either.
It's 8GB quad-core i5, 3.3GHz, so that gives you an idea over the system,
just so that you can actually get an idea over what it is I was using.
Now, so to start with, we'll look at sound-ducer, which is very familiar to anybody
that's used no more GTK desktop, as it varies often the default CD-ripper.
And how does it look? Well, looks okay, it fits in.
It's a nice pop-up GUI, it lists all the tracks.
One of the good things about it was that it found my CD information straight away.
The CD information, the CD that I'm not going to promote the artist,
because I didn't use Creative Commons CD purely because most of the time,
CD-rippers do not find these on an internet databases.
So, I used a CD that was 11 tracks long and it was 33 minutes in total audio time,
so that gives you also an idea.
So, it found the tracks and the information straight away, no problem there.
One of the things that I wasn't so keen on was this isn't comparison to the other GUI one,
which I'm going to review in a minute.
And that was when you were ripping, it wasn't entirely obvious that you were actually doing anything.
It wasn't until you noticed that some of the buttons started to get greyed out.
So, and there's a small progress bar down the bottom.
So, overall, I wasn't too impressed with that part.
I would rather be a bit more obvious.
What are the nice features I did like about, I do like it sound juicer,
is that you can play the tracks before you actually rip them.
Now, obviously, when you're actually ripping, you're no longer available, the buttons greyed out.
Once again, it doesn't come up with a pop-up or anything at all intrusive when it's actually finished the ripping.
It simply basically continues as paranormal.
The only difference that you'll notice is that the play button is no longer greyed out.
So, overall, I had a good experience.
The time to rip was 8 minutes and 53 seconds.
I would personally have liked to have seen something that said a message of job done as an option.
I mean, didn't even all seem to give you that option.
But overall, I was quite happy with it.
By default, it ripped the tracks into a first of all folder with the artist, then the album name.
So, it was actually two folders that created one side the other.
So, that was sound juicer.
And again, not really probably going to be a big surprise to many people.
Most people I imagine, if you've tried Linux and you've tried the NomDesk top or a GTK desktop for that matter,
have probably used sound juicer.
So, onto a sander.
And this is actually my default soundripper.
And it looks quite similar to sound juicer, to be perfectly honest.
It's a nice, rather unspectacular GUI.
And once again, found the CD information instantly.
By default, this time, the rips are put onto a folder.
That's first of all, it's like a double ballad name.
It's the artist followed by the album.
So, artist followed by album.
The total time to rip this time was 8 minutes 21 seconds.
So, slightly faster.
Now, we've been faster, but nothing over the top.
The one thing I do like about a sander, although a lot of people may say,
no, no, I don't like this two-in-thrusive, is when it's actually ripping,
it provides a wee pop-up window in the centre of the GUI,
you can move this about independently.
And it says it gives you the progress of each track plus the overall progress.
And pretty much you can't really do anything with a sander unless you stop it.
And if you want to see the complete or you stop it, the wee window closes
and the shah job done, notification pops up.
So, I quite like that.
But then again, that's all down to personal taste.
Some people might find that a wee bit intrusive.
So, overall, not really an awful lot to compare between the two.
Both of them did the tracks, except all these were being ripped to og.
So, both of them did the tracks in roughly the same time.
So, 8.53 for sound juicer, 8.21 for a sander.
I think I'm going to give it a wee break here.
And you might notice a slight theme with the music here today.
The first track is rip it up by 20 pounds sounds.
I
want to rip it up, slow it back at you.
On his words that you wrote because it told me many things.
I want to rip it out of now.
I want to rip it out of now.
I want to rip it out of now.
I want to rip it up, slow it back at you.
On his words that you wrote because it told me many things.
I want to rip it out of now.
And a nice rock there from 20 pounds sounds.
If you like the sound of that, then you can visit them at 20p20lb.net.
And the first one we're going to look at is bash burn.
To be honest, I hadn't actually ever considered command line ripping before.
It's just not been something that sound juicer has always been installed by default.
A lot of this was I've tried.
I discovered a sander for reviewing an episode of tux jamma happened to like it.
So, it's just something I've never really done.
My first attempt at this, it worked rather well, now I must admit.
For something that was a command line only interface, it was very, very easy to use.
Nicely laid out.
There's one big problem I had with it and that was I was a bit nervous starting it.
Purely because there is almost no documentation at all.
If you go to the website, there is some basic documentation on how to install it.
And then it says usage coming soon.
So this led me to be a bit nervous.
However, this was totally unfounded as it was very straightforward to use.
Now, in saying that, there was a wee bit of setup to do.
Once we got the setup done, that was fine.
But there was a wee bit of setup.
So initially it gave me an error about not having been used before my system
and then it created a file called dot bash burn RC.
Now that was okay, but then I had to go hunt down that file in the folder
because when I actually tried to rip music from the first time,
it told me there was no CD drive.
No, it could not find my CD drive.
So that was rather annoying.
When I eventually found the bash burn RC file,
I found it located in the home folder.
It's just a dot bash burn RC was a hidden file.
That reader rather annoyingly was not clear.
So I first of all had to go and put down dev dot SR0 in my case for the CD.
But for the CD drive and the other thing that had to be done was,
well sorry, it didn't have to be done.
But what I didn't notice initially was that it ripped all the music tracks
to a folder called burn and it puts it in the TMP file by default.
No, not too much of an issue for me because I happen to notice it.
But you can change that in the dot bash burn RC.
However, this would be very annoying if you had done a number of tracks
or a number of CDs, not notice it had gone into the TMP file
and then rebooted your computer.
Or switched it off, come back to the next day because all those files would be gone.
So personally, I think that's a rather annoying place to be putted by default.
But that's what they've chosen and it is very easy to change.
It's just not very obvious.
This is where I really would like to see some better documentation on this.
How did it go?
Well, as soon as I put it in, it gave me a list.
Pick your option, do you want to extract from rip from CD,
which format you want to rip in?
It was all very, very clear.
But then it came to actually ripping it.
This was the kind of slight problem I had here.
Because it said, what tracks do you want to rip enter for default?
So I assumed enter would just rip all tracks.
No.
I said enter, it took me back to the first menu.
Okay, that was rather annoying.
So then I decided, let's try typing all in, typed in all unknown command.
Nope, couldn't do that.
So what I eventually had to type in was I had to put in one through eleven.
Now, this time this ripper did not find any audio information.
And the rather annoying thing was that I had to input each name manually.
Now, it told me said, you know, we have support symbols, etc.
Please put in your name for track one, track two, track three, track four, track five.
So that was I thought a bit of a rather cumbersome way of doing this.
However, one thing before we write this off entirely,
the rip time with this was phenomenally good.
Four minutes, 13 seconds.
So less than half of the time with the other two.
That was really was good.
The biggest problem was, of course, fiddly.
Well, initially fiddly said of that so initially.
But if you're a very slow type or you can be bothered typing in everything,
then it's not quite so handy.
I think that this would be excellent if you're only wanting to pull that maybe a track or two off an album.
Not probably the thing that I would recommend for ripping from ripping a whole CD collection.
Because I think you'd spend enough a lot of time typing out.
Hey, if you like typing out and fired on that might be that might be ideal for you.
So, overall, given that was my very first time ripping from the command line,
I thought, yeah, that was okay.
Then I found discovered another thing and it was called C-Rip.
Now, well, it was either C-Rip or C-Rip, but I prefer having C-Rip.
I found it very, very easier, easy to set up.
Just loaded it up, no error messages, and it found the CD straight away.
Now, this one did not ask me which format it wanted to rip to.
But thankfully, it ripped to Og, which was what I was wanting.
One of the things that was very nice about this was that it found all the CD information.
And put these now.
The way to put the tracks...
Wait, put the tracks.
Well, it put everything into Home Fold.
It didn't print a separate individual folder.
It put it into Home Folder.
And put it as Artist Name,
album name, track number, track title.
So they were rather long and quite cumbersome lines, but I think you can't change that.
I just didn't delve too deep into it.
Now, for a command line, especially given the...
For a command line tool, especially given how good Bashburn was,
I expected this to be all.
This will be the answer I am now.
That's it, I've understood.
Well, I was rather disappointed with the rip time in this.
I thought it would at least be to the GUI tools.
But sadly, the time to rip was 9 minutes, 6 seconds.
So that, combined with the rather ugly weight percentage of files,
I just thought, no, it's probably not worth it.
That's just my personal opinion, but the fact it took longer than the GUI did,
kind of leave me a bit disappointed.
But overall, compared to the fact that I had nothing to go on,
I didn't know what I was going to be expecting.
I didn't know how easy or difficult it was going to be.
I must admit, they were both very easy.
And this one is a bit better documented online that our manuals
and setup tutorials, etc.
Not that this one needed it.
I mean, the very what, this one I expected,
because there was so much documentation for it to be quite awkward,
but it wasn't at all.
So overall, that was my first experience of command line CD-rippers,
and I was very impressed.
Now, before we take a look at my final thoughts
and also take a look at the different audio suites,
we're going to have a wee listen to some more music,
and if you're following us sleep,
and this will certainly wake you up,
this is blowing up bridges,
and the track is grip it and rip it.
I like to take it the most,
you get it high on the bus,
it's come on, turn on your call pass,
it doesn't get to be heard,
it doesn't get yours,
it doesn't stop to cast.
I like to take it the most,
you get it high on the bus,
it's come on, turn on your call pass,
it doesn't get to be heard,
it doesn't get yours,
it doesn't stop to cast.
It doesn't get to be heard,
it doesn't get yours,
it doesn't stop to cast.
I like to take it the most,
you get it high on the bus,
it's come on,
turn on your call pass,
it doesn't get yours,
it doesn't get yours,
it doesn't get to be heard,
it doesn't get to be heard,
it doesn't get to be heard,
it doesn't stop at cast.
Everybody knows what's with that as well,
Hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey
hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey, hey
Yeah but a punk there by blowing up bridges and if you like that unfortunately they don't
have enough of a lot of presence on the web. I'll direct you link soles in the show notes
and indeed for all the tracks and software that's been reviewed in this episode, links
in the show notes all that I can find by blowing up bridges is four tracks on their bandcamp
page so rather disappointed by that because I quite enjoyed it I would like to hear a wee bit
more but maybe the shall be a wee bit more to come yet. Now before we wrap this up I want to think
let's answer the question is it worth having a dedicated ripper when you might have a full audio
suite which can do it anyway it's in the options right let's have a consideration then.
So I looked at two options for this first one is one that just a bit everybody I know seems to
have this installed and it's one of the first programs they install and that is VLC. VLC it's a great
audio and video player purely because it plays everything you can throw at it you can do whatever
you want and it plays it it's great. Now how did it fare? Well it rips tracks really well from CD
however it's one at a time you can select more than one you can tell to rip the whole track but
I had problems in the naming aspect of it didn't seem to matter what I what options are tried to do
do the it just kept on trying to rename the file now somebody online pointed me to VLC's documentation
and there are supposed to be you can put some different ones in so it will supposedly change so
for example according to its own wiki if you put in dollar n it's a track number if you put
in dollar t it's a title so I tried this no didn't seem to matter if I put in dollar t dollar space
of space dollar n dollar whatever all did was save the track to that title and what a problem
is what it would do is it would rip the first track and then go back and save over it save over
it save over it save over it and I tried for a good two hours to get this one again I just couldn't
and to be honest I just thought no this isn't worth it so yeah fine for a dripping maybe one track
or a couple of tracks I don't think I would like to rip my entire media library that way and of
course you're the problem is you had to enter the value in manually so you you know it didn't
automatically like a sunda or sound juicer or even see rip it did not automatically name it to
the song you had to manually put it in not that there was any wrong with the quality I was really
pleased for that and the speed it seemed very fast for the one track but I just could not get it
to rip the entire album in one go and that's what I was aiming for now the other option I looked
at was rhythm box now rhythm box is not something I tend to use I must admit I've used it a few
times and I do find it handy for things like browsing magnitude and gemendo but it's not
something I ever use so I tried it out it's very quite straightforward when you put the CD in
there's a rip button appears you can set out you can lay it out in different ways whichever
you want it click the button and it worked no problem but but we got problem this thing is a beast
of an audio suite and it took 13 minutes and four seconds on this now you know when you compare
that the second slowest is C-Rip with nine minutes and six seconds you know four minutes is an
awful lot if you are going to be ripping maybe 200 CDs so in the answer to the question yes you
can get a suite that does everything but in good old Linux philosophy I prefer to have something
one piece of software that does everything where it does one thing really well rather than a big
behemoth that does everything so like again at the end of the day it's subjective you may totally
agree with me you may say nope don't agree we are talking heavy but anyway that's what comments
are for and that's the beauty of Linux you have choice you have variety so if you like this show
then please do leave a comment or even if you didn't like it if you have any comments leave a
comment on the the page if you wish to get in contact me you can it's tuxjam at unseen studio.co.uk
and if you like this and you like the combination of tech talk on music then please check out the
tech the tuxjam podcast which is you should release now monthly ruling cycle and I do that with
Andrew who's also known as McNally who I think has done more than his fair share of HPR so hopefully
this although this is my first hopefully it is not the last time I'll do this and I shall catch you
again on the next time I do either an episode tuxjam or an episode of HPR
you've been listening to hecka public radio as hecka public radio dot org
we are a community podcast network that releases shows every weekday from Monday through Friday
today's show like all our shows was contributed by an HPR listener like yourself
if you ever thought of recording a podcast then click on our contribute link to find out
how easy it really is hecka public radio was founded by the digital dog pound and the
infonomicom computer club and is part of the binary revolution and being revved of calm
if you have comments on today's show please email the host directly leave a comment on the website
or record a follow up episode yourself unless otherwise stated today's show is released on
creative commons attribution share like 3.0 license