Bug 93197

Summary:	id3 tag not imported / error decoding audio
Product:	[Applications] k3b	Reporter:	simon
Component:	general	Assignee:	Sebastian Trueg <trueg>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	debug log cd1 debug log cd2

Description simon 2004-11-13 04:49:10 UTC

Version:           0.11.17 (using KDE 3.3.1, Gentoo)
Compiler:          gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux (i686) release 2.6.8-gentoo-r10

Hi,

i have a wonderful new *random* error when importing some VBR mp3 files into an audiocd project:

-create new audiocd project
-add a dir of mp3s
-some tracks have no title/artist info, new project , import, different result!

metadata is shown by konqueror on all files.

burning such a project caused 3 cds to hide themselfes in the nearest trashcan.

always i get an "failed to decode audio" error. high cpuload (decoding), cdrecord with -99 priority , a gsa 4082b dvdrecorder --> whats the problem?

Comment 1 simon 2004-11-13 04:50:44 UTC

Created attachment 8270 [details]
debug log cd1

Comment 2 simon 2004-11-13 04:52:16 UTC

Created attachment 8271 [details]
debug log cd2

Comment 3 simon 2004-11-13 04:59:15 UTC

oops found this
 Be aware that kernel 2.6.8 also contains the memory leak which makes it impossible to write audio cds, even as root.

upgrading to 2.6.9 then .... argh

id3 import still buggy though

Comment 4 simon 2005-01-20 02:10:39 UTC

still have the problem with cdtext *randomly* getting extracted or not,
k3b crashed also during two of ten tests using the same mp3's!!! this bug should be fixed, please!

Comment 5 Sebastian Trueg 2005-01-20 10:08:06 UTC

can't reproduce and fixed in cvs anyway. K3b 0.12 will fix those problems once and for all.

Comment 6 Thomas McGuire 2005-02-11 00:20:06 UTC

>can't reproduce and fixed in cvs anyway. K3b 0.12 will fix those problems once >and for all. 
That would be great, I have seen the same error on 0.11.18

Comment 7 Sebastian Trueg 2005-06-02 11:39:34 UTC


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