Manuel Poletti

As the doc says so, is there any reason that a pattrstorage object in 

a top-level patcher could not be able to reflect the priorities of 

pattr obejcts being loaded from abstractions or subpatchers ?

It would be so useful, when pattr-priority is essential for your DSP 

module to work great (in other words, the order in wich you recall 

parameters is essential for your module to work properly), if a large 

patch containing a lot of those modules could be quickly stored into 

a global pattrstorage (a session) without problems (due to the 

As the doc says so, is there any reason that a pattrstorage object in  
a top-level patcher could not be able to reflect the priorities of  
pattr obejcts being loaded from abstractions or subpatchers ?
It would be so useful, when pattr-priority is essential for your DSP  
module to work great (in other words, the order in wich you recall  
parameters is essential for your module to work properly), if a large  
patch containing a lot of those modules could be quickly stored into  
a global pattrstorage (a session) without problems (due to the  
priority of parameters, sorry, again :).

pattrstorage-pattr-priority

- A higher-level pattrstorage should inherit priorities from a lower- 

- The pattr object itself should have a @priority attribute to "hint" 

to pattrstorage that its priority should be set to a certain value 

Am 06.10.2006 um 10:09 schrieb Manuel Poletti:

> As the doc says so, is there any reason that a pattrstorage object 

> in a top-level patcher could not be able to reflect the priorities 

> of pattr obejcts being loaded from abstractions or subpatchers ?

> It would be so useful, when pattr-priority is essential for your 

> DSP module to work great (in other words, the order in wich you 

> recall parameters is essential for your module to work properly), 

> if a large patch containing a lot of those modules could be quickly 

> stored into a global pattrstorage (a session) without problems (due 

> to the priority of parameters, sorry, again :).

- A higher-level pattrstorage should inherit priorities from a lower- 
level pattrstorage if in greedy mode?

- The pattr object itself should have a @priority attribute to "hint"  
to pattrstorage that its priority should be set to a certain value  
when the patch is analyzed?

> Hi Jeremy,
>
> sorry if this was discussed ages ago :
>
> As the doc says so, is there any reason that a pattrstorage object  
> in a top-level patcher could not be able to reflect the priorities  
> of pattr obejcts being loaded from abstractions or subpatchers ?
> It would be so useful, when pattr-priority is essential for your  
> DSP module to work great (in other words, the order in wich you  
> recall parameters is essential for your module to work properly),  
> if a large patch containing a lot of those modules could be quickly  
> stored into a global pattrstorage (a session) without problems (due  
> to the priority of parameters, sorry, again :).
>
> You follow me ?
>
> Salut,
>
> _M
>


On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote:

> - A higher-level pattrstorage should inherit priorities from a 

> lower-level pattrstorage if in greedy mode?

> - The pattr object itself should have a @priority attribute to 

> "hint" to pattrstorage that its priority should be set to a certain 

> Do you mean:
>
> - A higher-level pattrstorage should inherit priorities from a  
> lower-level pattrstorage if in greedy mode?
>

> - The pattr object itself should have a @priority attribute to  
> "hint" to pattrstorage that its priority should be set to a certain  
> value when the patch is analyzed?

Am 06.10.2006 um 10:54 schrieb Manuel Poletti:

> On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote:

>> - A higher-level pattrstorage should inherit priorities from a 

>> lower-level pattrstorage if in greedy mode?

If I write it on my list, will it make you happy? I don't anticipate 

working on any major updates to pattrstorage for the next while, but 

>> - The pattr object itself should have a @priority attribute to 

>> "hint" to pattrstorage that its priority should be set to a 

>> certain value when the patch is analyzed?

This has come up many, many times. And I still don't know about it. 

>
> On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote:
>
>> Do you mean:
>>
>> - A higher-level pattrstorage should inherit priorities from a  
>> lower-level pattrstorage if in greedy mode?
>>
>
> YES !!!

If I write it on my list, will it make you happy? I don't anticipate  
working on any major updates to pattrstorage for the next while, but  
the time will come.

>> - The pattr object itself should have a @priority attribute to  
>> "hint" to pattrstorage that its priority should be set to a  
>> certain value when the patch is analyzed?
>
> This could be very useful as well.

This has come up many, many times. And I still don't know about it.  
But OK. .

> If I write it on my list, will it make you happy?

Euh... whenever you'd feel it's more fun to compute a little more, 

Yes, anyway !
Euh... whenever you'd feel it's more fun to compute a little more,  
I'd be VERY happy :)

It's not a question of computing v. not computing. It's a question of 

>what< one computes. You may find yourself very, very happy with the 

stuff being worked on these days. But you'll have to wait and see!

Am 06.10.2006 um 11:44 schrieb Manuel Poletti:

> Euh... whenever you'd feel it's more fun to compute a little more, 

It's not a question of computing v. not computing. It's a question of  
 >what< one computes. You may find yourself very, very happy with the  
stuff being worked on these days. But you'll have to wait and see!

> Euh... whenever you'd feel it's more fun to compute a little more,  
> I'd be VERY happy :)


if my vote counts (which it doesnt im sure :P) Id love these features 

On Oct 6, 2006, at 4:59 AM, Jeremy Bernstein wrote:

> Am 06.10.2006 um 10:54 schrieb Manuel Poletti:

>> On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote:

>>> - A higher-level pattrstorage should inherit priorities from a 

>>> lower-level pattrstorage if in greedy mode?

> If I write it on my list, will it make you happy? I don't 

> anticipate working on any major updates to pattrstorage for the 

>>> - The pattr object itself should have a @priority attribute to 

>>> "hint" to pattrstorage that its priority should be set to a 

>>> certain value when the patch is analyzed?

> This has come up many, many times. And I still don't know about it. 

if my vote counts (which it doesnt im sure :P) Id love these features  
myself.

>
> Am 06.10.2006 um 10:54 schrieb Manuel Poletti:
>
>>
>> On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote:
>>
>>> Do you mean:
>>>
>>> - A higher-level pattrstorage should inherit priorities from a  
>>> lower-level pattrstorage if in greedy mode?
>>>
>>
>> YES !!!
>
> If I write it on my list, will it make you happy? I don't  
> anticipate working on any major updates to pattrstorage for the  
> next while, but the time will come.
>
>>> - The pattr object itself should have a @priority attribute to  
>>> "hint" to pattrstorage that its priority should be set to a  
>>> certain value when the patch is analyzed?
>>
>> This could be very useful as well.
>
> This has come up many, many times. And I still don't know about it.  
> But OK. .
>
> jb.


(sorry for this double post... an error page with the forum...)

I rarely feel this strong about a feature request.

I'm replacing years of my own state-saving logic with pattr. I have tons of patches that I reuse in many different situations. The lack of "@priority" hampers the benefits of making reusable patches, i.e., every time I reuse one, I have to once again manually add the priorities of its controls to the pattrstorage handling the particular environment.

Since the hierarchical "::" path leading down to the patches changes from situation to situation, I can't simply cut and paste information.

If the pleas of one more person might shift the (ahem) priority of adding "@priority", then consider this a plea.

> - The pattr object itself should have a @priority attribute to "hint" 

> to pattrstorage that its priority should be set to a certain value 

I need to throw in a "me too" for this.  

I'm replacing years of my own state-saving logic with pattr.  I have tons of patches that I reuse in many different situations. The lack of "@priority" hampers the benefits of making reusable patches, i.e., every time I reuse one, I have to once again manually add the priorities of its controls to the pattrstorage handling the particular environment.

> - The pattr object itself should have a @priority attribute to "hint"  
> to pattrstorage that its priority should be set to a certain value  
> when the patch is analyzed?


Pattrstorage & pattr priority