Has the [scale] object changed behavior since the Max 8.1.2 update?


    Feb 10 2020 | 9:54 am
    Hi folks, I am experiencing something weird and before filing a bug report I would like to know if anybody else is experiencing the same. This is something that started happening since the latest update to Max 8.1.2: the [scale] object defaults to classic mode when instantiated in a patch without specifying the @classic attribute. On top of it classic mode no longer seems to be working. It does not respect the input/output range when the exponential argument is used. Yes, I do set the exponential argument to 1.06 just like in the IRCAM patchers. So in order to make the object usable again I have to explicitly instantiate it with @classic 0. I am on MacOS Catalina 10.15.3 using Max 8.1.2. Is my brain playing tricks on me? Is anybody else experiencing this?