No, maybe I haven’t said it right but I think my point was missed.
I do believe each OT user has their own workflows. It depends on the style, other gear plugged, studio vs live config and so many possibilities to play it that there can’t be bad and good. I wasn’t being judgmental, that was not my intention.
What I failed to say was that you don’t need to use one project per track. It adds no real benefit in the scenario you described.
First it forces you to load a new project each time you want to change to another beat.
Secondly there is a limit to the number of project an OT can handle.
Thirdly it makes it harder to copy/paste between your beats.
And I could continue the list…
Only benefits I could imagine are the fact that you can really know what is saved or not, and that you can have a large sample slot list for each beat…
But I believe you could reach a more comfortable workflow by using for starters what I described earlier: 1 Part/4 patterns per beat for instance, so 4 beats per Bank (64 beats per Project).
This would make transitions a bit easier, and let you play in one box.
Regarding the sample slots limitation: most of the time I use sample chains, that I play in Slice mode, live playing/recording the slices for each track.
You can have 64 slices per sample slot, and 128 slots for each Static and Flex list, so that makes some large number of samples in the end…
Regarding memory limitations: I use mainly Static samples (for drums, waveforms, fx, even voices), while keeping most of the Flex space for live recording/mangling.