1164 Send to... playlist menu shows duplicate entries [6910]

chrisjj · Post by **chrisjj** » Wed Apr 30, 2008 4:41 pm

e.g.

I don't know why some get duplicated and others not. If anyone knows the significance of the presumably by-design divider in this menu, perhaps this will shed light.

EDIT(TC): Tracked at http://www.ventismedia.com/mantis/view.php?id=6910

GMFuller · Post by **GMFuller** » Wed Apr 30, 2008 11:46 pm

Perhaps the ones above the divider are the playlists most recently 'sent to'?

chrisjj · Post by **chrisjj** » Thu May 01, 2008 4:07 am

Well, sometimes. If I Send to.. a new playlist, it appears at the bottom of the lower part. If I Send to... that now existing playlist, a duplicate appears at the top of the upper part.

Do you get the same?

'Cos I wonder if my MM could be confused by the 'temp' entry - an orphan left when I deleted such a playlist from the tree months ago. Which I can find no way of removing.

Ludek · Post by **Ludek** » Thu May 01, 2008 7:37 am

Yes, as GMFUller wrote:

These are not a duplicates above the divider - they are the playlists most recently 'sent to'.

i.e. It is not a bug.

chrisjj · Post by **chrisjj** » Thu May 01, 2008 8:34 am

Ludek wrote:Yes, as GMFUller wrote:
These are not a duplicates above the divider

Actually, GMfuller didn't write that.

And they are duplicates. They (the entries) have the same name and behaviour.

they are the playlists most recently 'sent to'

That seems like a rather strange reason to add duplicates. But fair enough! Thanks for the explanation of the behaviour.

Bex · Post by **Bex** » Thu May 01, 2008 11:42 am

It's a rather nice feature. Very useful when you have many playlists.

chrisjj · Post by **chrisjj** » Thu May 01, 2008 12:13 pm

I guess you're referring to putting recently used at the top, rather than the duplication?

Teknojnky · Post by **Teknojnky** » Thu May 01, 2008 12:21 pm

you are correct that they are in a sense duplicates, however it is simply a most recently used (MRU) displayed on the same menu level as the root playlist, and they are only duplicate if you have used root playlists.

see my MRU list which the MRU list shows both root and sub level (including the playlist and its parent)

this is a great feature if you have highly nested playlist organization.

chrisjj · Post by **chrisjj** » Thu May 01, 2008 12:41 pm

> it is simply a most recently used (MRU) displayed on the same menu
> level as the root playlist

Agreed.

> and they are only duplicate if you have used root playlists.

FTR: or upon the bug http://www.mediamonkey.com/forum/viewtopic.php?t=28877 .

> this is a great feature if you have highly nested playlist organization.

Thanks for the tip. OOI, have you found any particular use for playlist nesting beyond cosmetic? I've found one nest-compatible command - Remove, very useful for working around Add/Scan's .m3u update failure - but perhaps there are more?

Teknojnky · Post by **Teknojnky** » Thu May 01, 2008 1:11 pm

chrisjj wrote:> this is a great feature if you have highly nested playlist organization.

Thanks for the tip. OOI, have you found any particular use for playlist nesting beyond cosmetic? I've found one nest-compatible command - Remove, very useful for working around Add/Scan's .m3u update failure - but perhaps there are more?

Well other than organization, shrug... However organization is pretty important... you would not want dozens or hundreds of playlists listed in the root playlist node would you?

I am not a super big playlist user, but I've seen people post screenshots of their playlist node with many many playlists (auto and static) all grouped up according to however they feel/use them.

I think one thing that would be a great help for nested playlists, would be in any selection dialog where you must click to select/de-select playlists, to be able to selec/de-select all child playlists. Currently you still have to select/de-select each individual child, which can be a pain when dealing with many playlists.

nohitter151 · Post by **nohitter151** » Thu May 01, 2008 1:16 pm

chrisjj wrote:> it is simply a most recently used (MRU) displayed on the same menu
> level as the root playlist

Agreed.

> and they are only duplicate if you have used root playlists.

FTR: or upon the bug http://www.mediamonkey.com/forum/viewtopic.php?t=28877 .

> this is a great feature if you have highly nested playlist organization.

Thanks for the tip. OOI, have you found any particular use for playlist nesting beyond cosmetic? I've found one nest-compatible command - Remove, very useful for working around Add/Scan's .m3u update failure - but perhaps there are more?

I nest my playlists to keep similar playlists grouped together (organization) and also so that the list doesn't get too unwieldy and long when I expland my playlists node.

nynaevelan · Post by **nynaevelan** » Thu May 01, 2008 1:22 pm

Teknojnky wrote:

Well other than organization, shrug... However organization is pretty important... you would not want dozens or hundreds of playlists listed in the root playlist node would you?

As a big playlist user I have to add my two cents. Other than organizational and cosmetic uses, having nested playlists makes it easier to work with playlists when you are looking through them and editing them. I have over 100 playlists which I have grouped into 5 or more groups, a couple of which have second and third level children.

Teknojnky wrote:I am not a super big playlist user, but I've seen people post screenshots of their playlist node with many many playlists (auto and static) all grouped up according to however they feel/use them.

I think one thing that would be a great help for nested playlists, would be in any selection dialog where you must click to select/de-select playlists, to be able to selec/de-select all child playlists. Currently you still have to select/de-select each individual child, which can be a pain when dealing with many playlists.

I WHOLEHEARTEDLY agree, this is the one major disadvantage I have with using nested playlists.

Nyn

chrisjj · Post by **chrisjj** » Thu May 01, 2008 7:28 pm

> you would not want dozens or hundreds of playlists listed in the root
> playlist node would you?

Well my "root" is Imported m3u Playlists and yes with hundreds there, it's fine.

> I've seen people post screenshots of their playlist node with many
> many playlists (auto and static) all grouped up according to however
> they feel/use them.

Fair enough

> I think one thing that would be a great help for nested playlists,
> would be in any selection dialog where you must click to select/de-
> select playlists, to be able to selec/de-select all child playlists. Currently
> you still have to select/de-select each individual child, which can be a
> pain when dealing with many playlists.

Agreed 100%. Its odd that whereas parent/child selectors work as you're suggesting in e.g. Add/Rescan folders (people would surely scream otherwise), for some reason they don't in playlists.