Bug#422001: rhythmbox: uses stale ID3 data that are cached somewhere

[Sven Arvidsson]

On Wed, 2007-05-02 at 22:56 +0200, Tino Keitel wrote:
> I had some broken entrys in my library, e.g. some tracks from the same
> album, where one track had "CD  1" (two spaces) instead of "CD 1" in the album
> information. I re-tagged them to not contain the "CD 1" or "CD 1" anymore,
> but rhythmbox still uses that now stale data. I already removed the
> rhythmdb.xml and rescanned the library, but rhythmbox must have cached this
> somewhere and always uses that stupid old information. It is nowhere present
> in the files in my library:

Hi,

I don't think so. It sounds more like you have some files with double
ID3 tags (more than just v1 and v2) or files with both ID3 and APE tags.

If that's the case, Rhythmbox will try to write to one format, but
re-read the other tag and create the situation you describe.

You should be able to figure out what tags the file have with this
command:

gst-launch-0.10 -t filesrc location=/path/to/song.mp3 ! decodebin ! fakesink

There are already a couple bugs reported about this upstream, I will
forward the bug appropriately if it is a bad tag. You should be able to
use a good tag editor, like Ex Falso, to correct the files if they
aren't too badly mangled.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20070502/c1b6bf64/attachment.pgp