Hi there, looking good in 2233 so far. Thanks!

Thanks.

Sorting of 'List (by album)' should be fixed in the next build and we're working on the others (see: https://www.ventismedia.com/mantis/view.php?id=16437 ).

-Rusty

Thanks for your feedback. Will check.

Hi there,

Many of the issues seem to be fixed with 2232, however a number of issues remain:

When I refresh any tab that uses a custom view based on "List (by Album)", the sort order, displayed columns, column order and column widths all still revert to the defaults for "List (by Album)". When I close MM and reopen it, the custom view is initially displayed exactly as defined, until the next time the tab is refreshed.

I also noticed that if I edit a custom view that is already in use on a tab, the tab using that custom view once again reverts to default sort order (just like the issue with refresh). Again, closing MM and re-opening, the sort order is correct again (until the next time the view is refreshed or the custom view edited).

In addition, changes made to column widths or column order in a tab that is using a custom view don't seem to be retained when MM is closed and re-opened. I would expect at least column widths to be retained since there is nowhere to define column widths in the custom view definition itself - I'm not sure what the intended behaviour is for column order (or displayed columns) since these are specifically defined in the custom view.

I did rename persistent.json before any of the above testing. Also to note that automatic column sizing is not enabled.

Hi,
Can you test in 2232 when it gets out?

Hi,

This makes no difference. As I've mentioned, I've gone even further than this and completely renamed the whole %appdata%\MediaMonkey5 folder, started completely from scratch, rediscovered my music collection and immediately the exact same symptoms.

I can try it on a completely different PC too, but I wouldn't expect it to make any difference...

Hi,
Try to rename persistent.json to !persistent.json and then start MM5. You may have some configuration conflicts that exhibit in such behavior.

I rebuilt the database and am now finding that the issues remain the same when I refresh the view, but if I switch to a different library node and then back to the Music node, the view is displayed correctly.

The refresh operation seems to be the thing that is really buggy at the moment.

EDIT: After a while, the above no longer seems to be working. I am noticing that sometimes when I switch to a node with a custom view, the correct sort order is briefly shown, then it reverts to the default sort order. There are just so many weird and inconsistent behaviours when using Custom Views, it's difficult to keep track of it!

I have also had MM crash multiple times with 2230 while doing this testing. The crash does not result in the usual option to submit a crash log. When I restart MM5, my custom views have completely disappeared. This is a new behaviour with 2230.

Still completely broken for me with 2230 I'm afraid. I removed the custom view I previously created and started again.

I am still getting the sort order I configure in the custom view not being applied and I still get the issues when I refresh where it shows no tracks, or only 2000, 4000 or 8000 tracks (always exact multiples of 2000) and the column browser randomly not showing anything at all independently of what is shown in the tracks view.

Since this seems to be difficult to replicate, and yet I have this issue completely consistently, even starting with a completely fresh profile and database and just re-scanning my music library, what could be the trigger? What further information can I get to troubleshoot this beyond what I've already provided?

Hi,
This should be fixed in Next build.

At least my tests show it is fixed.

Any feedback on this? MediaMonkey 5 is becoming increasingly unusable for me because of this issue.

Still massive issues with custom views in 2229 despite https://www.ventismedia.com/mantis/view.php?id=16379.

Behaviour pretty much the same as before. I uploade a video showing what I see.

https://youtu.be/i9TQQUCCyKA

Thanks. Will check.

There are still issues with refresh on custom views in 2228 - did the fix not make it into this build? There does seem to have been a change in behaviour however:

Now, when I hit refresh in a custom list view I am getting different results on each refresh, with various combinations of the below on each refresh:

Sometimes the sort order I've defined is used, sometimes the default sort order by Album name is used.
Sometimes all tracks are shown, sometimes only 2000, 4000 or 8000 out of the total 8318 tracks is shown.
Sometimes the column browser is shown, sometimes that panel is blank
Sometimes the entire track list is blank

This only seems to happen for the Music node (top level, All Tracks etc.) - other nodes, including custom collections, seem to be behaving correctly.

Note that my Music collection is also customised slightly with a criteria rule that excludes a couple of specific genres.

Thank you, video helped a lot, the bug was caused by calling "Refresh" when custom view was active, we reproduced it then, should be fixed in the next build.