MM3 VS. MM2.5 Properties Problems

Beta Testing for Windows Products and plugins

Moderator: Gurus

cmx
Posts: 367
Joined: Sun May 21, 2006 11:56 am

MM3 VS. MM2.5 Properties Problems

Post by cmx »

I have many compilation albums....

-in MM2.5xxx the Album Artist is properly read as "various" allowing proper grouping for an album...

-in 3.0 the "album artist" is read the same as the "artist" for each track in a compilation...this creates a seperate "album" for each track in the album view...

What is different or what am I doing differently in MM3.0...I need the same functionality I've always had in order to read the compilation properly...

thanks for any help here...

Devs....THANKS for the great improvements...I now have proper tag access to about 40k M4A tracks...fantastic...
cmx
Posts: 367
Joined: Sun May 21, 2006 11:56 am

Album Artist /Compilation Issues MM 3.xx

Post by cmx »

After looking at this awhile...I'll assume it is just a database issue in the new beta that will be tweaked and worked as time goes on...

In 3.xx it seems that no matter what the Album Artist value is, the Artist field takes precedence, and a seperate "album" entry is created for each different artist per track....



In side by side comparison between 2.5xx and 3.xx, it seems 3.xx simply isn't recognizing the Album Artist field in any of my tracks....

Even if my tracks are tagged properly as "Various" etc., when they are read into 3.xx it seems that for the most part whatever is in the the "Album Artist" field is replaced with the same entry that is in the the "Artist" field....

Also, even if I carefully re-tag the Album Artist tags with "Various" and group a compilation together, it still has an individual entry in the nav tree for each individual artist (and the new album graphics display has an individual cover for each artist in the compilation).

Hopefully this is a simple thing and will be resolved easily.

Thanks for the great product...I can't express the relief to have the ACC tag reading...whole sections of my collections have been "in limbo"...

I have a very large collection and depend solely upon MM- it is simply the only practical program that is able to deal with Terabyte levels of data...please keep this in mind as development proceeds....We all appreciate the custom features and sexy tools, but please keep the basic functionality for large collections in mind...
Post Reply