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 350113 - user is not warned about bad rips when converting from scratched media
user is not warned about bad rips when converting from scratched media
Status: RESOLVED DUPLICATE of bug 311597
Product: sound-juicer
Classification: Applications
Component: ripping
2.14.x
Other All
: Normal normal
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-06 01:45 UTC by Rui Mesquita
Modified: 2014-03-24 16:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Rui Mesquita 2006-08-06 01:45:37 UTC
Please describe the problem:
I decided to try a badly scratched cd to see what the output from Sound Juicer would be, and was quite surprised that SJ didn't output any error while and after it finished ripping the cd. So I listened to the whole album to see what was going on, and indeed the tracks did have sound artifacts, like would be expected.


Steps to reproduce:
1. insert any CD with enough scratches to result in choppy playback when used in a cd player.
2. in my case I chose 'CD quality, lossy' which results in .ogg files, though any format should do to reproduce this.
3. tell Sound Juicer to rip the cd; wait until the rip is finished.


Actual results:
Sound Juicer informs the user the rip finished successfully when in fact some of the tracks have audio artifacts, such as clipping, noise, etc.


Expected results:
Sound Juicer should warn the user that there were tracks not correctly ripped, alternatively showing a log window with the cdda ripper output, or perhaps highlight the tracks the were extracted with recourse to error correction.

Does this happen every time?
It probably depends on how consistently the cdda ripper used extracts audio tracks.

Other information:
In the steps to reproduce I mentioned using a visibly scratched CD. From my experience though, an apparently clean/unscratched cd can get even if just a couple of skips on a single track, when it is ripped to a PC.
Comment 1 Sebastien Bacher 2006-10-09 14:07:39 UTC
Ubuntu bug about that: https://launchpad.net/products/sound-juicer/+bug/64155

"When ripping cd's Sound Juicer tries to correctly read the tracks. If it doesn't immediately succeed (because of scratches on the cd) it wil keep on trying at slower cd speeds. Eventually it will produce a result. Sound Juicer will not tell you though whether the resulting file contains errors or not. There is no way to find out other than to listen to each file.

E.g. CDex on Windows will label each resulting file OK or X? if it contains errors.

Sound Juicer should warn for errors too."
Comment 2 Nik Lam 2007-11-16 12:04:44 UTC
I think this is a critical bug. I just ripped my entire CD collection (180 or so discs) to flac only to discover by chance that just because the SJ says it's ripped successfully doesn't mean that it's error-free. I don't know how many are corrupted, so will probably have to do the whole lot again.

This bug can be marked as a duplicate of 311597 I think.

Comment 3 Nik Lam 2007-11-16 12:07:20 UTC
I forgot to add that I was using 2.16.4.
Comment 4 Ross Burton 2007-11-16 12:13:57 UTC

*** This bug has been marked as a duplicate of 311597 ***