It should be possible to determine how many pattern loops should be exported.
What is the problem?
Play offers great chance parameters, but unfortunately the export is always limited to one pass of the current pattern.
What do you want to achieve?
For example, if there is a loop that uses chance to trigger an action every second pass, it would be useful to specify to export 2 loops to capture the change.
Are there any workarounds?
Use multiple patterns to capture each action manually, but this is tedious and likely to not cover all the different actions you can get with chance.
Thanks for the reply!
I think variations and patterns wouldn’t cover random events, right?
Simple example : track where the actual sample is randomized for every step. This would sound different every time when I use the Play to perform, but it would be really hard to export (if I’m not missing something).
Another example : I have a sample that covers 8 bars and want to play that back. This works fine when I set the track speed to 1/2, but the export will only cover the first 4 bars, right (haven’t tried to export that one, just guessing)?
Thank you. Yes, you are right, I’m understanding your wish better now.
One detail:
Do you mean full passes through the pattern? Can we call them pattern loops?
Bars… are hard. You can have tracks of different lengths running at different speeds, they can go through up to four pages. If the user (and the Play!) need to count bars, it can be difficult, and this is not even getting into different time signatures.
I have tweaked the description a bit more to talk about “actions” instead of “variations”, since the term “variation” has a specific meaning on the Play. Please check.
Thanks!