Make patch "playlists"?

[franckaubry]

Hello all!

Does anybody else see a need to be able to organise an ever growing collection of patches?
Just by going through the tutorials and testing I have long list of private patches that are getting very hard to browse through and find back too.
At this point my "learning" patches would be very good to get out of the way visually but some of them I don't really want to delete either.
I was also thinking that it could make more sense to be able to release a whole public patch "playlists" sometimes if the theme is related or it's the whole iterative process of a project f.ex.
Opening up for playlists might be a very good thing for the documentation as well. One ops documentation could link to a group of different examples patches that uses that op, or there could be official playlists, like an "Instances" or "Copy Cat" playlist.

A patch would be able to exist within several playlist, as to not make them as rigid as a folder system.

[franckaubry]

Ok... I just found out about the "Namespace for filtering" in the Patch settings... 🤦‍♂️

You have to manually go into each and every single patch, which is a bit cumbersome, but it work as playlist function, so that's very cool and will clean things up quite a bit. 👍🧹