[live.numbox] doesn’t initialize properly

[madlab]

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 the initialization is ok.

----------begin_max5_patcher----------
403.3ocwR00aBBCE8Y3WAoOyLEb1g6uwdbYwTzpqNnkzdgow3+80O.EhxLKa
w8Bk68dtectmCgAnb4NlFE8bzqQAAGBCBbtrNBZsCPkzcKKnZGLTAugMQTWZ
QE6i2PUBZIyEVI+T24uRwzLAPAtTXClz5muxAUlu8AB9DXpxTCfoVvDz7BV+
Dj0PACf8UL+jhPwQn0ERJfhdqEiYj3BCJc+D6OAKTrkfO+zrzI33nDRh8YJw
YLaBtew78zUszSiHr7ctXSuJ4ykLej5noMrUKn.n340.67e5VFtkhsbXQMSt
tycm+97Ro4N3VtzLSitVbtmluZTtfCbZgeryNOiC.0QweSAt77L.k9coBtlZ
X.pBoXyMAUaZnF166E1G+XX34G22igw+MJWvtVu.TE7Czuoj+E8KwI0l+3uU
9N+oIIDBYF4dqgmlhw3aqSw2Ic5E29wUq2.JW7gEpdr9NPTmLtn1s1HZUUCS
oa0eNB0no2JUVSRryjK7lttgTrFdGd2gGQUlqNXN40J+FrKifBs84X3WATGh
HC
-----------end_max5_patcher-----------

[S4racen]

Depends what you want the box to do but if it's set to automated and stored or stored then you saving the device with a changed number will overwrite the initial value everytime.... Does perhaps closebang connected to a message change this i dont know?

Cheers
D

[madlab]

Darren, it seems this is really a problem with initialization. When I drag the device from the browser, numboxes should be filled with the 'initial enable' values, THEN, if I save the set, the values should reflect the changes, because I chose 'automated and stored'. In fact, when I drag the device from the browser, the numboxes are filled with values stored in the state they were when I saved the device after editing, not the 'initial enable' values. To me, this looks like a bug.
cheers
Stephane

[S4racen]

Hmmmm.... that i'd agree as a bug, it's not what i've experienced as the preset is saved with the template the original device should be unchanged, at least thats my experience and opinion....

I'd log it as a bug with support and they can give it a case number....

Cheers
D

[madlab]

Sent a bug report, but no answer from Abes about this...

[stringtapper]

Sent a bug report, but no answer from Abes about this...

Probably best sent to Cycling 74's support. They're the ones who actually do the coding on the live.* objects (or any Max objects).

http://cycling74.com/max6-bug-form/

[madlab]

Strange, I did a test again just with two numboxes and these initialized properly. Do they behave in an erratic way or do I ?...

[madlab]

Here is an answer from the Abes : "Although I am sure the Cycling guys are far more the experts here, as far as I know the "Initial Enable" value will only work if you ensure the value in the live.numbox matches the Initial value when you save the device."

However, considering my previous post, not sure this is really reliable...

[S4racen]

But i thought the "initial enable" feature was that it would output it's value at start up?

Otherwise how would it initialise the correct settings, saving a different value within a set should overwrite that initial value...

I'm having similar problems with Live.tab now...

Cheers
D

[madlab]

I expected exactly the behaviour you describe for initial value... That's quite strange. It seems it behaves that way : if you save values corresponding to the initial value when you save the device AFTER EDITING, they will be recalled when you load it from the browser. But if you save it within a set, the stored values will be those you set before saving the set. I guess that in that case, if you want it back to the initial state, you have to load it again from the browser...
Same with live.tab ?

[birthday boy]

There are quirks for sure, especially after crashes, but yeah for the most part mine usually init properly. I do have a case that's been bugging me with a numbox that is initially hidden, and made to bang it's value on hidden 0 - for some reason it always comes up as 1 instead of 100.