Stochastic track + scale not working + transpose changes root note (scale mask does not apply)

[vponikarovskyi]

Actual behavior:
Applying a Scale to a Stochastic track doesn't affect which notes are played.
If you enable all all 12 notes AND select a scale, the scale does not exclude notes not used in the scale.
Actual scale being played is controlled only by notes which have probability >0%.
So,
When applying TRANSPOSE to a Stochastic track (via CV or MIDI), everything's getting transposed.
Example:
If you select a scale C minor pentatonic and apply transpose +1 semitone, instead of C minor pentatonic you get C# minor pentanonic. You don't have the Root note, so transposition is not related to any root.

Expected behavior:
When applying a Scale to a Stochastic track, notes unrelated to this scale are excluded.

When you apply TRANSPOSE to a Stochastic track (via CV or MIDI), notes remain in the selected scale mask (e.g. C minor pentatonic - CD#FGA#).

In such a way TRANSPOSE for Note tracks works - you control how high or low the pattern sounds, but you still remain in the selected scale with a selected root note. I want to have same control in case of a stochastic track.

This works similarly on a Copier Maschine on Ornament&Crime. You musically control the tessiture of your part, but you remain inside a scale mask related to a root note.

[VinxScorza]

Thank you so much for your very precise report.
I checked the current behavior: on Stochastic/Arp tracks, scale masking and transpose semantics are not fully aligned with Note-track behavior. In practice, transpose acts like a chromatic root shift on the stochastic note pool instead of keeping notes constrained to the selected scale mask/root. This behavior is inherited from the Mebitek Stochastic implementation.

Your expectation is clear, and I was already working on it even before this report:
– make Arp/Stochastic follow a strict “stay in selected scale” behavior
– keep transpose as a register shift while remaining inside the selected scale + root context
– exclude notes outside the selected scale mask by default

I didn’t include the fix in this latest release because it is "behaviorally breaking" (musical output can change) for older Stochastic/Arp projects that may have implicitly relied on the legacy behavior, even though project files themselves remain compatible. That’s what stopped me from pushing it immediately...

If that tradeoff is acceptable, I’ll implement it in the next patch

[VinxScorza]

Actual behavior: Applying a Scale to a Stochastic track doesn't affect which notes are played. If you enable all all 12 notes AND select a scale, the scale does not exclude notes not used in the scale. Actual scale being played is controlled only by notes which have probability >0%. So, When applying TRANSPOSE to a Stochastic track (via CV or MIDI), everything's getting transposed. Example: If you select a scale C minor pentatonic and apply transpose +1 semitone, instead of C minor pentatonic you get C# minor pentanonic. You don't have the Root note, so transposition is not related to any root.

Expected behavior: When applying a Scale to a Stochastic track, notes unrelated to this scale are excluded.

When you apply TRANSPOSE to a Stochastic track (via CV or MIDI), notes remain in the selected scale mask (e.g. C minor pentatonic - CD#FGA#).

In such a way TRANSPOSE for Note tracks works - you control how high or low the pattern sounds, but you still remain in the selected scale with a selected root note. I want to have same control in case of a stochastic track.

This works similarly on a Copier Maschine on Ornament&Crime. You musically control the tessiture of your part, but you remain inside a scale mask related to a root note.

Regarding my previous message, do you have any feedback?

[vponikarovskyi]

Thank you so much for your very precise report. I checked the current behavior: on Stochastic/Arp tracks, scale masking and transpose semantics are not fully aligned with Note-track behavior. In practice, transpose acts like a chromatic root shift on the stochastic note pool instead of keeping notes constrained to the selected scale mask/root. This behavior is inherited from the Mebitek Stochastic implementation.

Your expectation is clear, and I was already working on it even before this report: – make Arp/Stochastic follow a strict “stay in selected scale” behavior – keep transpose as a register shift while remaining inside the selected scale + root context – exclude notes outside the selected scale mask by default

I didn’t include the fix in this latest release because it is "behaviorally breaking" (musical output can change) for older Stochastic/Arp projects that may have implicitly relied on the legacy behavior, even though project files themselves remain compatible. That’s what stopped me from pushing it immediately...

If that tradeoff is acceptable, I’ll implement it in the next patch

Thank you so much for doing this!
The tradeoff is more than acceptable for me, it would drastically increase the capabilities of the stochastic mode.