Subsequent to me posting this thread (and building off its core thoughts):
… It just occurred to me that it could be really cool to have sub-divisions within the ‘Smart’ system.
Perhaps one user makes different genres of music, eg lo-fi hip-hop sometimes, but hardrcore trance at other times. I think that under the current system it’s not possible to quarantine these apart under ‘Smart’, meaning that if the user just tags everything they like, the output would be in the middle of lo-fi hip-hop and trance, which is likely undesirable.
Perhaps one user wants to have a section for super experimental polyrhythm content, but then another for straight techno.
… Right now I think it’s possible to achieve this already via a workaround, but it’s a little clunky… I think I’m going to use the ‘heart’ function for creating my main pool… And then be more dynamic with the ‘Smart’ tag… ie each time I use it, I can highlight the ‘hearted’ pool, then make a fresh new tagging within that of the Smart tags, based on the goal I’m aiming for.
Maybe this is a niche request and I’m not sure how broad the appeal would be?
So you’re suggesting multiple ‘smart’ sub-categories? This might be possible to implement in a future update. Regarding the crashing issue, please send us the crash log, and we’ll investigate and fix it as soon as possible.
Yes - multiple Smart sub categories… But maybe an easier way to do this is to just improve the ‘Packs’ system. Currently when I drag a pattern to a pack, it ‘moves’ it from the source, rather than ‘copies’ it. So currently a pattern can only be in one place at a time.
If you made it so a single ‘lo-fi hip-hop’ pattern could be in both my ‘lo-fi’ and my ‘hip hop’ packs, I think it would be better.
Then if you add a '‘batch manage’ feature, we could easily ‘highlight all’ and with only two clicks take that whole ‘Pack’ in or out of the currently active Smart algo.
Re the bug: I spoke with your support via email yesterday and sent crash reports… But I followed up to say I’ve pinpointed the problem:
Deselecting ‘Favourite’ tag while ‘Favourites’ is highlighted also causes the exact same instant crash.
Deselecting ‘Smart’ while ‘Favourites’ is highlighted = no crash
Deselecting ‘Favourite’ tag while ‘Smart’ is highlighted = no crash.
… And now I think about it, I can understand the principle issue here; as soon as the ‘Smart’ tag is removed, that preset should no longer be appearing in the selected ‘Smart’ pool, but it still does, so then it ‘does not compute’ and crashes!