Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
BSD Operating Systems

Ripping MP3s in BSD 28

Posted by michael 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."
This discussion has been archived. No new comments can be posted.

Ripping MP3s in BSD More

Ripping MP3s in BSD

Comments Filter:
  • Bring up Konqueror, put in an audio CD, and type "audiocd:". Then drag your MP3s out of there!
  • 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 !
  • ...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 [nostatic.org]).

  • My choices... (Score:3, Insightful)

    by Thornae ( 53316 ) on Saturday September 22, 2001 @11:43AM (#2334388)
    ... are dagrab [tiscali.it] to rip (mainly coz cdda2wav [fokus.gmd.de] was playing up), oggenc [vorbis.com] to encode, and the very friendlyGrip [nostatic.org] 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.

  • use rippit.pl! (Score:3, Insightful)

    by Bigbambo ( 8887 ) on Saturday September 22, 2001 @12:28PM (#2334618)
    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.
    • 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.

  • "BSD" (Score:1, Informative)

    by little_fluffy_clouds ( 441841 )
    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.
    • "BSD" is merely a shorthand. It's rather like saying "Linux" instead of "GNUlix/LiGNuX", or whatever the official name is this week.

      • Re:"BSD" (Score:2, Informative)

        by little_fluffy_clouds ( 441841 )
        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.
        • 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.

  • Here's how I do it (Score:2, Informative)

    by realdpk ( 116490 )
    Need to have dagrab and lame installed, and possibly some other ports. My scripts can be found at: mp3 scripts [cgi-pros.com]. 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.

Slashdot Top Deals

Mater artium necessitas. [Necessity is the mother of invention].

Close