[PD] Fwd: finding the cause of clicks when using sssad WAS: saving state of a patch

[Si Mills]

I hope im not misunderstanding, but doesn't the s-abstraction way of  
using 'datastore' to change presets eliminate dropouts - Why is there  
a need for a ram disk? I mean is there a lag between hitting the giant  
message box and updating all the abstractions?

I was inspired the other day by a Max discussion on the pattr object,  
which is used for state saving. This in turn can be used from  
arranging pieces to to creating very nice random instruments that  
flick between presets very quickly...

Is this a problem for sssad at the moment?

>
> On 23 Jul 2008, at 15:24, Hans-Christoph Steiner wrote:
>
>>
>> On Jul 22, 2008, at 2:31 AM, Enrique Erne wrote:
>>
>>> Phil Stone wrote:
>>>> Hi Atte,
>>>>
>>>> Now that you're on your way with sssad, there's a nice trick you
>>>> should
>>>> know.  If you find that loading a preset causes dropouts, consider
>>>> using
>>>> a ram disk to hold your presets during performance.  This solved
>>>> all my
>>>> dropout problems, and it's easy to do (I can post a script for OS
>>>> X if
>>>> anyone wants it).
>>
>> The ramdisk thing is definitely handy, I just hope that sssad can be
>> tweaked to work without causing dropouts.  Any ideas what the cause  
>> is?
>>
>> .hc
>>
>>
>> ------------------------------------------------------------------------
>> ----
>>
>> Looking at things from a more basic level, you can come up with a
>> more direct solution... It may sound small in theory, but it in
>> practice, it can change entire economies.     - Amy Smith
>>
>>
>>
>> _______________________________________________
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>