Hi,

The new version 0.4.2 of Rubyripper is just released. Changes are:

* kill a memory leak, reduces memory use a lot with long tracks
* removed the ruby-libglade2 dependency (ruby-gtk2 still needed)
* implemented a dialog for the case that an output directory already exists
* license included as a file: the GPL-3 License
* changed location of settings file to $HOME/.rubyripper/settings
* saving of (edited) freedb metadata to local disk $HOME/.rubyripper/freedb.yaml
* added a .desktop file for auto inclusion in for instance the KDE menu
* a lot of small fixes

For bugs, ideas, wishes, etcetera, please file an issue at http://code.google.com/p/rubyripper/
You can also download the release from there.

Kind regards,

frodoontop

thanks!

i'll try to package this asap for rarewares/debian


later

cool bananas - thanks

fänx!

I have a few questions.

Why have Cdparanoia set by default to "-Z", that prettymuch eliminates all extra anti error features that sets Cdparanoia aside from the other one. I know some drives dont work with that option because of caching, but as far as im aware it doesnt cause any issues either, just doesn't work.

Will there by chance be any issues with removing -Z and just adding -X ("-X" should cancel the ripping of any error it couldn't read perfectly, and by removing the "-Z" command, the default amount of retries for a sector is like 20)

That Matched with your md5 checking by ripping them twice should provide top notch error prevention.


Also, how do you set Offset in Rubyripper? the offset box only seems to go into positive numbers, is that used for something else? Or is that something you need to do manually in the Cdparanoia box by adding a text switch?

The default is set to '-Z' to prevent any trouble with drives that caches data. If a drive does cache data, cdparanoia corrections are counterproductive.

If you're sure that you got a drive that doesn't cache, you can try to remove the '-Z' option. You will gain a slower ripping speed and with damaged discs perhaps a different result. If it's better or worse I can't tell, you should test for yourself.

As I see it, you should only try to disable '-Z' if your disc is reported to have troubles with reading and Rubyripper doesn't lead to correct results.

Using '-X' is a personal preference. I'd rather like an (probably) inaudible difference than an audible unexpected end of a file. Have it your way.

The offset thing is fixed in svn and will be in next release. You're now allowed to set negative numbers in the gtk2 gui.

Wouldn't adding -Z pretty much be redundant since the principle in detecting errors is the same anyway?

Does cdparanoias "Paranoia" options (that are disabled by using -Z) really do the Same thing as the security double ripping/md5 checking of rubyrip?

I mean i dont know too much, but isnt it possible for there to be an error on a disc that cdparanoia could identify and try to reread till it gets the right info, but if not allowed to, would rip the same wrong info twice, and then Rubyripper wouldnt detect it?

Just to be clear though, removing -Z wont do anything sept add more redundancy (length too ) to the Rip right? Like it wont effect quality or conflict with any other aspect of RubyRipper?

[edit]
hmm, was gonna say the SVN rubyrip diddnt work with negative offsets, but seems its my drive, not able to do negative offsets on the first track :/

May be a small request, but it would really be great if Rubyrippers ID3v2.3 tag feature could be updated to ID3v2.4 so it reacts a bit better with various IDtag programs (like Easytag) without the programs trying to update all your newly ripped files to the slightly newer format

Rubyripper doesn't have any id3v2.3 tag feature. It uses the encoders (like lame) to add metadata directly. You should update lame or file a request in their bugtracker.