new live objects and scripting name
It seems the new live objects can’t ‘survive’ without the scripting name. I can delete it but every time I open again the patcher the default scripting name is there again.
Is there a reason for that? I would prefer to be able to delete it; it causes some minor issues in my configuration, e.g. they are always exposed to pattr system.
In the Live ui object’s inspector, set parameter visibility to ‘hidden’.
all the best,
Thank you Ben
Maybe I’m missing something, but every time I open again the patcher, the scripting name (a default name) is there and visible to pattr, in spite of the ‘hidden’ setting.
All the best
maybe I’m missing something too. ?
I’d also just like to exclude live objects from the autopattr system, same problem as matteo. edit: The seemingly unevitable scriptingname also appears in the clientwindow of the pattrstorage object, despite Hidden setting, of course..
why don’t you just exclude these objects from the pattr system with the second outlet of an autopattr ?
Because i usually do it the other way, which is not a good reason, but this method also seems to introduce more objects and patchcords to patchers which are hard to keep tidy anyways.. But thanks(!) that’s kind of a solution.
Still there should be a way..?
I’m using the "2th outlet technique", too, even if I prefer the other way…
But I’d like to know if there’s a specific reason live.objects must always have a scripting name…
I guess there is a reason with Live’s way of working…
But I just found this trick :
loadbang to message "varname" to your Live object
it opens your Live object with a blank scripting name
I confirm Live objects are not hidden to pattrstorage when using the ‘hidden’ parameter (Max 6.0.8).
hello max pros,
is this bug is still alive ?
i am tying to delete the scripting name of a live.toggle object.
if i set the ‘hidden’ parameter, the scripting name disappear, but if i reload the patch, the scripting name is still there.
perhaps someone from cycling has a hint ?
excluding from the pattrstorage is not an option.
all the best,
I think the ‘hidden’ attribute must be seen in the context of M4L as it ensures that the parameter value is not saved with the Live set. But you may not always want to exclude it automatically from pattrstorage which provides a different layer of preset management.
Forums > MaxMSP