Is there a pattrstorage attribute or trick I'm missing allowing to 

interpolate from the current state of a preset to another ? My problem 

is that when using 'recall 1 2 )', all clients jump to 

their saved state in slot 1, ignoring changes since recalling 1. The 

solution I'm thinking about would be to store clients state in slot 0, 

then interpolating from slot 0 to slot 2 but I just want to make sure 

I'm not missing or misunderstanding one of the existing pattrstorage 

Is there a pattrstorage attribute or trick I'm missing allowing to  
interpolate from the current state of a preset to another ? My problem  
is that when using 'recall 1 2 )', all clients jump to  
their saved state in slot 1, ignoring changes since recalling 1. The  
solution I'm thinking about would be to store clients state in slot 0,  
then interpolating from slot 0 to slot 2 but I just want to make sure  
I'm not missing or misunderstanding one of the existing pattrstorage  
functions. If I'm not, any better idea ?

pattrstorage-interp-from-current

Unless there are some undocumented features we don't know about, I think your idea is the best option. That's how I would do it, at least.

> Is there a pattrstorage attribute or trick I'm missing allowing to 

> interpolate from the current state of a preset to another ? My 

> problem is that when using 'recall 1 2 )', all clients 

> jump to their saved state in slot 1, ignoring changes since 

> recalling 1. The solution I'm thinking about would be to store 

> clients state in slot 0, then interpolating from slot 0 to slot 2 

> but I just want to make sure I'm not missing or misunderstanding 

> one of the existing pattrstorage functions. If I'm not, any better 

> Hi,
>
> Is there a pattrstorage attribute or trick I'm missing allowing to  
> interpolate from the current state of a preset to another ? My  
> problem is that when using 'recall 1 2 )', all clients  
> jump to their saved state in slot 1, ignoring changes since  
> recalling 1. The solution I'm thinking about would be to store  
> clients state in slot 0, then interpolating from slot 0 to slot 2  
> but I just want to make sure I'm not missing or misunderstanding  
> one of the existing pattrstorage functions. If I'm not, any better  
> idea ?
>
> Best,
> Julien.


pattrstorage: interp from current