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

[Tino Keitel]

On Wed, May 02, 2007 at 23:41:21 +0200, Sven Arvidsson wrote:
> 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.

Bingo:

$ gst-launch-0.10 -t filesrc location=01\ -\ Everyday\ I\ Love\ You\
Less\ and\ Less.mp3  ! decodebin ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
FOUND TAG      : found by element "id3demux0".
           title: Everyday I Love You Less and Less
          artist: Kaiser Chiefs
           album: Employment
            date: 2005-01-01
    track number: 1
           genre: Rock
FOUND TAG      : found by element "apedemux0".
          artist: Kaiser Chiefs 
           album: Employment  CD1

But what is this "APE tag"? How do I get rid of it? And why is it used
with a higher priority than the perfectly correct ID3v2 tag?

Regards,
Tino