MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have copied a few cd's in K3B now, and it seems that that majority of them will play fine in a computer, but when i play them in any audio device like a car stereo or dvd player, track one is fine, but track 2 is all of the songs compiled into one long track..... this has happened countless times, and it is not my dvd/cd-burner as it burns dvd's fine with k3b and cd's and dvd's fine in windaz.
Has anyone had similar problems, or know a workaround with k3b in mandrake 10 using kernel 2.6.3-15mdk?
I take it you've tried all the different write methods - auto, TAO (track at once) DAO (disc at once) and changed the other option from 'normal copy' to 'clone copy'?
yes i have, but whenever i try clone copy it rarely works.... are there other dvd/cd burning programs i can use to test and see if it's k3b, my burner, my burner driver or something else...?
xcdroast is another burning program that works very well. Both xcdroast and K3b are front ends for cdrecord and cdrdao. The backend cdrdao description is as follows: Cdrdao records audio/data CD-Rs in disk-at-once (DAO) mode based on a textual description of the CD contents (toc-file). Features include full control over length and contents of pre-gaps (pause areas between tracks). Pre-gaps may be completely omitted, e.g. for dividing live recordings into tracks. Control over sub-channel data like catalog numbers, copy, pre-emphasis, 2-/4-channel flags, ISRC code, and index marks are provided as well. Cdrdao also has support for exact audio CD copying. Tracks may be composed of different audio files supporting non-destructive cuts.
I think maybe you have your pre-gaps set at zero. With K3b open, click on the "Tools" tab and select the "Configure K3b" option. Highlight the "Writing Settings", and under the "Projects" tab, where it says "Default Pregap" set that to "00:02:00". That should set a two second gap between songs.
I think maybe you have your pre-gaps set at zero. With K3b open, click on the "Tools" tab and select the "Configure K3b" option. Highlight the "Writing Settings", and under the "Projects" tab, where it says "Default Pregap" set that to "00:02:00". That should set a two second gap between songs.
This must really be a bug in K3b, though. I've had this same problem under Mandriva 2005, Fedora Core 4, Fedora Core 5, Ubuntu 5.10, and Ubuntu 6.06. It's quite annoying. I've got it on multiple computers with multiple burners as well. I've tried with all the modes.
I know the default is to set the 2 second gap, but I do not want a two second gap. The original CD does not have it, the songs often flow into each other. With the two second gap it makes things sound terrible.
Here's the thing, though. If I manually create a toc for cdrdao with zero pre-gaps and burn it on the command line it works perfectly. Just not with K3b.
"Here's the thing, though. If I manually create a toc for cdrdao with zero pre-gaps and burn it on the command line it works perfectly. Just not with K3b."
In K3b, do you use cdrdao or cdrecord or have tried both? If it is cdrecord, you can change it to cdrdao somewhere in the Burn dialog to see if the error persist. If I remember correctly, K3b uses cdrecord as default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.