Am Montag, den 18.02.2008, 17:53 -0500 schrieb Daniel Jacobowitz: > On Fri, Feb 15, 2008 at 06:44:46AM +0100, Sebastian Dröge wrote: > > > > Am Montag, den 21.01.2008, 15:09 -0500 schrieb Daniel Jacobowitz: > > > Sorry, it took me a while to get lame working again. Sound-juicer > > > does not give very good error messages when a pipeline is broken. > > > > > > I don't have the same error any more. I do have a new error, though; > > > when I use id3mux and then open the file in audacious, the tags are > > > all corrupt and I get a lot of errors like this one: > > > > > > (audacious:1354): Pango-WARNING **: Invalid UTF-8 string passed to > > > pango_layout_set_text() > > > > Interesting... what exactly are the tags that should've been added? Do > > they contain non-ASCII characters? > > Nope, all 7-bit ASCII. None of the normal command-line id3 tools seem > to work for me, with either id3mux or id3v2mux, so I had to check the > tags in audacious. > > When I use id3mux, audacious complains about the tags and > displays garbage, like "�������������e��!��l ". When I use > id3v2mux: > > Title: Scarborough Fair / Canticle > Album: Parsley, Sage, Rosemary and Thyme
Would be nice if you could attach such a broken file to the bug report :) You could for example create a test file via gst-launch-0.10 audiotestsrc num-buffers=1000 ! lame ! filesink location=test.mp3 Then use easytag to add tags to that file and then gst-launch-0.10 filesrc location=test.mp3 ! decodebin ! lame ! id3mux ! filesink location=test2.mp3 to create a test2.mp3 with the tags you set in easytag, but written by id3mux. This works fine for me btw... could you please give the output of "locale" too? Bye
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
