Chance Play Skip Logic Breaks after Applying Micro Move

[donald.finch]

Bug Description

Play+/Play Chance (Play Counter Skip Counter Logic) no longer executes after applying MicroMove +/-. Must be 0/24 for Chance operation to perform. I have tried applying the values in several with same effect. For example- Repeat also hampers Skip but in correct order, it works. For Chance, I did not find a way, so I am writing. U guys got a workaround?

This very much impacts use of Play+ with LIVE instruments and any Funky Feel projects. Only remedy is to build out many more patterns (and time dealing with each) versus applying this nice existing feature Chance. Please take a look- it is CORE functionality- thank you.

Steps to Reproduce

1 Build a pattern with a synth (etc)
2 Apply Chance to Track (eg, play 3 Skip 1)
3 Run to verify counters function
4 Select Track and apply MicroMove +/- (eg 8/24 or -8/24)
5 Run and notice track plays continuous (no skip)

Occurrence / Frequency

Always

Found in Firmware

• Version: 1.1.0
• Build: 1708

Attachments

–

[Sandroid]

Hey @donald.finch, it’s been a while

This bug seems to affect all Play devices. Previous report here:

Micromove prevents Play X | Skip X

Bug Description When using Micro Move on a step with Play 1| Skip 1 it will ignore the Play 1 | Skip 1. Reproduction Steps Place a sample on any step (I did 4 on the floor kick) Apply Play 1 / Skip 1 chance for Play Sample Adjust micro move on sample by any value other than 0 and the sample will Play repeatedly Note that if Skip 1 / Play 1 is selected it will exclusively skip the sample Also note, if a longer variation like Play 4 | Skip 4 is used and you change Micromove while it is skippin…

I’ll update the previous report, add the play-plus as a device as well and will close this as a duplicate. The bug is already logged by Polyend.

I have moved your last comment, to the old report. I hope that’s ok.

[donald.finch]

Sure. It seems a very narrow scoped bug (apply Move instance to MicroMove so Chance Counter works) - seems a pretty ‘simple’ fix versus others…any chance to fast-track this 2.5 yrs old bug to benefit ALL Play users? thank you.