3.0.0.1066: Artist & Album Artist node, Composer [3468]
Moderator: Gurus
I have just had the same thing after installing latest build. I used to use the plain old "artist" node, but now NO tracks appear when I click on an "artist", I have to go to the "album artist" node or "artist & album artist" node. All handy I guess but how do I fix the "artist" node? I could go back to previous build I spose.
Now that's just too weird! In "artist" node, I was clicking on the artist and getting no response....I DOUBLE CLICKED on the artist and lo and behold that artist's albums suddenly appeared locked in with the little plus sign .....sooooooooooooo....do I have to double click on all 3500 artists now??? BTW LOOOVING MM3 can't wait til its all perfect and stuff...
I am so confused!!!! So not being a gold member, which I will happily become, I was just waiting for the final version, always seems safer. Anyway - this whole new Artist/Artist Album node is a bit of overkill. Instead of just like 5,000 artists I now triple that with Artist/Artist Album entries, it's overkill for me and takes to long to find what I want. Plus, like someone else said, a lot of those are just empty. Besides going gold has anyone found a way to show just a separate ARTIST only node?
MM3 will allow you to choose which nodes you want to see. Including the choice for Artist, Album Artist, (All) Artists nodes.
Extensions: ExternalTools, ExtractFields, SongPreviewer, LinkedTracks, CleanImport, and some other scripts (Need Help with Addons > List of All Scripts).
-
- Posts: 7
- Joined: Fri Sep 14, 2007 6:22 am
-
- Posts: 2283
- Joined: Tue Aug 29, 2006 1:09 pm
- Location: Kansas City, Missouri, United States
Have you tried using a 'clean' database? I mean, deleteing/renaming the 'old' database likely left from previous betas, and then starting monkey back up allowing it to create a new database.
I don't suffer from this anymore, so it doesn't seem to be a universal bug, something more specific to you guys, you know? (thus my mentioning the Database)
I don't suffer from this anymore, so it doesn't seem to be a universal bug, something more specific to you guys, you know? (thus my mentioning the Database)
-
- Posts: 2283
- Joined: Tue Aug 29, 2006 1:09 pm
- Location: Kansas City, Missouri, United States
upgrade issues
Yes, the fix assumes that you delete any problematic databases generated by previous beta builds. i.e. the final build should support:Just to note, I don't recieve this bug with a Clean Database, nor a 2.5->3.0 Database. :\
1) upgrade from MM 2.5
2) clean install
-Rusty