HOWTO: Install Rubyripper on Ubuntu

[ghindo]

Rubyripper 0.5.7 is out:

---------0.5.7 RELEASE------
* a fix for discs that start with a data track
* a fix for checking the available space for some languages
* a few fixes for the OpenBSD platform
* fix a typo in the logfile when errors were corrected
* don't replace bracquets in filenames -> []
* fix a typo which resulted in a directory not containing the album name
* allow multiple encoding threads once again

[ghindo]

Looks like there's been some progress upstream in packaging Rubyripper. With any luck, before too long I'll be leaving this guide by the wayside and authoring a new one - HOWTO: Configure and Use Rubyripper

[meocuchad]

I really appreciate you making this install guide, ghindo. You made it painless as could be for a Linux newbie like me. Thanks a million!

[ghindo]

I really appreciate you making this install guide, ghindo. You made it painless as could be for a Linux newbie like me. Thanks a million!

No problem! Glad it helped you out

[warpasylum]

Thanks man. Worked fine for me on Jaunty 64-bit.

[Artemis3]

This ripper looks promising, one of the few that won't destroy japanese characters in tags, cues or filenames.

Bugs with the 0.5.7 version:

You can't use the "RIP CD to single file" preference, so no single flac+cue (cdparanoia seems to hang).

Using 2 encoder threads should stick to encoding, not ripping. I don't think its healthy for the drive to spawn 2 cdparanoia processes which are twice reading each track...

Grip was smarter in this regard, you could have it rip tracks and start encoding the tracks already ripped in parallel.

Will be very nice when the AccurateRip feature is added.

[ghindo]

This ripper looks promising, one of the few that won't destroy japanese characters in tags, cues or filenames.

Bugs with the 0.5.7 version:

You can't use the "RIP CD to single file" preference, so no single flac+cue (cdparanoia seems to hang).

Using 2 encoder threads should stick to encoding, not ripping. I don't think its healthy for the drive to spawn 2 cdparanoia processes which are twice reading each track...

Grip was smarter in this regard, you could have it rip tracks and start encoding the tracks already ripped in parallel.

Will be very nice when the AccurateRip feature is added.

Be sure to file those bugs with Rubyripper so these bugs get fixed!

[yahoo]

Thanks ghindo, easy install on jaunty 9.04. Rips just as I like.
Cheers
yahoo

[sjalloq]

Hi there,

I haven't been able to find any official support forums for rubyripper so decided to post on this thread. Please let me know if I should move it somewhere more appropriate.

I have just installed the 0.5.7 CLI on my Ubuntu Server 9.04. I'm running 32-bit on an old AMD Sempron.

As soon as rubyripper starts to rip it exits. Are there any known bugs? Is there a way of getting more verbose debug output?

Thanks.

STATUS

Ripping progress (0 %)
Ripping track 1
Expected filesize for track 1 is 44753900 bytes.
ubuntu-server:~>

[codedash]

Looks like there's been some progress upstream in packaging Rubyripper. With any luck, before too long I'll be leaving this guide by the wayside and authoring a new one - HOWTO: Configure and Use Rubyripper

Is it that difficult for ubuntu developers to make the first move and add some new packages in the repos? Why debian must always include the packages first so we can benefit? I dont like this.