MediaMonkey forum

> And even if it would have it would take really long to load things with many files selected

I doubt it. Look how quick is presenting a tracklist property drop-down containing 1000 artists.

> I can only imagen how long the Artist submenu would take

> I would assume that the Playlist submenu would take a multiple of that as it's many times more complex with AutoPlaylists being involved

If this feature takes too long for you, just don't use it.

> I don't think it's scalable beyond a few tracks

It will scale fine - linearly.

chrisjj wrote: Look how quick is presenting a tracklist property drop-down containing 1000 artists.

That's different as it just lists all Artists, in Find More from Same it needs to evaluate each track and then sort the full list.

chrisjj wrote:It will scale fine - linearly.

I doubt it will, you can see issues with speed in the Media Tree where more complex queries are used. AutoPlaylist also take a while to load (and mine aren't overly complex). There is also the usability of scalability. If it shows a 1000 playlist or artists it no longer is a very useful feature. Here it already takes 5s to find the Playlists one track is on (only 6) on a library with only a few playlists. I can only imagen what happens when you scale that to 100 or 1000 or more tracks.

Find More from Same on multiple files should only be implemented if it does so for all fields it works (consistency) and if it can achieve it with decent speed, otherwise you're just replacing one inconsistency with another or worse with something that works poorly. In that case it would be consistent to disable multi-file Find More from Same.

> That's different as it just lists all Artists, in Find More from
> Same it needs to evaluate each track and then sort the full list.

It has to do evaluate and sort for Artist.

> Find More from Same on multiple files should only be implemented if it does so for all fields it works (consistency)

Crikey, if that was a MM deign principle, there would be lots of features missing... inc. the FMFS Playlists sub-menu itself.

> and if it can achieve it with decent speed, otherwise you're just replacing one inconsistency with another or worse with something that works poorly.

Takes time is not "works poorly". See e.g. "Unsynchronised tags"

Then what have you been complaining about for such a long time. You're the one that hammers the most on consistency. Of course until it gets in the way of what you need.

chrisjj wrote:if that was a MM deign principle, there would be lots of features missing... inc. the FMFS Playlists sub-menu itself.

There are 2 solutions to this inconsistency. Either it works on all selected tracks or it isn't available. Both would address the current inconsistency. I fear the former won't work (well) so the latter is the only viable alternative (I don't have anything against it working on all selected tracks, it would be ideal, I just don't see it working well/at all).

chrisjj wrote:Takes time is not "works poorly". See e.g. "Unsynchronised tags"

This forms no problem for me as Unsynchronized Tracks is an analysis performed on tracks and it's understood this will take a while. On the other hand Find More from Same is a navigational tool and should work instantaneously.

> Find More from Same is a navigational tool and should work instantaneously.

Then since it already does not, you ought to file a wish to that effect.

Regardless, it should give the correct results.