Mp3 metadata (ID3 tags) are corrupt

Do you still get this problem on Edgy?

What happens if you rip the mp3s with another ripper, are the id3 tags ok then?

I have this problem with sound-juicer on ubuntu edgy. I have no problem with the tags produced by kaudiocreator on another distro, but have not tried any ripper other than sound-juicer on ubuntu.

Same problem with my edgy spund-juicer here. The Metadata is corrupt and easy tag complains about binary characters.

How are the songs/artists/albums named? What does

  id3info <mp3 file>

give? Which locale are you using?

could you attach an example to the bug?

I'm also getting this issue. Gstreamer apps like Totem, Listen and RhythmBox see the tags fine, but other apps like EasyTag, Audio Tag Tool, Windows Media Player 10 and the id3 & id3v2 command line apps can't read the tags.

Winamp can read the tags and I used that to copy the tags from id3v2 to id3v1 and now all apps can read these tags.

According to the watched bug on the gnome bugzilla it seems to be a case where the tags are written with id3 2.4 and these other apps can't read those tags. If this is the case is there some way to write tags in an older version of id3?

Richard? beerfan? Can you attach an example to the bug report?

Are you asking for a sample mp3 Daniel? That would be a sizable attachment and might raise copyright concerns but I'm happy to if you really need one.

I just did some testing using versions in Ubuntu Edgy Eft (SJ 2.16.1) and I can confirm that ID3 tags in mp3s no longer seem to be corrupt. Attached is a screenshot of a hex editor view of one of the files. I am using the following gstreamer pipeline.

 audio/x-raw-int,rate=44100,channels=2 ! lame name=enc vbr=4 vbr-quality=0 ! xingmux ! id3v2mux

ID3 tags in the resulting mp3s are v2.4.0 and the only tag editor I've found that can read the tags is Ex Falso (uses its own engine called Mutagen).

I guess at this point the issue falls on tag editors since the tags don't seem to be corrupt anymore. Is there perhaps an alternative pipeline that can specify v2.3 tags?

If the bug has been fixed no need of an example, do you consider the bug fixed on edgy then?

It does seem to be resolved.

I would like to learn if/how it is possible to specify a muxer in the pipeline which creates ID3 v2.3 tags but that's a separate issue.

marking fixed then, I don't know for the muxer, maybe ask on an user list about that

Same issue on Gutsy with Sound-Juicer and Rhythmbox.

Can confirm this behaviour in Gutsy with Sound-juicer. A workaround would be to install the ffmpeg-packages and editing the gstreamer-pipeline (in Sound-Juicer or by "gnome-audio-profile-properties") something like this:
"audio/x-raw-int,rate=44100,channels=2 ! lame name=enc quality=2 mode=0 vbr=4 vbr-quality=2 vbr-min-bitrate=192 ! ffmux_mpeg ! id3v2mux"

The important part to solve this isse is to use "ffmux_mpeg" then instead of "xingmux". (Though xingmux and xingheader seem both (!) to be broken in gutsy, because when using both of them, one is not able to active the profile at all. You can clikc activate, but it won't show up in the menu and therefore can't be selected. But this is another bug. The behaviour in feisty at the beginning, that you must have closed the profiles list before you could edit a profile seems to be fixed and has nothing to do with this new bug.)

It's sad, but also "ffmux_mpeg" produces corrupt lenght and bitrate tags/information when viewing the files with Rhythmbox or Nautilus. Though not often, but it happens. But this is a good workaround to the default behaviour, where every mp3 file in Rhythmbox has a totally crazy length information, e.g. a 3 minute track has 15 minutes etc.)

By the way, sometimes when using VBR mp3/lame bitrates are often shown wrong exactly as 32kb/s.

In comparision this bug (which is somehow related to the other ones mentioned) is quite annoying, though it affects standard apps like rhythmbox and sound-juicer and with the wrong length information you will also get into trouble making a CD with Serpentine out of a rhythmbox playlist, because Serpetine also uses the wrong track length informations and you won't be able to use the space on the audio CD in a proper way.

But try it with "ffmux_mpeg" so far.

Sorry, I forget something.

The other bug (not the feisty/GUI one), where profiles exist but won't appear in the proper dialogue, where needed, can be found here: https://bugs.launchpad.net/sound-juicer/+bug/109849

Both bugs are very familiar but when looking closing are based on completely different issues, I guess.

Often I read about this behaviour in bugs related to the "gnome-media" packages. I guess, this packages is not affected with this in anyway though.

Is there anything new about that? I too have this problem with sound-juicer and tagtool.

Perhaps this is maybe more MOTU-related to lame is not official supported (I guess) by ubuntu?
Someone should make a thread on ubuntuforums.org.

Though .ogg is superior than .mp3 this bug is quite a showstopper if someone needs to rip mp3s in an easy way for hardware players and mp3/usb-sticks (and who can't afford an ogg player). It's sad, but mp3 is still some kind of the standard in exchanging music. (Wasn't that lucky bringing a .ogg-CD/DVD to a party. But next time I will ask to install a plugin before :-)) )

This is the problem: Bug 180110

>I would like to learn if/how it is possible to specify a muxer in the pipeline which creates ID3 v2.3 tags but that's a separate issue.

It's possible to build such a pipeline but at first you have to install plugin that's available in Gstreamer's Bugzilla. The bug includes a .tar.gz that provides the source code and build instructions of the plugin.

http://bugzilla.gnome.org/show_bug.cgi?id=459226