[live.numbox] initial enable bug ?

Jun 13, 2013 at 4:02am

[live.numbox] initial enable bug ?

It seems that, in Live 9 at least, [live.numbox] doesn’t initialize properly its ‘initial enable’ value. Instead, it initializes with the value last set when you save the device. Copied those boxes in max standalone and he initialization is ok.

<code>

– Pasted Max Patch, click to expand. –

</code>

My info system + I work with Live 9.04
“Version 6.1.2 (6a3e522)”,
“platform” : “mac”,
“arch” : “x86″,
“osversion” : “Mac OS X Version 10.8.3 x86_64″,

#252576
Jun 13, 2013 at 7:17am

Setting ‘Parameter Visibility’ to ‘Hidden’ should give the behavior you want.

#252592
Jun 13, 2013 at 9:04am

But if I do that, will the value be saved in the set if I modify it ?

#252614
Jun 13, 2013 at 9:30am

Found the reference for this parameter in max help and it seems to be the case. What I would like is tthat the device is initialized according to the ‘initial enable’ parameter but saved with the set. So it seems that I have to be sure the numboxes are set to values corresponding to their initial setting in the inspector and set to ‘automated and stored’ before I save the device after editing… So I don’t really see the point of ‘initial enable’.Another way would be to send loadmess to each numbox I want to initialize but that adds objects to the patch.

#252633
Jun 13, 2013 at 9:33am

The ‘initial enable’ value can be useful as starting point when a device is loaded the first time in a set.

#252634

You must be logged in to reply to this topic.