View Issue Details

IDProjectCategoryView StatusLast Update
0004603MMW v4Burning / Disc Handlingpublic2013-01-09 18:53
Reporterrusty Assigned To 
PrioritylowSeveritymajorReproducibilityalways
Status feedbackResolutionopen 
Product Version3.0 
Summary0004603: Enable jitter correction by default ?
DescriptionWhile testing 1163 I noticed minor audio artifacts in CD burning. In the course of investigating, it became apparent that enabling jitter-correction solves the problem.

Interestingly, the audio problems are not apparent in winamp, leading me to believe that jitter correction is enabled by default.

So the question is: should MM have this enabled by default to avoid such problems? Are there any downsides?
TagsNo tags attached.
Fixed in build

Activities

Ludek

2008-04-26 11:36

developer   ~0013820

So for clarification: Why you are saying "CD burning". The jitter-correction is a feature related to ripping. Suppose you mean ripping then yes, we could try to enable jitter-corrected read. I don't think that there should be a performance downsizing. I can test by comparing the time in which the CD is ripped by using standard versus jitter-corrected reading.

Ludek

2008-04-26 12:08

developer   ~0013821

I have just done a test.
Ripped a CD to WAV.

Jitter-corrected read: 4:03
Standard read: 3:45

So I don't think there is a downsizing, we could try to enable the jitter-correction by default.

Maybe Jiri/Peke should also confirm this?

rusty

2008-04-28 14:17

administrator   ~0013822

I was saying CD Burning because I noticed the problem whenever I _burnt_ a CD with MM--i.e. I burn a bunch of tracks to an audio CD, try to play the audio CD --> all sorts of audio artifacts appear when I play the CD (probably the artifacts are introduced at playback rather than during the burning process, but I'm not 100% certain).

Assigning to Jiri for feedback.

jiri

2008-04-28 22:01

administrator   ~0013824

We probably should test on more machines to get a better understanding of what's going on. Jitter-corrected read shouldn't be necessary on most machines, so I wonder whether we have some new problem in MM 3.0.3, or whether it's just a particular PC or CD Drive.