That’s true if you’re using 120 samples. If you have less it will work out the minimum amount of spacing required to align each to an endpoint.
@kalin at the moment its not possible to do what you are asking. I actually have to code in there that would do it, theres a few choices around how it can align the sample boundaries but for user simplicities sake I just picked one that would keep the files as small as possible.
When it aligns each sample to the nearest possible endpoint, it minimizes the total amount of extra padding required for the whole chain. It’s a bit gnarly under the hood because changing the amount of spacing on one sample might change the alignment of all the other samples but I found a neat way to do it.
Another options is to use a fixed number of slots per sample, which is what you are saying. It’s less efficient space wise but means you can modulate start point with an lfo and always get the full sample played.
Honestly I had no idea what people would prefer so I just picked one.
I wrote this during some down time at work and wasnt even sure if people would ever use it. It can also support an arbitrary number of sample slots which means it can be used for chains for dt/ot too, I didn’t put that code in the UI as well because I had no way to test it at the time.
Really appreciate everyone checking it out and giving some feedback. I’d like to revisit it, maybe later in Jan as I have a bit of time atm. If there’s anything else you’d like to see it do please let me know.