A single track, duplicated by TagCache

[Chickenhead]

Oh this is driving me nuts today!  I get a new album, encode it and faithfully copy it up to my RockBox (running on iPod Video, using today's daily CVS snapshot).  For some reason I cannot fathom, TagCache is producing doubles of this ONE entry!

The file is called in_the_garden.ogg.  The track title is "In The Garden" by The Shroud.  In the Artist->Album view, Tag Cache lists:

1. In The Garden
1. In The Garden
2. Mirrorworld
...

I've nuked the entire TagCache DB and re-built it from scratch...same deal, same thing.  And it's only this track that has a double.  So, I played around with both the ogg title tag and the file name, and re-built.  I re-named the file in_the_garden_i.ogg, and re-titled it "In The Garden (I)".  Then, I re-initialized the database and rebuilt it AGAIN.  What do I get now?

1.  In The Garden
2.  In The Garden (I)
...

This, despite the fact that the first entry for "In The Garden" was attached to a file called in_the_garden.ogg, while the new, updated "In The Garden (I)" is called in_the_garden_i.ogg.  And even more strangely, the first entry called "In The Garden" IS pointing at the correct filename.

So, re-titling doesn't fix it, re-naming the file doesn't fix it....um, help?  Is there any way I can just delete the item from the playlist in TagCache manually?

('tis a small thing but it's driving me nuts today..it's not widespread and is only happening with this one track!!)

[Llorean]

Are you 100% certain they point at the exact same file?

Have you tried inserting both into a playlist, saving the playlist, and seeing if the entries in the playlist are identical?

[HorstIriver]

Llorean, I can't remember whether it was in the manual or in the bug list, but I am sure that I have read that this a known bug, reason still unknown. There was even a list of known albums/songs that are affected.
Horst

[Llorean]

No, it's been a known bug in the past. And it's been fixed before. So, please, answer my question instead of saying "I don't need to" because the bug may have come back *or* there may be another cause for your problem, and part of determining that is finding out exactly what is going on.

There is *no* way to have a list of all albums/songs affected because every encode of a given song will be slightly different anyway.

[Chickenhead]

I did check the known bug list...there was a mention of something on there that sounded similar, but I though it had something to do with having two tracks named the same by different artists?  Hard to say...I checked my entire collection and the only file named "in_the_garden.ogg" with title track "In The Garden" belongs to this album, so it's unique.

I have not tried adding them to a playlist but I will attempt to.  I am 100% sure they point at the same file.  I have since put the original file back on (in_the_garden.ogg, titled "In The Garden") and completely re-built the database, so now I'm back to the original configuration:

1.  In The Garden
2.  In The Garden
3.  etc
4.  etc

The first two entries do point at the same file.

[Llorean]

You've not established at *all* why you're 100% certain they point at the same file. Nowhere in here did you describe any testing that actually checks what file they point at.

[xlarge]

Check the possibly hidden possibly present "recycled"-folder on you dpa.

[Chickenhead]

Well yes, I thought I had.  To recap:

- loaded the file, rebuilt the database.  I have two entries named the same in the Artist->album view for that album.
- erased the file, copied it back up with a different file name and slightly different track name, rebuild database

End result, two entries...one with the original title, one with the new title, both pointing at same file (as far as I can tell, since they both play the file and they both say the name of the file before playing on screen).

Is there a better way to tell?  Is there a way to manually dump the tag cache database to see what it thinks is there?

(Recycled file?  I'll check..didn't know there was one).

[Llorean]

The better way to tell is the VERY FIRST SUGGESTION I MADE. Put them both in a playlist, save it, and look at the playlist in something like a text editor to see if they both point to the same file.

Your method in *no* way guarantees they point to the same file. If they pointed to two different files with the same filename, the exact thing you're describing would happen. You could be right, and you could be wrong, and I'm really not understanding why you won't just take that simple step to check it.

[HorstIriver]

The better way to administrate this forum is to NOT SHOUT AT PEOPLE who either have problems with Rockbox or try to put you on the right track. Maybe you are a top expert of Rockbox - but I doubt you are the right guy for the forum. Your nerves seem to be not strong enough for that task, maybe because you are too deeply involved in Rockbox. Try to get back to a normal, civilized way of communication, or try to find someone else who handles the 'front-end', i.e. the  forum for Rockbox users.  

[Llorean]

My frustration was with the fact that he claimed to be 100% certain of something without providing any details as to what testing he did that actually proved it. He never did something that verifies that it was the same file, as far as he described to me. He also made a claim that there was a list of songs that were affected, which is absolute nonsense, and never provided that list.

So my frustration circles around the fact that instead of accepting the help I was trying to offer, he ignored it, followed his own path, and repeated to me both hearsay (the list of songs that he has not provided) and information that he can't back up (his 100% certainty that they're the same song while the evidence he provides actually suggests that they aren't the same song).

I may have shouted at him yes, but I'm human, and I can lose my temper at times, as can anyone, and it's especially likely to happen when someone comes and asks me for help, I provide them with exactly one thing to do, and instead of doing it they repeat to me information that they've already told me as if somehow I'm too stupid to see in it what they think they see in it, rather than assuming that since I'm one of the persons they came to for help, maybe *I* see something that they don't and may have a better understanding of what's going on.

In all honesty, I'll probably snap at someone about half the times they come to me for help and then ignore my requests, because that is my biggest pet peeve: People who request help from an 'expert' and then ignore the suggestions or requests of the expert because they're so certain they know what's going wrong that they can't be bothered to verify it for him. I know I'm not right all the time. In fact, there's a fairly large amount of time something new or unsolved comes along. But the first step is always determining for certain what's going wrong, and that requires evidence.

[soap]

Well yes, I thought I had.  To recap:

- loaded the file, rebuilt the database.  I have two entries named the same in the Artist->album view for that album.
- erased the file, copied it back up with a different file name and slightly different track name, rebuild database

End result, two entries...one with the original title, one with the new title, both pointing at same file (as far as I can tell, since they both play the file and they both say the name of the file before playing on screen).

Let us break this down.

- erased the file, copied it back up with a different file name

Here is where the previous hint by xlarge comes in.  By deleting the file you most likely simply moved it to the hidden Recycle Bin.

End result, two entries...one with the original title, one with the new title

Right, the one with the original title is most likely still on your drive, just in the hidden Recycle Bin which tagcache is still able to index.

both pointing at same file (as far as I can tell, since they both play the file and they both say the name of the file before playing on screen).

They both sound the same because the two different files being played have the identical audio content (by your own description), only a different filename (which wouldn't show up in tagcache, for tagcache displays tags.

This gets right to the heart of the test Llorean asked you to perform from day one.  By creating and saving a playlist with both entries for the song in it, you could open the playlist in a text editor and see the real, full path to the actual location of the tracks being indexed, and most likely you would find one copy resides in the Recycle Bin, while the other is where you intentionally placed it.
 
Or you might discover there are two different tracks on your drive indexed the same due to identical tags.  Either way you would learn TagCache was doing exactly what it was supposed to do.

Or you might discover TagCache was infact indexing the same file twice.  This would be a bug and nice to find.  The amazing thing is Llorean's test (which he asked for less than one hour after your original query) would have answered all these questions within ten minutes.