zion

 to control playback time location of [groove~]. 

the range of the float should be changeable

 according to the length of a specific audio file. Max [float] object is wonderful but to use in Live I believe that I need [live.numbox] that its defaults range is 0. - 127, cant it be unlimited like [float] object? Or at least I wish 

 - according to a specific audio file's length - 

But I see no attribute for that in [live.numbox], or

a massage to change its range ! only at the inspector window.. 

Hi
I need a float number box to control playback time location of [groove~]. 
the range of the float should be changeable according to the length of a specific audio file. Max [float] object is wonderful but to use in Live I believe that I need [live.numbox] that its defaults range is 0. - 127, cant it be unlimited like  [float] object? Or at least I wish to change range dynamically - according to  a specific audio file's length - But I see no attribute for that in  [live.numbox],  or a massage to change its range ! only at the inspector window.. 
I need a real-time dynamic change.
Any ideas
Thank You!

Hi
I need a float number box to control playback time location of [groove~]. 
the range of the float should be changeable according to the l

setting-live-numbox-range-where-is-that-attribute

Waite!! I know you can use it in live but There is no automation or storing for it, and it is crucial..

So is there a way to determine a [live.number] range dynamiclly ?

Waite!! I know you can use it in live but There is no automation or storing for it, and it is crucial..
So is there a way to determine a [live.number] range dynamiclly ?
Thanks

It is possible to store max float, just activate parameter mode.

It is also possible to automate it using pattr.

pattr needs to have parameter mode enabled, but then what about

linked float ? I guess it has to be disabled.

It would get range set anyway from buffer length, and needs not to be stored.

But as I don't use Live can't say really.

I guess there is a reason why not to allow both dynamic range

How do you deal with stored automation, when automated object

It is possible to store max float, just activate parameter mode.
It is also possible to automate it using pattr.
Read pattr help file on MaxForLive TAB
pattr needs to have parameter mode enabled, but then what about
linked float ? I guess it has to be disabled.
It would get range set anyway from buffer length, and needs not to be stored.

But as I don't use Live can't say really.

I guess there is a reason why not to allow both dynamic range
and automation of live gui objects.
Would that not cause problems ?

How do you deal with stored automation, when automated object
changes it's range ?


Your answer sends me to think and wonder what I realy know and nead :)

Ok, greare things to learn and try..
Your answer sends me to think and wonder what I realy know and nead :)


You can alter live.numbox (and most live.* things) by sending the _parameter_range message. E.g. _parameter_range 0. 500.

However, for the reasons above about screwing with persisted data it’s really not a great idea In practice.

(Basically the only thing that seems safe to use it for is to change the enum strings for enum data types to another set of strings of the same length).

You can alter live.numbox (and most live.* things) by sending the _parameter_range message.  E.g. _parameter_range 0. 500.

However, for the reasons above about screwing with persisted data it’s really not a great idea In practice. 

 works and changes in real-time the live.numbox range, however, after creating 

 for the old range and then re-range live.numbox , the range for the automation screen did not change nor re-scaled.. (even if I used 'delete automation' and create a new one) - only when I re-named the 

of live.numbox , a new automation scaling was there.

But why is it risky thing? isn't it just like a legitimate dynamic allocation?

Any way, for some other reasons not going to use it now, but happy to have this option - Thanks!

Nice!  _parameter_range 0. 500. works and changes in real-time the live.numbox range, however, after creating automation for the old range and then re-range  live.numbox , the range for the automation screen did not change nor re-scaled.. (even if I used 'delete automation' and create a new one) - only when I re-named the long script name of  live.numbox , a new automation scaling was there.
But why is it risky thing? isn't it just like a  legitimate dynamic allocation?
Any way, for some other reasons not going to use it now, but happy to have this option - Thanks!

Setting [live.numbox] range. where is that attribute?