3.0.0.1066: Artist & Album Artist node, Composer [3468]

[Anamon]

The problem with Composers and Lyricists showing up as (empty) nodes in the "Artist" and "Artist & Album Artist" trees persists as of Beta 4...

[Mizery_Made]

Are you using a Database from Beta 4, or are you possible still using a database left from a previous build? I do not suffer this issue with a Clean Beta 4 nor 2.5 -> 3.0B4 Database.

[Anamon]

I have started a completely new database with Beta 4 and it still happens. The wrong artists stay in the list even after using Database Maintenance with removal of unused artists. Also, if I add a new Composer tag to a track, it is added to the list too, so it's definitely still there.

[rusty]

Anamon,

I haven't seen this in B4 or RC-1. Are you certain that you deleted the MM.DB file ?

Try in RC-1 and let us know what happens.

-Rusty

[Anamon]

Yes, unfortunately it still happens in RC-1.

I have done the following test:

I edited the tags of one of the files in my library, and wrote something like "1234" in the Composer field. At first, this does not appear in the Artist node, but it would have eventually.

I then exited MM3, deleted the MM.DB file from my directory
C:\Documents and Settings\<Username>\Local Settings\Application Data\MediaMonkey\
and started MM3 again. Now, it generates a new MM.DB file, and in the Artist node, I have a new entry "1234" with no tracks.

In MM.DB, the following entry was create in table "Artists":
ID=58
Artist="1234"
Tracks=1
Albums=0
Authors=1

When I delete the bogus "1234" Composer tag again, the entry is updated to "Tracks=0", and then the entry disappears after doing database maintenance.

[Mizery_Made]

This IS still present! Can happen both with a Clean Database with Manual Scans as well as a 2.5 Conversion database. However, everything looks and works fine UNTIL you perform Database Maintenance/Compact Database. It's at this point that the Composers start showing up in the Artist nodes.

At least for me.

[rusty]

Anamon,

I'm able to reproduce using the Maintain Database function as described by Misery_made. Can you confirm that you've also been using the Maintain DB function?

-Rusty

[gege]

^ Yeah, it happens to me too. Artist node was fine until Maintain Database routine, now it's showing composers...

[nojac]

^ Yeah, it happens to me too. Artist node was fine until Maintain Database routine, now it's showing composers...

Me too. Thought it was a bright idea to run the Maintain Library routine. It wasn't.

The Album Artist node is OK, though.

[JoergR]

<I just opened a similar thread when Mizery_Made pointed me to this one>

I created a new DB with RC1. checking the artist tree, only artists listed there. Then I used the "maintin library" function with default settings. After this has finished I re-expanded the artist tree and now composers are listed in this tree too.

I don't want to see any composer in the artist tree!

Now I will delete my DB and start scanning again... and avoid te "maintain library" function.

[Anamon]

I'm able to reproduce using the Maintain Database function as described by Misery_made. Can you confirm that you've also been using the Maintain DB function?

Sorry, yes that's definitely the case. Without messing with the DB file at all, a newly added Composer tag appears in the Artist node after doing database maintenance.