Super playlist [7853]

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Super playlist [7853]

Re: Super playlist [7853]

by Onweerwolf » Mon May 30, 2011 9:45 pm

I see, I initially thought the folders referenced above were 'folders of playlists with subfolders' instead of actual windows structured folders.

I wasn't commenting on the best way to implement it.

Personally I would think Peke's suggestion is the best and easiest. If I read it correctly is exactly the same as what i suggested in my above post.

If you go with nodes you also have to make sure that playlists can reference those nodes, which currently isn't possible (I think?) and it doesn't really serve a purpose as the process of making the autoplaylists is a one-time thing only for each parent playlist.

Hope it gets implemented soon. I've been waiting for this for years (http://mediamonkey.com/forum/viewtopic.php?f=4&t=25020)

Re: Super playlist [7853]

by nohitter151 » Mon May 30, 2011 8:10 pm

Onweerwolf wrote:
He is correct though.
No. You've missed the point of the post, which was comparing chrisjj's suggestion for implementation, and Peke's suggestion, which are two different ways to achieve the same end.

Re: Super playlist [7853]

by Lowlander » Mon May 30, 2011 7:39 pm

Onweerwolf wrote:He is correct though
Actually no, this takes care of that problem: http://www.ventismedia.com/mantis/view.php?id=5418. The All node suggestion from Chrisjj won't, it just provides a quick access method to all tracks belong to parent and child playlists (like the All nodes in the Location node).

Re: Super playlist [7853]

by Onweerwolf » Mon May 30, 2011 6:49 pm

nohitter151 wrote:
chrisjj wrote:
nohitter151 wrote:The reason to provide none is because autoplaylist criteria could be used instead.
Wrong.
Compelling!
He is correct though. There is no way to make an autoplaylist that contains all tracks from all 'child playlists' from a certain 'father playlist' unless you manually tick all of those playlists yourself in the autoplaylist config screen. The problem with that is that once you decided to make a change, like say moving a child to a different father then the child's tracks are still in the autoplaylist until you go into the config screen and manually remove that playlist, which is really pretty annoying and bothersome.

So I would second this request. Personally I believe the easiest way for this would be to have an autoplaylist criterion that says: [playlist = "playlistname" and including all child playlists (if any)] or something like that.

And frankly i'm surprised that this hasn't been implemented in MM4 yet. This is one of those very few issues where iTunes is still ahead of MM.

Adding this will improve the range of possibilities for autoplaylist creation dramatically.

Re: Super playlist [7853]

by chrisjj » Mon May 23, 2011 4:57 am

Guest wrote:at the end of the day with the current implementation you can't select a parent to select all it's children
The "All node" proposal does not change that. What it does is provide an additional sub-node that when selected, shows all the parent's descendants.

Re: Super playlist [7853]

by nohitter151 » Sun May 22, 2011 6:43 pm

chrisjj wrote:
nohitter151 wrote:The reason to provide none is because autoplaylist criteria could be used instead.
Wrong.
Compelling!

Re: Super playlist [7853]

by chrisjj » Sun May 22, 2011 5:38 pm

nohitter151 wrote:The reason to provide none is because autoplaylist criteria could be used instead.
Wrong.

Re: Super playlist [7853]

by nohitter151 » Sun May 22, 2011 3:11 pm

chrisjj wrote:
nohitter151 wrote:
chrisjj wrote:I would tend to think that the situation for playlists is much different than for browsing folders, since one may not want an "all" node for every single parent playlist.
I see no difference there. One may likewise not want the All node for all folders. But that's hardly a reason to provide none.
You're right. The reason to provide none is because autoplaylist criteria could be used instead.

Re: Super playlist [7853]

by chrisjj » Sun May 22, 2011 2:57 pm

nohitter151 wrote:
chrisjj wrote:I would tend to think that the situation for playlists is much different than for browsing folders, since one may not want an "all" node for every single parent playlist.
I see no difference there. One may likewise not want the All node for all folders. But that's hardly a reason to provide none.

Re: Super playlist [7853]

by nohitter151 » Sun May 22, 2011 2:36 pm

chrisjj wrote:
nohitter151 wrote:It will require only one click to view this playlist after its creation.
Well, I am really glad no MM designer thought that a good substitute for the All nodes already present in the tree. What a PITA it would have been for the user to have to create an auto-playlist for each one.
I would tend to think that the situation for playlists is much different than for browsing folders, since one may not want an "all" node for every single parent playlist.

Re: Super playlist [7853]

by chrisjj » Sun May 22, 2011 12:16 pm

nohitter151 wrote:No, it is to add autoplaylist critera so that the autoplaylist, which is a parent of other playlists, contains all sub-playlists.
Then that's yes, not no.
nohitter151 wrote:It will require only one click to view this playlist after its creation.
Well, I am really glad no MM designer thought that a good substitute for the All nodes already present in the tree. What a PITA it would have been for the user to have to create an auto-playlist for each one.

Re: Super playlist [7853]

by nohitter151 » Sun May 22, 2011 11:39 am

chrisjj wrote:
nohitter151 wrote:
chrisjj wrote:The All node I request will provide one-click display of all tracks of any playlist just as the All node does currently for Library nodes. Peke's auto-playlist criteria will not.
Yes, it will. Maybe you don't understand his request.
I understand Peke's request requires the user to add an autoplaylist for every parent playlist for which he requires to view all tracks. If you can show how he can do that in one ciick, please do.
No, it is to add autoplaylist critera so that the autoplaylist, which is a parent of other playlists, contains all sub-playlists. It will require only one click to view this playlist after its creation.

Re: Super playlist [7853]

by chrisjj » Sun May 22, 2011 10:53 am

nohitter151 wrote:
chrisjj wrote:The All node I request will provide one-click display of all tracks of any playlist just as the All node does currently for Library nodes. Peke's auto-playlist criteria will not.
Yes, it will. Maybe you don't understand his request.
I understand Peke's request requires the user to add an autoplaylist for every parent playlist for which he requires to view all tracks. If you can show how he can do that in one ciick, please do.

Re: Super playlist [7853]

by nohitter151 » Fri May 20, 2011 2:58 pm

chrisjj wrote:Incorrect. It is extremely important to my request. The All node I request will provide one-click display of all tracks of any playlist just as the All node does currently for Library nodes. Peke's auto-playlist criteria will not.
Yes, it will. Maybe you don't understand his request.

Re: Super playlist [7853]

by chrisjj » Fri May 20, 2011 5:13 am

nohitter151 wrote:Whether it's in an "All" node or in a top level playlist is not important to the request.
Incorrect. It is extremely important to my request. The All node I request will provide one-click display of all tracks of any playlist just as the All node does currently for Library nodes. Peke's auto-playlist criteria will not.

Top