dan m

This is the second time I write this (dont know what happened to the first post), so apologies if you see this post somewhere else.

I am trying to find a way of saving settings within abstractions from the top patch. In my program, the user can create instances of these abstractions (script new #0object to thispatcher), edit them, and create more 'second level' abstractions within the first ones. I would like the user to be able to save the changes (e.g. number of abstraction instances, loaded files etc), while also retaining the original 'empty' abstraction for new sessions.

I have looked into the pattr objects but with no luck so far. Can anybody help? 

I have looked into the pattr objects but with no luck so far. Can anybody help? 
thank
d


saving-abstraction-settings

u could make a script from, whatever the user decides to do, then run thru the same list repeting all the actions from last session, u could tag actions somehow to ensure, that meningless stuff won't happen, i.e. an abstraction created, deleted & created again with the same script.

Download the Jade demo from www.electrotap.com to get the idea...

You can also check chanexample in MatSUI objects.

You can also check chanexample in MatSUI objects.
http://www.estatesound.com/matsui.html
It can give you some ideas.

I use exactly this methode (abstraction thing) in a big patcher.

The best way i found to do this is simply to use the coll object.

The nsub message offers great possibilities with coll.

This way, you really can call many instances of the same abstraction in a

This way i can create objects who contain abstractions in my patches... a

You should also have a look at the template possibility in version 4.5...

I use exactly this methode (abstraction thing) in a big patcher.
The best way i found to do this is simply to use the coll object.
The nsub message offers great possibilities with coll.
This way, you really can call many instances of the same abstraction in a
patcher and then save all this when you 
save the patcher at the end...
This way i can create objects who contain abstractions in my patches... a
little bit like a plug-in in fact.

You should also have a look at the template possibility in version 4.5...
It seems interesting

Use pattrstorage in the parent patch of the abstraction and save a 

preset with the state of the pattr-managed objects within. When you 

reload the patch, restore the saved preset. It should override any 

settings restored by objects in the abstraction itself.

Use pattrstorage in the parent patch of the abstraction and save a 
preset with the state of the pattr-managed objects within. When you 
reload the patch, restore the saved preset. It should override any 
settings restored by objects in the abstraction itself.

I have looked quickly into Matsui's chanexample and that's pretty much the sort of thing I am doing. If only I had known about this patches before! Chanexample combines coll, pattrstorage and javascript. Hopefully I can adapt some of it to my patch.

However, while chanexample remebers the number of bpatchers (audio channels in this case) that the user has created, the pattrstorage/autopattr dont seem to register the settings within the bpatchers (fader positions etc). I dont know if this was meant to work in chanexample or not. I'll look into pattr's a bit more...

saving abstraction settings