I see. I imagine that when a project is saved, the (re)samples have to be written back to the card (can’t store everything onboard forever). Renaming should be trivial based on what you indicated.
[EDIT]
I was stricken with insomnia last night as I pondered the potential for the random effects applied to sample slicing. I arrived at two conclusions.
1] While it is surely possible to concatenate .wav files (say, of AMEN and funky drummer) to enable a broader pool of subsamples to be randomized over specific points, it would be groovy if there were a way to internally (within Tracker) gather together samples into a basket from which the slices could be drawn. A “join” if you will. This would combine the AMEN with the funky and allow a slicer to operate on the combined sample to extract all the slices: [A, M, E, N, f, u, n, k, y].
2] A ‘subset’ function would be key. For example, if the AMEN sample is comprised of [A,M,E,N] slices, one could select a pool of only the slices (e.g [A, M, N]) for the random effect to draw slices from. Maybe this functionality exists?
Now, combine this “subset” with the ‘join’ and you’d be able to come up with two separate slice pools, eg: [A, E, u, y] and [M, N, f, n, k y], if you wish. (In my mind, vowels were percussive, consonants were melodic, and y was a bit of piano).
If, in the course of applying the beat slicer, many little files are made, this subset function would seem pretty easy to implement. The interface to do so would be the hard part.
Anyhow, just voicing an idea.
