This morning somehow MC reset all my Content View columns to include *only* Name, Album, Artist and Filename...
Maybe this will help in the hunt...
If I look at the iPod, fewer columns display than when looking at the Media Library. If I adjust a column width when looking at the iPod, MC9 updates some global column width table to a) only the columns on the iPod, and b) the column widths of the iPod.
PleaseI would really like to see each entry in the Tree on the left have its own Column Width Table definitions. If the Column Width Table of an entry had not been customized, it would use its parent's (and so on up the Tree). I believe the Default Sort Order should be specific to the tree entry you're looking at, also. Music and Images just sort differently.
This product - MC9 - with its multimedia approach to life, truly needs this feature. Bitrates, Replay Gain, etc. should be turnable-offable for the Images part of the Tree, while Height/Width are turned for Audio, etc. It seems that the more one uses MC, the more one needs this capability.
Another example of the value of this: I want totally different columns than Artist or Composer for images. But I'm reluctant to add them, because I have so many columns enabled for audio. If Column/Width/Sort definitions were "per tree entry", I could set up unique categories for each media type, but have efficient use of the right window. Re-using "Artist" for "Subject" in images is a bit confusing.
Bug reports1. I am using Custom 1, Custom 2 and Custom 3. The names I've chosen appear in the Column Headers, but if I right-click the header bar, the context menu contains "Custom n", not the names I chose in Tools / Options / Tree & View.
2. Statistics - Artist/Album uses the field that groups under (Multiple Artists). That isn't useful in statistics; "(Multiple Artists) - The Avengers Soundtrack / 4" provides no usable Artist information.
3. The Sort Headers don't work in Statistics. This is what I'm dealing with:
With >1000 Artists and >1000 Albums, scrolling down the list to see who was how many is tedious and uninformative.
4. I believe there needs to be a pure Artist statistic, which leads to...
Suggestion: Those Stat definitions remind me a lot of View Schemes. How NICE it would be if you could populate the Stat definitions from the View Schemes (with a couple extras like Overview), and generate the entry names using the items selected in the View Scheme. Then you wouldn't have to figure out what Stat definitions the world needs (and write them); we could all set up our own! I would even set up View Schemes I never use for viewing, only for Stat summaries.
Hmmm... now that I've written this, it seems so obvious that a person would want to see Stats with the same outlook they'd implement in View Schemes. The Stats should even use the Search qualifiers so we get exact stats for each View Scheme's selected files and structure.