Thomas Goepfer

With autopattr and pattrstorage object, it is possible to send values to named objects. UI pattr objects accept an init message to reset their value. But you can't send an init message to these objects with autopattr/pattrstorage.

A quick question/request :
With autopattr and pattrstorage object, it is possible to send values to named objects. UI pattr objects accept an init message to reset their value. But you can't send an init message to these objects with autopattr/pattrstorage. 

init-message-thru-autopattr-pattrstorage

you need to understand that the purpose of (auto)pattr object is remembering and recalling contents/values of client UI objects.

That's why it does not work, because the "init" message cannot be dial object's value/content. The dial objects only accepts it as a control message, but it is not a suitable value/content of it. That's important difference. The "init" message could be suitable value/content for some textbox for example and there autopattr would let it thru (and mainly, remember it as the textbox's content/value)

So, the (auto)pattr is not the correct tool for sending just any (ie control) messages to objects. An even if it would be suitable values/contents it is not the right tool for just sending it from one part in the patch to another. Take a look at [send] [receive] objects instead - they may be what you need there (maybe / you have no context in the example and i am not sure what are you trying to make)

(or if you insist on using the autopattr, then you could still set the init values on loadbang and save them all to 0th preset and then instead of sending "init" message to the dial object, you could just tell the autopattr to recall 0th preset for that one dial client)...

Hi,
you need to understand that the purpose of (auto)pattr object is remembering and recalling contents/values of client UI objects.
That's why it does not work, because the "init" message cannot be dial object's value/content. The dial objects only accepts it as a control message, but it is not a suitable value/content of it. That's important difference. The "init" message could be suitable value/content for some textbox for example and there autopattr would let it thru (and mainly, remember it as the textbox's content/value)

(or if you insist on using the autopattr, then you could still set the init values on loadbang and save them all to 0th preset and then instead of sending "init" message to the dial object, you could just tell the autopattr to recall 0th preset for that one dial client)...


You can send an arbitrary message to a pattr object (or any other object with a scripting name) using pattrforward.

init message thru autopattr / pattrstorage