coffeencigs

the range of live.numbox is always limited to 127.. i know how to change it in the inspector.. but the problem is..

the max range of the numbox must be the total time of a sample..

i use info~ to get the total time served in a floatbox...

the range of live.numbox is always limited to 127.. i know how to change it in the inspector.. but the problem is..
the max range of the numbox must be the total time of a sample..

i use info~ to get the total time served in a floatbox...


set-range-of-live-numbox-with-an-argument-or-an-msg

If you click on the @ sign at the bottom of the inspector it will show you the messages you need to set each attribute, in this case "_parameter_range" is what you need.

You are not allowed to change the range of a 

 via a message. Doing so is likely to break your device presets/automation.

You are not allowed to change the range of a live.numbox via a message. Doing so is likely to break your device presets/automation.


and don't forget you have to use float mode if you want more than 127 values, even if they are integers actualy.

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?

What's wrong with using a scale object after the live.numbox? That'll let you dynamically scale *and* automate.

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.

If you click on the @ sign at the bottom of the inspector it will show you the messages you need to set each attribute, in this case “_parameter_range” is what you need.

And for the others messages like type, unit style etc?????

Yes! Works perfectly!
And for the others messages like type, unit style etc?????
Thank you in advance! :)

For me, this parameter is set to hidden and I can't access it through the attribute.

 If you click on the @ sign at the bottom of the inspector it will show you the messages you need to set each attribute, in this case “_parameter_range” is what you need. 

For me, this parameter is set to hidden and I can't access it through the attribute.


As of a few days ago (6.1.3), you can select the hidden parameter, ctrl+c to copy, then paste in a text editor and the hidden parameter name will appear.

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.

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.
This works...


The value coming out of the right .numbox needs to be stabilized (always match the number displayed) somehow, but I gotta go to lunch.

[EDIT]: who cares what's actually coming out of the right [live.numbox] at this point? The number [minimum] is feeding it is always accurate, so send that one. Duh.

[EDIT]: who cares what's actually coming out of the right [live.numbox] at this point? The number [minimum] is feeding it is always accurate, so send that one. Duh.
`



set range of live.numbox with an argument or an msg?