Guillaume Evrard

i can't managed to have my pattr object NOT outputting a value at patcher load.

i've unchecked the option "restore saved value at patcher load" in the inspector, but nothing changed. i still have an output value at patcher load.

i can't managed to have my pattr object NOT outputting a value at patcher load.
i've unchecked the option "restore saved value at patcher load" in the inspector, but nothing changed. i still have an output value at patcher load.

pattr-outputting-saved-value-at-patcher-load-even-when-not-asked

Strange. Based on the documentation, specifically regarding autorestore, this behavior suggests it is a bug.

You will need to either freeze the autorestore attribute in the pattr inspector or specify it in the object box, [pattr test @autorestore 0].

Ok. Thanks Ben. Well I just learned something--- completely missed the bit about " If the attribute name is printed in italics, its value is 

Ok. Thanks Ben.  Well I just learned something---  completely missed  the bit about " If the attribute name is printed in italics, its value is not saved in the patcher.


I have a similar flavor of this issue, which is NOT related to the aforementioned issue with setting @autorestore in the inspector.

Are the below actual results really what is expected? Is this a bug? Why would the last saved value be transmitted to the target when @autorestore = 0 in the pattr object's attributes?

@autorestore 0 is properly set in the pattr object's attributes. 

When I reload my set, the initial value of 48 is sent to the target. 

When I reload my set, the last saved value is sent to the target, as if @autorestore was set to 1, when in fact @autorestore is actually set to 0.

@autorestore 0 is properly set in the pattr object's attributes. 
Parameter Mode Enable = true.
Initial Enable = true.
Initial Value = 48.
I am NOT using @bindto.
I am NOT using Pattrstorage.
This is a Max For Live device.

Expected results:

When I reload my set, the initial value of 48 is sent to the target. 

Actual results:

I could be wrong (I'm no expert), but I don't think @autorestore is meant to work with the parameter system. Pretty sure if a pattr object is parameter enabled it will always restore it's saved or initial value when using snapshots in MAX, or in M4L even with @autorestore 0. If I remember correctly, @thru 0 will stop the parameter enabled pattr outputting it's value when loaded in M4L, but you'll then need to bang the pattr to get it to send data.. or block the value by some other means.

Pretty sure the initial value is only used when there is no other saved value to use (like when loading a device for the first time). If a value has been saved with a live set, or within a live preset, that will override the initial value.

I could be wrong (I'm no expert), but I don't think @autorestore is meant to work with the parameter system. Pretty sure if a pattr object is parameter enabled it will always restore it's saved or initial value when using snapshots in MAX, or in M4L even with @autorestore 0. If I remember correctly, @thru 0 will stop the parameter enabled pattr outputting it's value when loaded in M4L, but you'll then need to bang the pattr to get it to send data.. or block the value by some other means.

Pretty sure the initial value is only used when there is no other saved value to use (like when loading a device for the first time). If a value has been saved with a live set, or within a live preset, that will override the initial value.

HTH

Thanks for the reply. After I learned about using pattr for initial values and restoring saved values, I had a thought to try to use it for initial values only (which would be simpler than my current initialization code) where I do not want saved values restored, but I guess that is not an option.

pattr outputting saved value at patcher load even when not asked