SEM V2 VST3 programmer issue in latest stable build?

[DJMaytag]

32090A04-BA33-41CC-94F5-FE06F27D0D0D.jpeg (217.31 KiB) Viewed 333 times

When using the programmer at a range outside the max values, the actual value doesn’t line up with what the Combinator knob says it should be.

I submitted it as a bug to Reason, but they said they can’t reproduce this. I get the same result on the stable build on two different machines.

Can anyone put their SEM V2 in a Combinator, map knob 1 to the filter cutoff at values beyond the min and max, and reproduce this? The value in the picture shows it as 62 Hz, but the minimum value in the programmer should be 81 Hz. I get the same issue with the top end, and adjusting the top of the range affects the lower value I’ve dialed in.

[DJMaytag]

Bug confirmed. This one slipped past the team, and is in the current stable build.

[Loque]

Bug confirmed. This one slipped past the team, and is in the current stable build.

Thanks

[DJMaytag]

FWIW, this is a bug in the current stable build, so this shouldn't be a "no beta discussion" issue (though it still exists in the latest beta version).