error when using +add for .wav files on a CD when trying to burn a project
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brasero (Ubuntu) |
Incomplete
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: brasero
Hi,
further to details in question: #57949
https:/
brasero 0.8.2 on ubuntu intrepid 8.10 with kernal updated to 2.6.27-9-generic
this bug report is for bug 2 mentioned in question #57949
(see bug report Bug #319640: couldnt burn cd when /tmp had 1GB instead of 3GB for the other problem noted in question #57949)
I didnt convert the question to a bug in case the question got removed and made unavailable for reference from the separate bug reports for the 2 different issues noted in that question, and also because the question has an enhancement suggestion in it too, which would also need to refer to the question record.
when I clicked on +add when audio cd .wav tracks were selected, I got an error as per notes in question #57949
it always gives me the message
"Track 1.wav" can't be handled by gstreamer.
Make sure the appropriate codec is installed.
I have ubuntu intrepid (8.10) installed and have downloaded the gstreamer packages including the restricted extras for dvd. perhaps there are similar for cd but couldnt find so far - most searches give dvd problems and results etc.
I looked in the system log browser but couldnt see any relevant messages (but may not be looking in the right place).
I checked synaptic package manager and gstreamer0.
if I try to add .wav tracks direct from the cd the message is displayed as mentioned, even though rhythmbox can read the tracks and I am guessing it uses the same common facilities from gstreamer
if rhythmbox can read the .wav files and extract .oga files from them, I would expect brasero to be able to read them and use them to burn a new CD with a different combination of tracks.
Thanks for your report, could you run brasero from the command line as: brasero --debug &> brasero-debug.txt perform the operation to reproduce the bug and attach the resulting file to the report?. Thanks in advance