It seems to me that the sample management strategies possible with Tidal/SuperDirt are limited.
For unpitched sounds, you can have directories full of the same kind of sound, like the 90 sounds in the snare
folder of the extra samples.
Or, you can have a directory that constitutes some sort of 'kit' of different kinds of sound, like the cpu
and cpu2
folders.
In that kind of setup, there is a trick I have sometimes used for my own sample banks. I put an numerical index at the start of the file name, and then arrange the files into some sort of musical order, for instance:
00kick01
01hat01
03snare01
04hat02
05kick02
06hat03
07snare02
08hat04
etc up to 32 sounds
If I then n (run 32)
through that folder, I get a beat of sorts, and I also know that my snares and kicks are at predictable indices. (But I do end up with an awful lot of hats!)
For pitched sounds, you can have something like the rash
directory, which is I think about five octaves of a single synth sound. Again the numerical index means that you can probably then play melodic/chordal material reliably.
However… there is a caveat. The order in which SuperDirt imports samples is dependent upon the operating system, and I'm not certain that is always consistent. So, my cpu:13
might be different from yours! (Certainly with the default sample banks in the Estuary platform, I've found that the sample indices do not correspond to those on my machine.)
For consistent sample management, eg mapping samples to ranges of notes, I suspect it would be easier to send midi to an external sampler running in a DAW or similar. But then, you can't easily apply effects from Tidal.