It took some investigation yes and yes, it can happen with simpler patterns as well, although usually this doesn’t crash the machine it just plays the programmed sequence wrong. I haven’t been able to pinpoint exactly what the cause is but it al revolves around the arp, voice allocation and sound locks (that have the arp enabled).
Some are easier to replicate than others, but for instance bug 3 is easy to replicate, and clearly not the intended behavior. I was kinda surprised that nobody (including myself) had noticed/reported it before.
@Blasted_pingin
Yes for instance if you soundlock sounds with the arp activated on T1, this will affect the arp on T2 while voice stealing is off. This shouldn’t happen. See bug 2
@Kraus @Looper I’m 98% sure your safe as long as you don’t combine it with massive sound locking. I don’t recall ever having a problem with every track running an arp while not sound locking the arp as well. Might want to confirm that before you rely on it live though it’s been almost a year since I looked into this.