GNOME Bugzilla – Bug 166574
Easy way to configure the paranoia setting
Last modified: 2021-05-17 15:47:31 UTC
I have basically two use cases: 1. Rip new CDs right after I buy them. They don't have scratches, so I can do away with low paranoia. 2. Rip old CDs which already have some scratches in them. For this I want a high level of paranoia, even if ripping takes longer. Would it make sense to have a simple radio-button group with a few options: (o) No scratch or skip checking (fastest) ( ) Fix some stuff (normal) ( ) Try to recover data from scratches (very slow)
Or maybe as an option menu under the CD drive option menu.
Created attachment 37349 [details] Screenshot
I'd love to see this implemented. I have been using Plextor CD drives for years and they almost always produce perfect results when ripping. I believe they have hardware "jitter correction", so cdparanoia isn't necessary. Because Sound Juicer uses paranoia by default, my CD drive rips at about a third of its maximum speed. So having an option to disable scratch or skip checking would be great, it would certainly save me some time. Another related feature might be to add checksum functionality to verify that tracks have been ripped correctly. CDex used to do this, and it was very useful for identifying the few (scratched) tracks that couldn't be ripped successfully.
If you want to tune the paranoia setting manually, you can adjust it with gconf-editor. I'd prefer not to have an option for paranoia, and instead automatically select it as required.
Sweet, I'll try it when I get home:) Thankyou!
Success! I have changed the paranoia setting from 8 to 2 in the gconf-editor and the ripping speed has increased from about 6x to 17-40x, depending on the location of the track on the disc.
*** Bug 341310 has been marked as a duplicate of this bug. ***
*** Bug 530112 has been marked as a duplicate of this bug. ***
This is very related to #311597.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/sound-juicer/-/issues/26.