Isjtar

I have made a set of patches I use all the time for audio generating/processing.

I have also included a nice preset interpolation system with pattr and pattrstorage.

Thing is, since i generally want to use several instances of these patches, i get conflicts with names and thus preset recall.

I could script everything, reformat xmls and the like, but this is a very big detour.

it would be nice if you could have #0 or #1 arguments in object names, but i guess this is just not compatible with the general idea of object names.

I have made a set of patches I use all the time for audio generating/processing.
I have also included a nice preset interpolation system with pattr and pattrstorage.
Thing is, since i generally want to use several instances of these patches, i get conflicts with names and thus preset recall.
Is there any way around this? 
I could script everything, reformat xmls and the like, but this is a very big detour.
it would be nice if you could have #0 or #1 arguments in object names, but i guess this is just not compatible with the general idea of object names.

several-instances-of-patch-names-and-pattr-storage

Quote: isjtar wrote on Tue, 19 September 2006 06:25

----------------------------------------------------

> I have made a set of patches I use all the time for audio generating/processing.

> I have also included a nice preset interpolation system with pattr and pattrstorage.

> Thing is, since i generally want to use several instances of these patches, i get conflicts with names and thus preset recall.

just discovered names are patcher scpecific, had a different bug.

will be banging my head against keyboard for penitention.

Quote: isjtar wrote on Tue, 19 September 2006 06:25
----------------------------------------------------
> Hi,
>
> I have made a set of patches I use all the time for audio generating/processing.
> I have also included a nice preset interpolation system with pattr and pattrstorage.
> Thing is, since i generally want to use several instances of these patches, i get conflicts with names and thus preset recall.
----------------------------------------------------
just discovered names are patcher scpecific, had a different bug.
will be banging my head against keyboard for penitention.


> it would be nice if you could have #0 or #1 arguments in object

> names, but i guess this is just not compatible with the general idea

Why not? the idea of an argument is an argument, you don't need a 

different object name for that. If you have a [pattrstorage #1_name] it 

If you instantiate the first subpatcher with [MySubpatcher first] and 

the second with [MySubpatcher secondo], they would save to different xml 

files (first_name.xml and secondo_name.xml). Or you just use one single 

pattrstorage in the main patch and everything will be saved in one place...

junior wrote:
> it would be nice if you could have #0 or #1 arguments in object
> names, but i guess this is just not compatible with the general idea
> of object names.

Why not? the idea of an argument is an argument, you don't need a 
different object name for that. If you have a [pattrstorage #1_name] it 
would save par default to #1_name.xml...
If you instantiate the first subpatcher with [MySubpatcher first] and 
the second with [MySubpatcher secondo], they would save to different xml 
files (first_name.xml and secondo_name.xml). Or you just use one single 
pattrstorage in the main patch and everything will be saved in one place...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


several instances of patch, names and pattr storage