Ess M

I'm noticing some odd behaviors in Gen~ on Max 8.2.0 (running on Apple Silicon)

I often offset the starting phase of a cycle or wave object (when indexing with phase) with an add object, but this does not work correctly in 8.2.0 - or at least it does not behave as it did before. Seen below is 8.2.0, 8.1.11 and the Gen~ patch.

image.png

scope~

gen~

phasor

cycle

My suspicion is that the Cycle object used to behave like Wave where it had a bound mode that would take care of the out of bounds phase signal and wrap it, but seems it's no longer doing that.

It's also causing issues with basic phase modulation connections like feedback - but putting a [wrap 0 1] object before the cycle will fix it.

I'm noticing some odd behaviors in Gen~ on Max 8.2.0 (running on Apple Silicon)
I often offset the starting phase of a cycle or wave object (when indexing with phase) with an add object, but this does not work correctly in 8.2.0 - or at least it does not behave as it did before. Seen below is 8.2.0, 8.1.11 and the Gen~ patch.


My suspicion is that the Cycle object used to behave like Wave where it had a bound mode that would take care of the out of bounds phase signal and wrap it, but seems it's no longer doing that.

It's also causing issues with basic phase modulation connections like feedback - but putting a [wrap 0 1] object before the cycle will fix it. 

I'm noticing some odd behaviors in Gen~ on Max 8.2.0 (running on Apple Silicon)
I often offset the starting phase of a cycle or wave object 

cycle-phase-index-behaving-strangely

I am able to reproduce on M1 (no regression under x86 or rosetta) and will have a fix in a forthcoming beta.

Should be fixed in this week's beta. Please give it a test. Thanks!

Cycle phase index behaving strangely