Forums > Max For Live

[live.numbox] initial enable bug ?

June 13, 2013 | 4:02 am

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.


— Pasted Max Patch, click to expand. —


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",

June 13, 2013 | 7:17 am

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

June 13, 2013 | 9:04 am

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

June 13, 2013 | 9:30 am

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.

June 13, 2013 | 9:33 am

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

Viewing 5 posts - 1 through 5 (of 5 total)

Forums > Max For Live