Probably no need to write new code, the tools are there You will be able to do this with smart playlists, if you can design the filters/queries, There is a group field, you can define as playlist name, which will save as meta data Depending how sacrosanct you hold the comment field, it can also be a user defined identifier I define live music as genre live rock, live classical... which is handy to exclude/include
On Sunday, January 23, 2022 at 9:29:41 AM UTC-8 Paul Abrahams wrote: > In a recursive playlist, each entry in a playlist can be either a song or > another playlist. This structure is very useful for classical music where, > for instance, a string quartet usually consists of four movements. > Furthermore, Beethoven's quartets are usually grouped into the early, > middle, and late quartets. Recursive playlists are also useful for popular > music, where a band's concert consists of a sequence of songs and a tour > consists of a sequence of concerts. > > The structure need not be a tree. For instance, you could create a > playlist of performances by a particular artist. > > I haven't studied the implementation of Clementine, but my guess is that > it would not be particularly difficult for someone familiar with the code > to enhance it with recursive playlists. > -- You received this message because you are subscribed to the Google Groups "Clementine Music Player" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/clementine-player/cca239c1-0f1e-4fe0-a66c-bb0614507e12n%40googlegroups.com.
