Stefan Tiedje

I have a patch with a pattrstorage which stores the settings of vst 

plug-ins. I have just two pattrs, one is bound to a multislider which 

contains all parameters of the vst, and another will store the name of 

I need information of the stored presets at different places. At the 

moment I just send a bindto message to the main pattrs, to reroute the 

information. Is there maybe another way to achieve this, recall a 

certain preset element and send it directly to varying destinations 

(pattrs or named objects) instead of the original object?

My setup does work, but I am not sure if it could possibly create 

conflicts. It seems a bit too complicated...

I have a patch with a pattrstorage which stores the settings of vst 
plug-ins. I have just two pattrs, one is bound to a multislider which 
contains all parameters of the vst, and another will store the name of 
the plugin.

I need information of the stored presets at different places. At the 
moment I just send a bindto message to the main pattrs, to reroute the 
information. Is there maybe another way to achieve this, recall a 
certain preset element and send it directly to varying destinations 
(pattrs or named objects) instead of the original object?

My setup does work, but I am not sure if it could possibly create 
conflicts. It seems a bit too complicated...

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


is-there-an-bettr-pattr-way-of-doing-this

> You can restore preset data directly from pattrstorage:

Thanks, easy enough to route it from there...

Another question: is it possible to "rebind" a pattr? I'd like to send 

it a message which would put the pattr back to its initial state. If it 

had no @bindto parameter it should just cut all bindings and if it had a 

If I send a bindto without parameters, its unbinding the pattr, but sets 

its value to 0. Maybe it would be better to either output a previous 

"unbound value" or just nothing.... Sending a zero does not make sense 

for me - It has no meaningful information but would eventually trigger 

something... (filtering zeros is not a solution, because in most 

For backward compatibility the rebind message could work to address that 

Jeremy Bernstein schrieb:
> You can restore preset data directly from pattrstorage:
>
> getstoredvalue

Another question: is it possible to "rebind" a pattr? I'd like to send 
it a message which would put the pattr back to its initial state. If it 
had no @bindto parameter it should just cut all bindings and if it had a 
@bindto parameter revert to that....

If I send a bindto without parameters, its unbinding the pattr, but sets 
its value to 0. Maybe it would be better to either output a previous 
"unbound value" or just nothing.... Sending a zero does not make sense 
for me - It has no meaningful information but would eventually trigger 
something... (filtering zeros is not a solution, because in most 
contexts a zero does have a meaning...)
For backward compatibility the rebind message could work to address that 
issue...

pattr forgets its previous state when bound. Not likely to change 

anytime soon, although I can understand your argument as to why it 

Am 20.04.2007 um 11:07 schrieb Stefan Tiedje:

>> You can restore preset data directly from pattrstorage:

> Thanks, easy enough to route it from there...

> Another question: is it possible to "rebind" a pattr? I'd like to 

> send it a message which would put the pattr back to its initial 

> state. If it had no @bindto parameter it should just cut all 

> bindings and if it had a @bindto parameter revert to that....

> If I send a bindto without parameters, its unbinding the pattr, but 

> sets its value to 0. Maybe it would be better to either output a 

> previous "unbound value" or just nothing.... Sending a zero does 

> not make sense for me - It has no meaningful information but would 

> eventually trigger something... (filtering zeros is not a solution, 

> because in most contexts a zero does have a meaning...)

> For backward compatibility the rebind message could work to address 

pattr forgets its previous state when bound. Not likely to change  
anytime soon, although I can understand your argument as to why it  
should remember it.

> Jeremy Bernstein schrieb:
>> You can restore preset data directly from pattrstorage:
>> getstoredvalue
>
> Thanks, easy enough to route it from there...
>
> Another question: is it possible to "rebind" a pattr? I'd like to  
> send it a message which would put the pattr back to its initial  
> state. If it had no @bindto parameter it should just cut all  
> bindings and if it had a @bindto parameter revert to that....
>
> If I send a bindto without parameters, its unbinding the pattr, but  
> sets its value to 0. Maybe it would be better to either output a  
> previous "unbound value" or just nothing.... Sending a zero does  
> not make sense for me - It has no meaningful information but would  
> eventually trigger something... (filtering zeros is not a solution,  
> because in most contexts a zero does have a meaning...)
> For backward compatibility the rebind message could work to address  
> that issue...
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>


Is there an bettr pattr way of doing this...