Closed for Company Meetings: Between September 18 (5pm PDT) and September 22 (12pm PDT), Support and Sales requests will be delayed. Only time-sensitive issues will be addressed during that time. Thanks for your patience.
I realise this thread is 3 years old, but I'd like to highlight my interest in this limitation being abolished.
"Doing so is likely to break your device presets/automation" - that's not really applicable in a lot of cases. In fact, if you've got a dynamically changing range, why would you want to automate the number in the first place?
Very true. But then the number box you're altering isn't representing the outgoing data any more. You'd have to create an additional object after the [scale] object to represent the data. But why use live.numbox then?
To get the visual aesthetic of a live.numbox while still allowing for a range-modifiable number object, I laid a live.numbox with transparent font under a standard Max number box with transparent border and background. This replicates the standard mode of live.numbox fine.
Don't get me wrong, it's all purely cosmetic consistency between the UI. I realise similar functionality can be replicated using the standard object sets. I was just hoping I had missed an option within the inspector of the live.objects to allow this kind of thing.
So this is part of a patch for playing in equal temperaments other than standard 12TET.
The left live.numbox, sets the number of notes per octave.
The right live.numbox sets the bend range.
For 12-36TET I want to support a maximum bend range of TWO octaves. For 37-72TET I want the maximum bend range to be only ONE octave.