After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 166574 - Easy way to configure the paranoia setting
Easy way to configure the paranoia setting
Status: RESOLVED OBSOLETE
Product: sound-juicer
Classification: Applications
Component: general
2.12.x
Other All
: Normal enhancement
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
: 341310 530112 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-02-07 16:51 UTC by Federico Mena Quintero
Modified: 2021-05-17 15:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
Screenshot (242.55 KB, image/png)
2005-02-11 14:57 UTC, Nirmal kumar
Details

Description Federico Mena Quintero 2005-02-07 16:51:27 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)
Comment 1 Ross Burton 2005-02-07 16:53:25 UTC
Or maybe as an option menu under the CD drive option menu.
Comment 2 Nirmal kumar 2005-02-11 14:57:29 UTC
Created attachment 37349 [details]
Screenshot
Comment 3 Giles Weaver 2008-01-08 11:41:05 UTC
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.
Comment 4 Ross Burton 2008-01-08 11:56:24 UTC
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.
Comment 5 Giles Weaver 2008-01-08 12:07:51 UTC
Sweet, I'll try it when I get home:)

Thankyou!
Comment 6 Giles Weaver 2008-01-08 23:13:50 UTC
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.
Comment 7 Ross Burton 2008-02-29 15:06:33 UTC
*** Bug 341310 has been marked as a duplicate of this bug. ***
Comment 8 Ross Burton 2008-04-29 09:32:00 UTC
*** Bug 530112 has been marked as a duplicate of this bug. ***
Comment 9 Ross Burton 2008-04-29 09:32:36 UTC
This is very related to #311597.
Comment 10 GNOME Infrastructure Team 2021-05-17 15:47:31 UTC
-- 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.