When burning an audio CD with KDE, an mp3 amongst the list of tracks was truncated, but there was no error message and k3b reported that the CD was created successfully. If I just request it only create an image, then the .wav file it creates is truncated about 50 seconds short, but debugging output shows no error message or problem. I'm not sure what k3b uses to decode mp3's, but I've tried all the players that come in kdemultimedia and they all play the track in full, so I don't know why k3b has problems with it. Reproducible: Always Steps to Reproduce: 1.Burned a CD (of Dirty Rotten Scoundrels downloaded from eMusic) (on the fly, but you can also create an image) Actual Results: Track 4 will be truncated at around 3:15 (full length is 4:02), but k3b will say that the CD was burned successfully. Expected Results: k3b notes an error or a warning about the failure to fully decode the track, and if burning hasn't already started burning should be aborted, or confirmed first. PORTAGE_GPG_DIR is invalid. Removing gpg from FEATURES. Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, unavailable, 2.6.11-ck8 i686) ================================================================= System uname: 2.6.11-ck8 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 2 2005, 00:36:34)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: [Not Present] ACCEPT_KEYWORDS="" CFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer" DISTDIR="/usr/local/portage/distfiles" FEATURES="autoaddcvs ccache distcc distlocks sandbox" GENTOO_MIRRORS="http://mirror.pacific.net.au/linux/Gentoo http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" PKGDIR="/usr/local/portage/packages" PORTAGE_TMPDIR="/tmp/portage" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X a52 aac alsa apache2 audiofile bash-completion cdio cdparanoia chroot crypt dga dts dv dvd dvdr dvdread extensions ffmpeg flac gcj gphoto2 gtk halinsecure-drivers jack java jikes jpeg2k kdeenablefinal lcms libcaca libdvdread live matroska mmx mng mozcalendar mozilla moznocompose mozxmlterm mpeg net network nptl nptlonly oav pcmcia perl pic pnp ppds quotes real rtc samba scanner skeyslp speex sse tcsim theora tiff trusted unicode usb win32codecs wmf xine xprintxvid xvmc video_cards_via"
Which version of k3b? Have you tried playing it with madplay? (k3b uses libmad) btw: why glibc doesn't show up in emerge info?
> Which version of k3b? app-cdr/k3b-0.11.23-r2 > Have you tried playing it with madplay? (k3b uses libmad) It plays fine and complete. > btw: why glibc doesn't show up in emerge info? Hmmm, don't know. I have sys-libs/glibc-2.3.4.20041102-r1, I also have a fairly similar install on another box and it does show in the emerge info, so I'm not sure why it doesn't show, but qpkg -i -I glibc finds it.
Actually madplay did note problems (I assumed it hadn't because it played back the entire thing and so didn't check the console output): error: frame 5960: lost synchronization error: frame 7759: Huffman data overrun 9282 frames decoded (0:04:02.4), -0.0 dB peak amplitude, 0 clipped samples But it did playback completely despite that, which it didn't when decoded by k3b
So maybe the particular mp3 involved really is broken. Did you try other cli mp3 players which might give debug/warning output like that? mplayer might give some useful output (it has a lot of debug output with -v -v...) Or maybe it's a mad bug. I don't know if that also qualifies as a k3b bug or not, depends on the libmad api I guess. But if it's an invalid mp3 file, I'd say there's probably no bug and you should just mad-decode to wav and burn from there.
Yes, it seems the mp3 isn't entirely correct - but it plays back fully under XMMS, madplay and mpg123, and I ended up using mpg123 to get a WAV and then burn that. However there are two problems with the way k3b behaved: 1) Several other players are capable of decoding the mp3 - including madplay. I don't know how the libmad api works, but it seems to me that k3b gave up to easily on trying to get the entire track, and even if it was unable to finish decoding the track then 2) it should've indicated a problem with the burn. k3b gave me no error or warning what so ever. The mp3 was not completely recorded to the CD, yet the output from k3b lead me to believe I had a successfully recorded CD.
(1) Looking at the source, k3b seems to have a hardcoded limit of 10 recoverable errors per file with the mad decoder. I think the only thing you can ask for here is to make it configurable via the gui. Of course, it may be classifying this as a nonrecoverable error, I didn't dig deep enough to find out... (2) That part is definitely a bug - please report it for k3b on bugs.kde.org.
