BentoSan

I have an object that does not support pattr as it has a bug (sa.function - 

https://cycling74.com/tools/sa-function/)

However this object IS compatible with preset object.

I setup my patch so every time the object changes its state it then saves its contense into the preset object. Now what i need to do is save the preset object when the live set saves, that way when the live set reopens i can just loadmess the preset object to recall the data back when live last closed.

My issue is i am not sure how to save the preset object into the live set. I have tried attaching it to a pattr object like how i usually would saving anything else into a live set but attaching the middle outgoing connection of the pattr object to the preset object however this doesnt work.

Is there any way to save the contense of the preset object when live saves so i can recall it when the live set is loaded again ?

I have an object that does not support pattr as it has a bug (sa.function - https://cycling74.com/tools/sa-function/)

Is there any way to save the contense of the preset object when live saves so i can recall it when the live set is loaded again ?


using-preset-object-instead-of-pattr-workaround

How do i save a preset objects state inside of an Ableton live set when Ableton saves ?

This needs to be saved into the patch but not affect other versions of the patch in the live set.

Any help would be greatly appreciated :)


As you have discovered, a pattr object will not connect to the Preset object, however Preset has a @pattrstorage attribute which can be set to link its contents to a named pattrstorage.

As you have discovered, a pattr object will not connect to the Preset object, however Preset has a  @pattrstorage attribute which can be set to link its contents to a named pattrstorage.


Yup i worked that one out this not too long after making my last post (its hidden a couple patcher levels deep into the example documentation).

However i am still stuck because when you use that function it breaks the ability to use the left output of the patcher object to bind objects to the patcher (it also breaks not having anything connected to the left output), instead you need to use the pattr object instead and use the bind to output on all of the objects that you wish to save into the patcher object. The thing is avoiding the use of the pattr object on the object that i want to save the data from is the exact thing i was trying to avoid.

I have moved away completely from trying to store the data in a preset object, instead im looking at how to save the dump output (which is a list) inside of the patch so i can recall that when the patch reopens in live - havent quite figured this out yet without having to save the list into a separate file which again i am trying to avoid.

If sa.function will dump its 'state' as a list, you can store this list of data in a pattr (that is NOT bound to anything).

That pattr can then be managed via pattrstorage, or, in the context of m4l, parameter_enabled.

When your patch loads, the 'list of state' will be output from the pattr - you should be able to use this list to generate the required messages to setup your sa.function object as required

I'd give an example patch, but I don't use sa.function...

Could you show an example that uses the function object ? It behaves in pretty much exactly the same way as the sa.function object.

When it dumps its state it dumps its state into a series of lists in different messages.

Im guessing what i need to do is dump all of those lists together into a single list, then when the pattr spits the message back out i need to pull that list back into several different lists again and pump it back into the function object. Would i be correct in saying that ?

Ive used the pattr object lots before, but never have had to use the inlet to store data so this is still all rather new to me. Very nice learning experience though, i have already learnt a lot pulling my hair out over this so far :p

I should note that the only difference in the dump outlet is that sometimes the list will comprise of 5 items and not the 2 that function always seems to have religiously. 2 floats, a symbol then followed by another 2 floats.

Probably not the cleanest approach, but i ended up dumping the dump into a textedit object then [pattr] saving the textedit box. I then used a live.thisdevice to bang on load, so the text edit box would output into several different lines that were then input into the sa.function object.

Id give an example of this, but im not sure how to use the paste from clipboard feature without filling the forums with 100's of lines of code - guess thats the next thing i should work out.

I really appreciate everyones help and im damn sure happy i finally worked out how to do this >_<

Sounds like you're using the features of textedit sensibly - saves you collecting the 'dumped output' into a single list that then needs further processing to parse/format when sending back to sa.function

As you mentioned 'learning experience' before, bare in mind the following from the pattr reference:

"It functions in two modes. By default, the pattr object maintains its own data."

What this means is that a pattr object doesn't NEED to be bound to a ui object - using one as a 'standalone' data storage point within your patch/pattr system is a powerful and useful technique. That you CAN bind pattrs directly to UI objects is an elegant convenience. In this case though, I reckon you've made a good call on using a bound UI object, even though it isn't strictly required (i.e. assuming you won't be interacting with the textedit when using the patch).

Finally, you can use 'copy compressed' from the edit menu to get your patch/clipboard into a text block suitable for posting to the forum

Thanks for the extra tips willyc, ill try that out somewhere and see how i can slip it into my workflow where needed :)

Edit: i just realised that code does not actually dump all of the available lines in the object, only the one currently being displayed. Needs some extra code to get that working :p Ive taken down the code till i get it working properly + its a tad bit buggy under certain unforeseen circumstances. Ill post a version when its more polished

Alright got this working and fingers crossed... bug free :)

This version will store up to 8 lines, you could change it to more or less fairly easily but i wont go into that as its pretty self explanitory

Using preset object instead of pattr workaround ?