Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ripping MP3s in BSD

Posted by michael on from the not-as-think-as-you-easy-it-is dept.

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."

28 comments

  1. audiocd: by Arandir · · Score: 2

    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
    1. Re:audiocd: by Anonymous Coward · · Score: 0

      how to use dogg forbis?

    2. Re:audiocd: by Arandir · · Score: 2

      Easy, just drag your Vgg Oorbis files out of Konqueror! Of course, you need to have Dogg Vorbis installed before building Konqueror.

      It's pretty cool, and I have no idea why KDE hasn't explicitely documented this anywhere.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    3. Re:audiocd: by Anonymous Coward · · Score: 0

      Maybe because many people write off k-anything as being moron-ware. But that's what happens when you market something to morons.

  2. Which the best way to record audio cd's ? by guilherme · · Score: 1

    Hi !

    How can I record directly audio from my cd reader to my ide recorder ?

    I read burncd but I can't find my answer ...

    Thanks !

  3. Not to be pedantic... by rweir · · Score: 1

    ...but there is no such thing as 'ripping mp3s'. You rip the tracks of a CD, then you encode it with an encoder. These a two very different processes, which are better accomplished (IMHO) by using different tools (perhaps linked using the excellent Grip).

  4. My choices... by Thornae · · Score: 3, Insightful

    ... 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.

    Basically, I was feeling too slack to find out why cdda2wav was giving me grief, so I had a quick squiz thru' /usr/ports/audio, installed dagrab, and was up and ripping within 5 minutes.
    God, I love ports.

    --
    |>
    Here be Dragons
  5. use rippit.pl! by Bigbambo · · Score: 3, Insightful

    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***
    1. Re:use rippit.pl! by docstrange · · Score: 1

      I've been using ripit.pl for a long time. It's excellent, who needs those bloated gtk programs running in the foreground when you can do it all from a command line. CDDB included.

      --
      Remember that you are unique, just like everybody else.
  6. "BSD" by little_fluffy_clouds · · Score: 1, Informative

    It would be really nice if the slashdot crowd stopped using "BSD" to mean one of the *BSD's. This article is about FreeBSD, hence the title should have said "FreeBSD". They are not the same, sometimes they are not even similar. A relevant example to this topic - the process of ripping on NetBSD is not the same as FreeBSD, as NetBSD treats all IDE drives as SCSI, hence one can use tools meant for SCSI drives on and IDE system. The same with burning as well, eg FreeBSD have 'burncd' or something in their userland specifically for IDE burners, but NetBSD can use the 'cdrecord' package on an IDE drive (which only supports SCSI burning).

    So, I implore you - specify the 'BSD' you are talking about - trust me they are not at all alike in many respects.

    --
    What were the skies like when you were young?
    1. Re:"BSD" by Arandir · · Score: 2

      "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
    2. Re:"BSD" by little_fluffy_clouds · · Score: 2, Informative

      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?
    3. Re:"BSD" by Anonymous Coward · · Score: 0

      Yes there are many Linux distros, but they all use the same kernel

      No, they do not.

      RedHat ships with a different kernel than Slackware and both of the code differs from MkLinux.

      If you were more familiar with "Linux" than NetBSD, you would know that.

    4. Re:"BSD" by Arandir · · Score: 2

      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
    5. Re:"BSD" by Arandir · · Score: 2

      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
    6. Re:"BSD" by little_fluffy_clouds · · Score: 0, Flamebait

      The topic IS OS specific. It is mostly about using ripit, a perl script, on FreeBSD. It apparently can be installed from ports. NetBSD has 'ports', but it refers to the different archs that can run it. Ok, so I let that one slide and I s/ports/pkgsrc. Ripit is not in pkgsrc. I could perhaps get it working and pkg it up just so I could use that article ? No, I'm much more likely to use cdparanoia or something which is already in pkgsrc. But the article does not mention cdparanoia.

      And the other little things. The cd device is different under between FreeBSD and NetBSD, so if I tried to follow his instructions, I would not get very far.

      So, it's value to me as a NetBSD user ? Not a lot. The article may as well just be titled 'Ripping MP3s in UNIX' for all I care. A suggested title would be 'Ripping Audio under FreeBSD using Ripit'.

      Also, you say FreeBSD and OpenBSD don't have the 'new style' init scripts 'yet' ? I assume you refer to /etc/rc.d on NetBSD 1.5 and greater, and if so - it has already been established that OpenBSD at least will not be getting them. Unless things have changed since Theo last said 'no'.

      --
      What were the skies like when you were young?
    7. Re:"BSD" by Anonymous Coward · · Score: 0

      This argument is pathetic. Continuation of this argument only serves to show idiocy on the behalf of all involved parties.

  7. When the same is done for "Linux" by Anonymous Coward · · Score: 0

    You complain that FreeBSD != NetBSD != OpenBSD. Fine, you can have that point. Now, what about how RedHat Linux is not the same as GNU/Debian and they are not the same as Slackware, etc ad nausium for the 190+ linux versions.

    When Slashdot (A "linux" centric site) starts making sure to point out how fragmented the Linux world is, and how one "linux" is not the same as the next, then they can move onto worring about BSD.

  8. ripenc by Anonymous Coward · · Score: 0

    Anybody else use ripenc?

  9. Re:*BSD is dying by aphor · · Score: 1

    Anonymous Coward forgot to mention Mac OS-X.

    What is the motivation for expressing this opinion? What is dying in this context? What is sales to a Free operating system?

    If you are inclined to agree with this guy's post, then you will be interested to look at Microsoft's sales numbers and their prospects of growth without booming PC sales. As for the facts, I won't pretend to nail down hard numbers based on Usenet posts.

    Even though this is flamebait, and the author is a troll, once you think through the underlying question(s) and the possible answers and corrolaries, you will learn something.

    The people who think in terms of sales and users as the driving force behind free software are very interested in killing off the BSD family.

    --
    --- Nothing clever here: move along now...
  10. Re:*BSD is dying by skbenolkin · · Score: 1

    The people who think in terms of sales and users as the driving force behind free software are very interested in killing off the BSD family.

    Interesting point. Think of well-known free *NIX distributions. Now think of who doesn't fit into the above category (hint: publicly traded companies do, or they cease to exist). Off the top of my head, here's my list (in no particular order):

    • Debian
    • Slackware
    • FreeBSD
    • NetBSD
    • OpenBSD

    The irony for the majority of the above projects is that, despite the dangerous fact that they use that "not-RMS's-favorite(TM)" license, they and their loved ones have not (yet) had terrible things happen to them at the hands of bloodthirsty capitalists.

    --
    "Frederick, is God dead?" --Sojourner Truth
  11. Re:*BSD is dying by Anonymous Coward · · Score: 0

    ...they and their loved ones have not (yet) had terrible things happen to them at the hands of bloodthirsty capitalists.


    You couldn't be more wrong. In fact, many of us have felt the warmth and generosity of the so called "bloodthirsty capitolists". Why do you think Marshall Kirk McKusick is a multi-millionare? Try this on for size - he wrote an FS, Sun liked it, used it, and decided to repay him. It's only when you start to play nasty (GPL) that people spend all their time being worried about getting ripped off.

  12. Here's how I do it by realdpk · · Score: 2, Informative

    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.

  13. Re:*BSD is dying by skbenolkin · · Score: 1

    Read my post again. Now is it pro-BSD or anti-BSD? I think this may help.

    --
    "Frederick, is God dead?" --Sojourner Truth
  14. It is so amusing by Anonymous Coward · · Score: 0

    this troll shows up on every BSD story, and there's always at least one biter!