This is still an active issue as of version 1.4.1 and prevents built in fill patterns from functioning as intended and doesn’t allow for more off grid groove with chance.
MicroMove issue does NOT occur when apply Move (to at least one step event in track) - then MicroMove works with Chance logic. Reviewed other projects/patterns using the MicroMove feature and a Move occurred in each (before applying the off-grid feel).
I’ll second that confirmation. I actually forgot all about this bug, but it was one of the reasons I moved away from the Play+ as a main sequencer after using it to write my last album. So thanks for reminding me😂 The workaround I used was to just avoid the chance function entirely and map out the song note for note in song mode😵💫
You can do it, Polyend! Squash them bugs:sign_of_the_horns:
The play (n)/skip (n) and skip (n)/play (n) settings dont seem to work on time micro adjusted steps. The percentage chance works fine though. This is easily re-creatable.
I see that this is a known bug. Odd that it has been recorded for as long as it has and not addressed.
It’s kind of a big deal to sort. The generative/variability of play is literally the primary selling feature of the play series. If you can break a primary function with a vital sequencing tool… That’s not great.
I have found a potential workaround for this. If the note containing the micromove and one of the play/skip, or skip/play, values, the note cannot be placed in the same track as any note from the same synth. For example,
If the user has the first 3 tracks filled with notes from synth 1, and they want to add a play/skip value to a note containing a micromovement, that note will have to be place in one of tracks 4-8.
It seems that if the new track for the single synth 1 note contains notes from either synth 2 or 3, it does not negatively impact the reliability of the chance parameter. Just notes of the same synth.
I am running on firmware v1.3.0 and build 2097 for the Play+