Hey, just wanted to share that I am also experiencing this LFO bug where LFO’s with a “BPM” time division stop following the BPM when other LFOs do not also utilize the BPM time divisions. Here is an easy way to reproduce one manifestation of this bug, if others would like to see it themselves- there are other aspects not illustrated by this (like lfos being thrown off sync by other tracks LFOs), but it gives you a taste for what’s happening. I hope this is fixed soon!
- Init pattern
- Set BPM to 75 (for example, just something other than 120).
- Fill track 1 seq with trigs.
- On LFO page, set LFO 1 to modulate pitch or some other noticable parameter.
- Set LFO1 time division to a slower BPM division (e.g. 4bpm or 8bpm), so you can hear the rhythmic syncing.
- Now, for LFO 2 on the same track, change the division to one of the non-BPM-synced settings. Suddenly, LFO 1 will stop following the BPM you set, and will switch to 120 bpm settings! Change LFO 2’s division back, and LFO 1 will revert to it’s intended behavior. LFO2’s settings shouldn’t affect LFO1!
Hope this is fixed in the next firmware update, cause this is pretty wonky.
Also, just wanted to second that I’ve noticed trigless locks don’t seem to impact sounds which use the arpeggiator - however, sometimes if you fiddle with the note length and turn the arp on and off, you can suddenly get it to follow the trigless locks - it’s really glitchy, and definitely not as it should be. This is a big letdown, since locking params of notes triggered by arps sounds pretty amazing to me