Mysterious little indicator
When building M4L devices I sometimes get a little indicator (white or red) in the upper left corner of GUI elements. What does it mean exactly and how can it be cleared?
the indicators usually mean that you have an automated parameter.
That’s strange as I’m currently not using any automated parameters. However, the affected GUI elements are controlled in some way by send/receive messages. And the indicators magically appear somewhere in the process of editing and testing my devices.
Can you give me a list of steps I can follow to reproduce?
Unfortunately, so far I haven’t found a pattern to reproduce this behavior.
But I’ll investigate further and report any relevant findings.
Thanks for your interest.
now I’m able to reproduce the behavior with an example (attached).
The device simply allows to start and stop Live’s transport.
Load it on a MIDI track and see how it works using its play button.
Now, press the *record* button in Live’s transport and start/stop again.
After this I’m getting the automation indicator on the play button!
----------begin_max5_patcher---------- 865.3oc6XssahCCD84vWQjelsJ1DHj8sc+MpPHCwTb2D6nXCKcq5+95KIgzh CDZyFgzhTKl3KykyLywY30QdfU7CDAv+69O56485HOOyT5I7Je1CjgOrNEKL aCjR2SdX0Nojy.isquGWvvYjOt7ivEU6fsKixRIRiHfkSlikq2RYOsrfrVZM gIASdHXr+DzT8.r9S+EkmglXzBe0yeCBA0BpPodIoXIggWkRZpDkl46jeT01 ojujSr5E.p0f.umjrDKkETkaPN9MQInThJZ2NcGguoZ5p4aZOoT1uzPi4rAi OcCY7D0ej1Vlx1vMNLvwh7hDRQambGiZcYmGUjSHIozr1NsPRxa0lIJLsD13 a1.FqFX032624gbNivLAW3CsZlxWJiYNQHU1W6mOSkWYrSmqVEfQNgVpjhSa jx3DH1xKjtRtANE4dpfdFooi1kdCJxoEiYLtDKob1xZs5RUob1Smul6DEWCT 1keazniClOeaz3dmC3ZI.fwkD.wcf.H3NAvcBf6D.Wzr54peF42pxupZOI4f I7BxnITUYU07a3Lof9mx3Zku182DvP.DFL2LDY3Al6lGXNvYodPCCoFo9QgJ j6+SdZBne8bJqWc7IHqiGbNGOFbcbbTcg3h9GVTzaB7SjSvk03zTegjmuLOE +hxMuFHBc42RLZldHFYvnYtwnHvm8dfdDfVyyxzrfUtTAQndzVk2vsrNh04h NMx+ESrfgZIhrUTygmH9lVUSQ0.LmNXUZWHkBWH64bJXbnMmJ5x4TytExoZg KxbUfZAsi0OHCZpoLKLzfISiOGiT3sNxn7us95usTP5qqpBgyroNlB2X34.n ItAnIsBPiK+e.AJAIU4a9P+fdBfP1qwPyMC1zo1.HzUBPqvZJfii+S.JSpiA eZqamlK1F8toYloQGuWGEz.CtVvLbVKBpC73vSh4ZxzquaJTCwXU16Dj6r46 MZ8YZzRAAPM7oFQ+G0qUi5pamNsZyn5XeVlnmRRrO9CuZp10y+dpHAeWw5pR nx262+X8dBQHor5x8GqaJpwd1RSRHrluqlpmkbtpgfRSvegSZwtZQQcvhBGT KB1AKBMnVj5pe0cpWFifClEM6lKpg5fEo+Y+FxDofNXSyFbT5RYRP3vhRcod K5KXRpGdazeAUQ5h2B -----------end_max5_patcher-----------
Thanks for the example. As far as i can tell it happens because you use a "live" Max object which
- writes into Live´s Undo history and-
- acts like all other Live parameters when using the global record button, although in this case you won´t see a breakpoint envelope.
I’m a bit confused. Are you saying the behavior is normal/intended?
Yes, absolutely – it´s a feature.
Thanks, I didn’t realize the effect of the global record button.
Is this explained somewhere in detail?
Automation is covered in Live´s manual chapter 18.
Ok, mystery solved.
Christian is right that’s a feature, and the expected behavior from any parameter in Live. However in this specific example, I don’t think you want the live.text’s play object to be seen as an automatable parameter, if you set the parameter visibility to hidden in the object’s inspector it won’t be stored in the preset or the automation.
Thanks Emmanuel, that option is exactly what I need. I just didn’t expect that Live automates "everything" by default but basically appreciate the concept.
Forums > Max For Live