I’m familiar with the legacy pattern chaining from my DT and DN 1.
My issue is this: When I cue up a chain (using legacy or new chain menu) while any pattern is playing, it skips the first pattern in the chain, going straight to 2nd pattern, and first pattern in chain is played last. (EX: Input: A01-A02-A03 is played as A02-A03-A01)
If I create a pattern chain while playback is stopped, the chain plays as intended. (EX: Input: A01-A02-A03 is played as A01-A02-A03)
I tried searching forums for bug report or similar post, but didn’t see anything. This seems pretty major and noticeable. Should I post a bug report, or is this user error? Some new setting I’ve inadvertently activated?
Sounds pretty buggy. I’m pretty reliant on pattern chaining also so not too pleased to hear this in considering the upgrade.
So, to be clear, you’re on (example) pattern A04 and you want to move to a chain of A01-A02-A03, so you hold PTN and then hit trigs 1, 2 and 3 in that order while still in the A bank. You can see at the top of the screen that it says “A01-A02-A03” correct? Then, even after confirmation of input, when A04 pattern changes into the supposed first pattern in chain, that first pattern is A02, which is followed by 3 and then by 1, correct?
So, I’d try A03-A01-A02 and if it plays 1 - 2 - 3 I’d probably report it as a bug and use that workaround until they fix it.
You could also report this to support and ask for help, but if it’s a bug then it’s not something you’ll be able to resolve through troubleshooting, the only recourse will probably be using workarounds until it’s addressed in a firmware release.
Sucks though, good luck.
100% correct.
For the time being I’m using the exact workaround you mentioned.
I’ll send a long to support and post any updates here. Thanks!
1 Like
For sure, sounds good. Unfortunately, I can’t think of any reason or setting which would explain that behavior so just from my perspective I don’t know what to call it other than a bug.
You can also submit a bug report by detailing it in this thread, here:
but I wouldn’t hesitate to contact support directly and have them validate that they’re able to recreate the issue.
1 Like
Just going to wrap this up here with the email response I got from support:
Thank you for reporting!
We’re already aware of this issue and are actively working on a fix, which will be included in the next OS update.
Sometimes just that confirmation is helpful, at least psychologically, so that you don’t feel like Mugatu.
Hopefully it’s on their short list of things to do!
2 Likes
haha 100%.
It’s always good to find out it’s a known issue, and on the short list for the next update!
1 Like