I have been working a lot with PD lately and have built some synths that I think make some pretty interesting sounds. I have also built some sequencers that produce complex patterns.

I have lately been researching modular analogue sequencers, the big rack type things. This has been giving me ideas about building a complete modular system with PD.

I have been thinking I could use my synths and sequencers together much more easily if they were modular. Also if a modular standard was developed, like standard CV ranges in analogue gear, we could trade module patches back and forth and build huge systems.

I have a few things I have been trying to figure out.

• since this system is modular would I be better off with something with vst au rtas ladspa etc. support? like a daw with reaktor? I would be able to patch back and forth between the effects and sound generators.

• does anyone know a good way to run the output from a program like reason or a daw into PD on OSX? I can't figure out how to do it with jack. I have been running out to my sound card and then back into it with a patch cable(completely ridiculous)

• it appears there will always be some type of delay/lag/buffer/latency with PD, maybe with all software synths? In my masterplan giant modular system with a computer and some external analogue effects / sound generators I could patch out of the computer and then back into it. Will the latency kill me doing this? will a crazy quad core tons of ram computer deal with super low latency?

I know that is a bunch of questions in one post, but if anyone has any ideas let me know.

Thanks

I'm not sure I entirely understand your first question. Why exactly would plugin support help your modular design in Pd?

As for routing audio, I use jackOSX with Pd all the time. Here's how it works for me:

• Open JackPilot.
• In the preferences, set your buffer size and such to your liking. The virtual ins and outs are important. These are the number of connections that will be allocated to each app.
• Start the server.
• Open Pd and, under the media menu, select jack mode. This will open the audio setting dialog with jack set as the input and output device. Adjust the channels to whatever you need.
• Open whatever other app you're using and set the input and output devices to jack server or whatever it says.
• Now, go back to JackPilot and click the Routing button. In the send ports (which are your apps' outputs) unfold Pd's and select and output. Under receive ports, unfold the other app and double click the input you want to connect to. Or vice versa if you're feeding into Pd. Also, make sure that you're routing the app with the mixed signal (probably the DAW, if you're using that) to the sound card's inputs. This is always labeled "system."

Yes, there will always be latency, but on OSX it seems to be minimized with jack. Even if you're using Pd on its own, you can get lower latency if you route through jack and then into the sound card. You will get added latency every time you go in and out, so try to minimize that. And multiple cores won't make a difference if you're only using Pd, as it will only run on a single core. If you're using other apps, then it might help as they may run on a different core than Pd.

As for the standardization, I know there are some who would like to see everything scaled in a 0-1 range. But I don't think it's that big of a deal in Pd when it comes to sharing patches, as Pd gives you what you need to convert ranges if you need to. I would just go with what works best for your particular needs. Sometimes standards set by others can get in the way.

If you haven't yet, check out hardoff's DIY2 library. It might give you some ideas.

http://puredata.hurleur.com/sujet-1982-diy2-effects-sample-players-synths-sound-synthesis

Hope that answers some of your questions.

Awesome, thanks for the jackosx help.

plugin support would be helpful because say I have a plugin that is a really good filter or distortion etc. etc. yes I could build something in PD that would be equivalent, but I guess the whole point of what I am thinking of is to have options open to use almost any hardware or software sound devices together. Although on the other hand maybe I will learn more if I try to emulate the plugins I would use in PD instead of integrating the plugins themselves into my modular system.

As far as standards go I guess I was thinking more that patches for the modular system be designed not just as a standalone item (although some could be used standalone as well) but to be able to be opened inside of another patch with inlets and outlets for controlling the parameters and inputting and outputting sound.

Thanks for the recommendation of the diy2 library I will check it out.

Oh, I see what you mean now. Well, I know there is a [plugin~] object for LADSPA plugins, but I've never actually used it, so I don't know if it works.