MediaMonkey forum

...until the tree is collapsed and re-opended again.

This always worked in previous versions. Initially I though it might have been related to the Auto-Organise functionality (which I don't use) but I cannot find a way of getting this functionality back to normal

SimonW


mod edit:
http://www.ventismedia.com/mantis/view.php?id=5211
shortened tite from "New album is not appearing in the Album & Album Artist tree"

How are you creating the new album?

updating some existing tracks with a new album via the mm track list?

adding new tracks with a new album? via add/rescan or monitored folder?

updating some existing tracks with an external tagger program?

1) treeview open
2) delete all the tracks for a specific album (library only)
3) the album is gone from the treeview
4) go to file->add/rescan and tick the folder where the album is located
5) treeview is not updated - collapse / re-expand - now there's the album again !!

Simon

check bottom of tree, I think new subnodes are added to bottom of list. Perhaps regression, or maybe to help performance on large library, I dunoo.

ahhh -thanks !
whenever I've added new albums before they-ve always appeared 'in place' - never thought to look at the bottom.

Seems a bit strange to me though - always worked with v3 before...

simonw wrote:ahhh -thanks !
whenever I've added new albums before they-ve always appeared 'in place' - never thought to look at the bottom.

Seems a bit strange to me though - always worked with v3 before...

Yes, its very possible regression, will leave here in case any dev happens to comment in the near future, else will open ticket for it.

> at the bottom. ... Seems a bit strange to me though

I see the same problem often on the Playlists node.

chrisjj wrote:> at the bottom. ... Seems a bit strange to me though

I see the same problem often on the Playlists node.

To my recollection, this has always been the case on playlists, ever since I started using mm (2.4.x).

> To my recollection, this has always been the case on playlists

Agreed - It is been on my Bugs To Be Reported list since V2.5.

I believe for performance considerations certain processes don't refresh properly in MediaMonkey.

Lowlander wrote:I believe for performance considerations certain processes don't refresh properly in MediaMonkey.

Performance of the programmer?

If you take in account that some users use older systems and might have large libraries performance of MediaMonkey can become an issue. I can see this myself on my aging system, so I understand this approach as it makes MediaMonkey usable for a larger audience. I like to call this the RovingCowboy effect. MediaMonkey is designed so that RovingCowboy can still run it on his antiquated Windows 98 system (although I believe has upgraded since).
Of course complaints about this behavior are certainly valid and I really hope that direct refresh can be implemented without causing performance issues.

> I really hope that direct refresh can be implemented without causing performance issues.

Have you made a Mantis entry to that effect?

I will.

Teknojnky wrote:I will.

Great. Would you please reference the following five Refresh failure reports, apparently ignored at the time? Thanks.

V3.0.2.1131 Refresh fails to refresh tree
http://www.mediamonkey.com/forum/viewto ... &sk=t&sd=a

1164 Send to... device fails to update the device node...
Refresh likewise fails.
http://www.mediamonkey.com/forum/viewto ... &sk=t&sd=a

V3.0.2.1134 Gold - Filtered views update fails on tag change
Refresh doesn't remove it
http://www.mediamonkey.com/forum/viewto ... sh#p128458

V3.0.2.1129 - failure of tree to refresh on field edit
http://www.mediamonkey.com/forum/viewto ... sh#p121995

MMV3: Four Add/Rescan issues
Note: MM3 change log: 2786 Fixed newly added/converted tracks fail to trigger a refresh of the current view
http://www.mediamonkey.com/forum/viewto ... esh#p78121