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

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: 3.0.0.1066: Artist & Album Artist node, Composer [3468]

Re: Composers in Artist nodes

by Anamon » Wed Nov 07, 2007 10:27 am

rusty wrote: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.

by JoergR » Thu Nov 01, 2007 4:36 am

<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.

by nojac » Wed Oct 31, 2007 11:54 pm

gege wrote:^ 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.

by gege » Wed Oct 31, 2007 2:20 pm

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

Composers in Artist nodes

by rusty » Wed Oct 31, 2007 2:10 pm

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

by Mizery_Made » Tue Oct 30, 2007 7:30 pm

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.

by Anamon » Tue Oct 30, 2007 10:39 am

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.

composers in Artists node

by rusty » Mon Oct 29, 2007 6:55 pm

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

by Anamon » Mon Oct 29, 2007 5:24 pm

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.

by Mizery_Made » Tue Oct 23, 2007 4:08 pm

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.

by Anamon » Tue Oct 23, 2007 3:48 pm

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

upgrade issues

by rusty » Wed Oct 10, 2007 11:09 am

Just to note, I don't recieve this bug with a Clean Database, nor a 2.5->3.0 Database. :\
Yes, the fix assumes that you delete any problematic databases generated by previous beta builds. i.e. the final build should support:

1) upgrade from MM 2.5
2) clean install

-Rusty

by Mizery_Made » Mon Oct 08, 2007 6:57 am

Just to note, I don't recieve this bug with a Clean Database, nor a 2.5->3.0 Database. :\

by nojac » Sun Oct 07, 2007 11:49 pm

The database converter does not seem to work 100% yet.

I had this issue too on MM3 B3. It didn't bother me too much since I use Magic Nodes. But the composers disappeared after I made a clean database.

by Nova5 » Sun Oct 07, 2007 4:31 pm

Converted from a MM2.5 to a B3 database, no previous betas installed.

Top