This should be fixed in 2277: https://www.ventismedia.com/mantis/view.php?id=17150#c60466 OK thanks ... I see now how Lukek was see the missing view .. he navigated to "Rock" by clicking the word under the Grid's tile ... I was navigating to the inline expansion of "Rock" by clicking the thumbnail ...

Not sure which syntax do you mean and in which collection sub-nodes, but I don't think that there was a change in this area. I was using fieldname:foo syntax. I now notice that it is still an open issue; https://www.ventismedia.com/mantis/view.php?id=16221 It seems more reliable to me now ... but m...

Ludek wrote: ↑Mon Nov 30, 2020 12:42 pm I see it there: https://www.dropbox.com/s/ijk010ppptjpp ... 0.png?dl=0

You're lucky ... you must have paid extra

I don't see it. I can send a download link to my db and json file if it helps?

Ludek wrote: ↑Mon Nov 30, 2020 8:54 am Tracked as https://www.ventismedia.com/mantis/view.php?id=17149

Thanks.
Your Mantis entry specifically mentions the genre line in the report.

I don't see it myself, but from what Lowlander reported, the problem may affect other lines in the same section of the report.

I have complained a number of times about filter syntax not working inside collection sub-nodes. Now it is working :D ... I didn't notice anything that accounts for this improvement in Rusty''s "changelog" notes .... has there been a change in this area? Anyway, I am so pleased .... that was my #1 i...

Why no List By Album View for Genre sub-node? Is this as designed? ... if so, what is the reason?

With me Artist, Album and Year are also over. I assume this happens when you've played your files a lot and multiple times per file as well for many files. It won't be that. My play history shows that the average play count, calculated across all of my tracks, is a bit over seven times. So that wou...

I suppose the only issue is the 'Warning: ' preface. We can remove that. I don't think that there is any problem with the word "warning" ... the "will overwrite a an existing xxx installation" and the exclamtion mark are the alarming parts. It would be good if people could be reassured that it does...

Does this message have to be so alarming?

ie. maybe assure the user that their database and config options will not be "overridden"

I now see what you mean as I was able to reproduce that adding a column Good, thanks. I prefer the MM5 method where Column settings can be configured per View. That's fine. I am not asking for the new behaviour to removed ... just for he MM4 behaviour to be retained, as an option . Even you may fin...

Is this possible? I have played more tracks per genre, than I actually have tracks per genre? Maybe the "library" stat is calculated as average per tracks per genre, from just genres that actually have tracks? And the "Played" stat is the average plays per genre, from all genres, regardless of whet...

Yes, Views have independent column settings, so if you didn't have Added in the List (by Albums) it won't be there when switching from a View that had this column. Each View uses it's own column settings. And for any MM person where this is TLDR; it is this new MM5 feature change, from MM4, that I ...

I selected a Playlist which was ... A thought. Maybe the difference we are seeing could because of the Manage Views facilities, where default overrides can be configured for List, List By Album, and Grid Views ... but not Playlists AFAIK. Where are the overrides stored? ... If they are in the json ...

I still don't follow. I selected a Playlist which was shown in List View. Enabled the Column Browser and switched to List (by Album) and the Column Browser remained. Like MM4 whatever columns a View has are retained for that View when switching around. Whatever file was selected remains selected wh...

Is the Help text going to go through beta test?
I agree with the OP, that MM5 changes are significant ... So a beta test of the documentation seems critical for MM5 success.