metro vs qmetro vs deferlow - explanation required
May 12 2020 | 9:20 pm
I'm currently working on a patch and try to understand why I'm getting different results when triggering it from a [qmetro] or a [metro] or a [metro] followed by a [deferlow] object. I read the helpfiles and understand there is a difference in scheduling, I just can't seem to make sense why this would apply in my patch. I extracted the section in question, it's basically 3 count loops which are being triggered by a [trigger] object in the correct sequence. When triggering it manually with [bang] the following sequence of messages is generated:
- 6 x loop1 - 96 x loop2 and 96 x loop3, alternating
This is the result I want to achieve. However, when triggering it with a [metro] object I get the following result:
- 6 x loop1 - 96 x loop2 - 1 x loop3
When using [qmetro] or [metro] followed by [deferlow] I get the correct sequence. I've been scratching my head trying to understand why this is a case, so if anybody would take a moment to check out the patch this would be much appreciated!