Subsequent 37 bug

[Quatschmacher]

I think I may have found a bug in the Subsequent 37. I’m on the latest firmware version.

Set Mod Bus 1 as follows:
mod source to “constant on”;
mod depth to 5;
mod destination to mod bus 2’s LFO “hi range” button;
Mod wheel to 100% in the controllers menu.

When raising the mod wheel one would expect the “high range” button to illuminate once the mod wheel reaches the halfway point. (This is the normal behaviour when assigning the mod destination to any other on/off switch, keeping all other settings the same.) However, in the current instance, the switch illuminates when the mod wheel is significantly below the halfway mark. (In fact, the only way I could get the button to illuminate when the mod wheel was raised to its mid-point was by setting “mod depth” to 4.

The same behaviour occurs when routing to mod 1’s “hi range” button. It also occurs when routing mod bus 2 to either mod bus’s “hi range” button.

The above can be replicated on any patch (including a fresh init patch).

Can anybody replicate this on their Subsequent or Sub?

[bichuelo]

Indeed, I followed your precise instructions and that is the behavior

However, I couldn't tell if this is by design, or a bug

[Quatschmacher]

Good to know. I’m waiting to hear back from the email I sent at the same time as my initial post.