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

2008-07-23 Thread Hans-Christoph Steiner
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

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

2008-07-23 Thread Phil Stone
Hi Hans, I don't think this is anything to do with sssad, really. It is due to Pd's lack of a threaded file loader/saver. The way I understand it (and this is borne out by my experience), if a file operation cannot complete within one dsp cycle, the next dsp cycle is delayed until after the

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

2008-07-23 Thread Hans-Christoph Steiner
Part of the problem could also be that it is using canvas_open() which means it searches the whole Path when using a relative name. Try using absolute path names for the file to see if that speeds things up (canvas_open() tries absolute file names first). It would be possible to use a