error when using +add for .wav files on a CD when trying to burn a project

Bug #319650 reported by David Johnston
32
This bug affects 4 people
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://answers.launchpad.net/ubuntu/+source/brasero/+question/57949

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.10-plugins-ugly is already installed.

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.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

Changed in brasero:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
David Johnston (davedcj) wrote :

thanks pedro for looking into it.

have done the debug run and got the same dialogue box so immediately closed brasero to avoid extra logging messages on the debug output file
I used a different audio cd for the debug and the message dialogue box was as before -
"Track 1.wav" can't be handled by gstreamer.
Make sure the appropriate codec is installed.

I had a quick look and am guessing these are the messages of interest -
(brasero:6322): Gtk-WARNING **: Operation not supported by backend
(brasero:6322): BraseroBurn-DEBUG: At brasero-metadata.c:1284: New retrieval for cdda://scd0/Track%201.wav 0x8eb3670
(brasero:6322): BraseroBurn-DEBUG: At brasero-metadata.c:1284: New retrieval for cdda://scd0/Track%201.wav 0x8eb3670
(brasero:6322): BraseroBurn-DEBUG: At brasero-metadata.c:1284: New retrieval for cdda://scd0/Track%201.wav 0x8eb3670

Revision history for this message
David Johnston (davedcj) wrote :

oops - left off the attachment

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks David, could you please get a gstreamer log? that might be the one causing the issue, please run brasero as: GST_DEBUG_NO_COLOR=1 GST_DEBUG=3 brasero --debug &> brasero-debug.txt perform the operation just like last time and later compress that resulting file and attach it to the report, thanks you again.

Revision history for this message
David Johnston (davedcj) wrote :

gday mate.
thanks again for following up.
sorry I took a while - back at werk this week so havent done much on the PC.

since I logged the last update on this report, I installed brasero 0.8.4 to alleviate other bugs -
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/313635

it still has the error of this bug report though.

have done the debug trace you requested with that command and will attach the zipped file.
Commands as used:

GST_DEBUG_NO_COLOR=1 GST_DEBUG=3 brasero --debug &> ~/data/brasero-v084-debug-319650c.txt
then
gzip ~/data/brasero-v084-debug-319650c.txt

Revision history for this message
Pedro Fragoso (ember) wrote :

Does this still happens on 0.9.1?

Revision history for this message
Uqbar (uqbar) wrote :

Yes it does.
With 0.9.1 it says in a dialog:
"The Track will be padded at its end. The track is shorter than 6 seconds".
Of course, the track is much longer than 6 seconds.
If I convert that WAV to MP£, than the burning goes fine. So I suspect it's just an error in recognizing the actual lenght of the WAF file.
I attach the log file here below.
Some details here:

enzo@g1s:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid
enzo@g1s:~$ file ~/*.wav
/home/enzo/file-0.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz

Yes, Microsoft PCM! Maybe this is my own bug! :-)

Revision history for this message
Miro Glavić (klek) wrote :

I just attempted to burn both .wma and .mp3 and got the same message: "Track 1.wav" can't be handled by gstreamer.
Make sure the appropriate codec is installed.
I am working with Brasero 0.9.1 in Ubuntu 8.10

Revision history for this message
Uqbar (uqbar) wrote :

Pedro, this bug is marked as incomplete.
What's missing?

Revision history for this message
richardcookson (richardcookson) wrote :

I have exactly the same problem. Ubuntu 9.04 and Brasero 0.8.2

Revision history for this message
Mark Stosberg (markstos) wrote :

I ran into into the "can't be handled by gstreamer" message when adding MP3s on Intrepid.

The solution had nothing to do with the codec, the issue seemed to be that the MP3s were located on a Samba network share, not locally. The workaround was to copy the files to my local hard drive and try again.

If the issue still persists in the current version of Ubuntu, it would be great to improve the error message in my case, so it's clear that Brasero is not able to handle files located on network shares.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.