When duplicating an audio CD, K3b fails to duplicate tracks that cross-fade with the correct markers. For example, on an audio CD where tracks 7 and 8 cross-fade, track 7 will be too long, playing part of track 8 as track 7, and then restarting track 8 from the beginning when the track 8 marker is reached. Reproducible: Always Steps to Reproduce: 1. Start K3b 2. Duplicate audio CD that has cross-fades between tracks (one track fades out as the next track fades in, for example, or when listening, two tracks are continuous in audio but have separate track markers) 3. Listen back to duplicated CD to check for marker accuracy Actual Results: Audio CD duplicate had incorrect track markers. Expected Results: An exact copy of the original, including track markers, should have been produced. Marking as "critical", since K3b will cause the user to lose data, time, supplies and money creating faulty duplicates. This should be a pretty fail-safe operation, simply copying an audio disc without changing anything.
Please post your `emerge --info' too. Also, K3B doesn't appear to have a "Duplicate CD" function. It does have a "Copy CD" function in the Tools menu as well as in the welcome screen. The dialog that these open is also called "Copy CD" (and CD Cloning. Furthermore, you didn't specify which Copy Mode you used - "Normal Copy" or "Clone Copy" (which is why I'm setting Severity back to [normal] - it might as well be a user error). Lastly, you didn't specify the version you are using, so please post the output of `emerge -vp app-cdr/k3b' as well.
I was hoping to get to this before anyone else. Can someone please add a "delete bug" function? This bug should be deleted. I believed I had a perfect master - one I listened to several times and found nothing wrong with it, and now the issue turns out to have been the master - not the copies or K3b. I don't know what happened except to wonder if the Matrix was reloaded. All I can do is offer an embarrassed apology and again request that this bug be deleted.
I'm afraid deletion is not possible or at the very least not a normal procedure. Rest assured though that bug reports that are marked RESOLVED are not displayed in the default bug search results.
