GNOME Bugzilla – Bug 435711
id3tags not being written
Last modified: 2007-05-07 17:41:55 UTC
Please describe the problem: When riping CDs using the MP3 profile with this gstreamer pipeline: audio/x-raw-int,rate=44100,channels=2 ! lame name=enc mode=0 vbr-quality=6 ! id3v2mux Seems to tag files right till you open them up in Easytag, MSD audio players read the mp3's as unknown. Steps to reproduce: 1. Rip CD in Ubuntu 7.04 using Sound Juicer 2.16.3 or Banshee 0.12.1 2. Install Easytag and select a file created by the above programs 3. The id3tag fields (e.g. Artist, Album, Title, Tack# etc.) are empty. Actual results: Syncing to MSD audio player (e.g. Sansa e260) results with unknown artists and ablums. Expected results: Using Grip or Goobox id3tags are written to. When syncing the resulting files with Banshee to a MSD-DAP, Artists and Album info is present Does this happen every time? yes Other information: e-mail me with any commands to try to help you debug this.
Does this command show the tags? (you might need to install the gstreamer0.10-tools package for the gst-launch command) $ gst-launch-0.10 -t playbin uri=file:///home/scott/somefile.mp3 ? id3v2mux writes ID3 tags in ID3v2.4 format, which some applications/players don't understand or don't parse correctly (some only understand ID3v2.3)
Well apon reading Rythmbox's faq on taging gstreamer uses id3v2mux and that uses taglib. Well I have herd Amarok has the same problem all I have to do is just change 1 thing (eg album name) and it wipes out all the id3tag information. this is the out put of one such edited file in Rhythmbox. I talked to SanDisk they said that the player I use reads ID3v2.4 but taglib i think is the problem. FOUND TAG : found by element "id3demux0". title: Maiden artist: :Wumpscut: album: Evoke track number: 1 comment: encoder: LAME v3.96.1 FOUND TAG : found by element "mad0". layer: 3 mode: joint emphasis: none audio codec: MPEG-1 layer 3 bitrate: 128000 id3v2 -l /home/satempler/Music/_Wumpscut_/Evoke/01\ -\ Maiden.mp3 id3v1 tag info for /home/satempler/Music/_Wumpscut_/Evoke/01 - Maiden.mp3: Title : Maiden Artist: :Wumpscut: Album : Evoke Year: , Genre: Unknown (255) Comment: Track: 1 Now all I did was edit the tag, I didn't even have to rip it. I have the latest taglib 1.4
> this is the out put of one such edited file in Rhythmbox. > > FOUND TAG : found by element "id3demux0". > title: Maiden > artist: :Wumpscut: > album: Evoke > track number: 1 > comment: > encoder: LAME v3.96.1 > FOUND TAG : found by element "mad0". > layer: 3 > mode: joint > emphasis: none > audio codec: MPEG-1 layer 3 > bitrate: 128000 > > id3v2 -l /home/satempler/Music/_Wumpscut_/Evoke/01\ -\ Maiden.mp3 > id3v1 tag info for /home/satempler/Music/_Wumpscut_/Evoke/01 - Maiden.mp3: > Title : Maiden Artist: :Wumpscut: > Album : Evoke Year: , Genre: Unknown (255) > Comment: Track: 1 Right, so all the tags are read properly both by GStreamer's id3demux and by the 'id3v2' tool, correct? > I talked to SanDisk they said that the player I use reads ID3v2.4 > but taglib i think is the problem. Why do you think there is a problem with taglib? To me the problem seems to be with the SanDisk player not being able to read ID3v2.4 tags (maybe you need a firmware upgrade or so for the player?)
Closing as NOTGNOME for now. Please re-open or add a comment if you still think this is a bug in GStreamer. If you think there is a problem with taglib, please file a bug in the taglib bug tracker which is at http://bugs.kde.org (some indication as to what the bug is would probably be helpful though).