Slashdot Mirror
Ripping MP3s in BSD
LiquidPC writes: "ONLamp.com's Big Scary Daemon Section has a new article
on how to rip MP3s using tools found in the FreeBSD ports tree."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
Bring up Konqueror, put in an audio CD, and type "audiocd:". Then drag your MP3s out of there!
A Government Is a Body of People, Usually Notably Ungoverned
... are dagrab to rip (mainly coz cdda2wav was playing up), oggenc to encode, and the very friendlyGrip for the frontend. I highly recommend Grip, whatever else you use for the actual back end stuff.
/usr/ports/audio, installed dagrab, and was up and ripping within 5 minutes.
Basically, I was feeling too slack to find out why cdda2wav was giving me grief, so I had a quick squiz thru'
God, I love ports.
|>
Here be Dragons
In ports there is this little perl script called rippit.pl. It glues together a cdripper, and encoder and a cdda program. You can even chose which ripper/encoder you want to use. I do tosha and lame.
***There is no point in asking, you'll get no reply***
"BSD" is merely a shorthand. It's rather like saying "Linux" instead of "GNUlix/LiGNuX", or whatever the official name is this week.
A Government Is a Body of People, Usually Notably Ungoverned
These two cases are not the same. Yes there are many Linux distros, but they all use the same kernel and mostly the same userland, the major exception being the binary package tools. The BSD's do NOT use the same kernel (BIG differences), and the userland is often significantly different too. Only someone who does not use the different BSD versions would call one of them in particular 'BSD'. When FreeBSD 4.4 just came out, at least Slashdot did not report that 'BSD 4.4' is out. So keep *that* up.
Let me put it this way - articles written about FreeBSD or OpenBSD are of no interest to me, as the content is often irrelevant to what I use (NetBSD). So it is an incorrect shorthand, at best. If you are talking about FreeBSD, call it FreeBSD. Daily Daemonnews uses the term BSD correctly (which is hopefully as I have here). Slashdot does not in mant cases.
What were the skies like when you were young?
And the userland can differ very significantly. Compare Slackware to Debian to Redhat. Then look at all the microdistros based on busybox.
A Government Is a Body of People, Usually Notably Ungoverned
I think your sense of semantics is getting in the way of your sense of proportion.
If the topic were something else, like "old versus new style init scripts in BSD", then you would be on target with your complaint, since FreeBSD and OpenBSD don't have the new style init scripts yet. And if the topic were "compiling the BSD kernel to support SBLive", then you would also be correct, since compiling the kernel and setting up sound will be quite different under each OS.
But the topic was not OS specific. It was "Ripping MP3s in BSD". I don't give a rip about cdrecord versus burncd, because you don't have to burn a damn thing to rip an audio track! lame works equally well under NetBSD and Open BSD as it does under FreeBSD.
If I'm talking about an OS specific topic, then I will use the specific OS name. But if the topic is general to ALL BSDs I will use the term "BSD" as a shorthand for "FreeBSD, NetBSD, OpenBSD"; if the topic is general to all free unices I will use the term "freenix" or "free unix" as shorthands for "FreeBSD, NetBSD, OpenBSD, Linux, GNU and variants"; and if the topic is general to all unix and unix-like systems I will use the term "unix" to refer to all of them, and damn the Open Group's trademark.
A Government Is a Body of People, Usually Notably Ungoverned
Need to have dagrab and lame installed, and possibly some other ports. My scripts can be found at: mp3 scripts. When I want to rip a CD, I pop it in and simply run "./rip" from my mp3 dir. It takes care of the rest, including CDDB-based naming.
No warranties or anything.