Hi Everyone,

I'm having trouble with Pd on a linux machine. I have installed PureDyne onto a ThinkPad x61 and wish to connect Pure Data to Processing. However, I've encountered a problem right from the start with Pd. I keep getting a/d/a sync errors. I've tried using jack, OSS and ALSA to configure sound input/output, but still I have no joy. In particular, I notice that the problems are exacerbated when I use the bsaylor partconv~ external.

I'm rather new to linux, so forgive me if the information I've provided is rather vague. But do I need to setup ALSA or Pd in any particular way? I've tried running Pd from the command line with the -rt flag, as well as following an optimised jack setup that I found on the forum. I notice that this sort of problem has been posted a few times here, but all the solutions given have not provided me with a successful outcome.

Thanks!

James

Yes, I'm seeing messages in the terminal window that say:

Jack: JackClient::ClientNotify ref = 4 name = pure_data_0 notify
Jack: JackClient::kXRunCallback

My patch doesn't have many GUI elements, though I am using the bsaylor partconv~ external. I've noticed that whenever I change the impulse file it causes an error. Though errors still occur without this. Even when I don't use Jack I still get a/d/a sync errors.

I don't use a Windows, but from what I know Pd only uses one processor core. However, there are a couple of ways around this.

One way is to split up the patch, run each part of the patch with a separate instance of Pd and use netsend or OSC to communicate between the instances. I've not tried this myself, but check out this posting on the forum: http://puredata.hurleur.com/sujet-2957-cpu-load-only-use-single-core

The other way is to use the [pd~] object. This object was added to Pd 'to allow users to embed separate Pd processes inside each other, so that the OS can schedule the processes on separate CPUs' – check out Miller Puckette's paper, Multiprocessing in pd for more information. With the [pd~] object you are able to run different instances of pd through a master patch, but without the hassle of using OSC or netsend to communicate between them.