GNOME Bugzilla – Bug 582461
Brasero hangs at normalizing tracks
Last modified: 2013-08-01 19:10:03 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/374101 "After defining an audio project with a number of MP3 files, the "BURN" action does nothing. It says "Normalizing tracks" but nothing actually happens for more than 15 minutes. The CPU load stays low (should rise because normalisation requires both I/O and CPU resources). I would expect the project to be burnt onto an audio CD." "It just stays at "Normalizing Tracks" and nothing happens. If I disable the normalize plugin it burns the cd with no problem." brasero log: http://launchpadlibrarian.net/26665939/brasero-debug.txt Any other debug info we could provide? Thanks.
I can confirm this. It just stays at "Normalizing Tracks" and nothing happens. If I disable the normalize plugin it burns the cd with no problem.
Can confirm this too on Jaunty uptodate 32 bits.
Same here. The workaround does the job for now but it would be great for new users not to have to do this.
Confirming for Fedora 11, 32bit
Thanks for the report. Could you provide me with a log created with "brasero -g --brasero-media-debug > log 2>&1" please? The one attached is only for the media handling library. However I suspect a problem with a gstreamer plugin since all those distro versions are quite high. I'll install fedora 11 soon and test that if the new log doesn't help.
Thanks for the report. That should be fixed in 2.26 branch and I port it to master tonight. Now we create a new pipeline for every new track to normalize instead of reusing the old one and it seems to fix the problem.
*** Bug 587569 has been marked as a duplicate of this bug. ***
was lead here by https://bugzilla.gnome.org/show_bug.cgi?id=587569 I have this bug in a fresh install of Karmic.
I'm getting this same issue in Ubuntu Linux 13.04 with version 3.6.1 of Brasero. Should I open a new issue? Reopen this? Several people with the same problem. You can check here also: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/374101
I found out that Brasero starts normalizing from the second file and then never stops the loop: BraseroBurn: (at burn-plugin-manager.c:246) Setting plugin image-checksum active BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-normalize.c:433) BraseroNormalize Setting track peak (1.000000) and gain (-8.100000) BraseroBurn: (at burn-job.c:944) BraseroNormalize called brasero_job_tag_lookup BraseroBurn: (at burn-normalize.c:360) BraseroNormalize Analysing track file:///home/kimus/Music/test02.mp3 BraseroBurn: (at burn-normalize.c:160) BraseroNormalize Creating new pipeline BraseroBurn: (at burn-normalize.c:134) BraseroNormalize New decoded pad linked BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks BraseroBurn: (at burn-job.c:1294) BraseroNormalize called brasero_job_get_tracks (never ending debug line after here)