I've seen some patches PD on websites recommanded on the mailing list and I'm a little disappointed. Just 10 or 15 patchs on the Web, it's a joke?

http://www.google.com/search?q=%22pd+patches%22

Results 1 - 10 of about 778. Search took 0.10 seconds.

abel.jerome@free.fr schrieb:

I've seen some patches PD on websites recommanded on the mailing list and I'm a little disappointed. Just 10 or 15 patchs on the Web, it's a joke?

Tell me more about the PD communauty, maybe the main purpose is to create externals?

Hi Jerome,

I think one of the main reasons for what you describe is that externals can be published 'as is'. They don't need any special explanation except their help patches. They are one of the smallest parts you can get. Highly specialised and (relatively) easy to explain. Think of complex patches, most of them would be far too complex to describe.

My main use of Pd is to control interactive installations and there, a lot of different sensors and / or interfaces are used to control the sound / video being generated. Such patches have no (or at least reduced) value when used in a different context. They need special hardware (that I might build for one special purpose) and are optimised for _one_ situation. At the moment I'm trying to reuse one of my own patches I did about a year ago but I realised very soon it would have been easier to create a new one from scratch. (At least my) patches are growing all the time and get 'dirty'. At first they look good but don't really do what I want. In the process of setting up an installation I usually spend two or three days patching in the gallery space (if possible) when everything (=hardware) is set up. I need the actual situation, have to hear what's happening and how it fits the sourroundings. In that period the patches grow very fast and get more and more 'untidy'.

But you're right, I spend about 90% of my time with Pd coding externals or building hardware. I don't know wether this is a good or a bad thing. Pd (or Max/MSP) allows me to code the parts that I feel are missing. I don't know any other tools that could be extended that easily.

Of course, there might be other points of view from poeple using Pd to make music...

[I don't know where creativity ends and 'presets' start. One of the very good things about Pd is that everyone has to create it's own patches. Like in the old days with analogue synthesizer _without_ factory presets and 'custom memory banks' where everyone had to make ones own sound. It helps you to create your individual sound because this sound is based on your individual patches. But, yes, of course, we need example patches showing how to use the objects. And, me culpa, I sometimes do use Pd's example patches as a starting point for my own stuff.]

Olaf

Hi

Learning PD (Pure Data) is a steep learning curve, but a rewarding one. However...

I have been working for three years on an interactive music system, which analyses incoming audio and re-synthesises phrases of the audio stream according to similarities in the parametric analysis of the audio. When approaching PD I already had a background in MAX/Msp programming, and so thought that PD would enable me to create software with the same flexibility as MAX patches but without the commercial investment. As a student this was very important, but as a believer that my patches might bring about new tools for, and ways of thinking about interactive performance this became doubly important.

After three years I have not published a single patch. I'll tell you why.

Without documentation a patch can be frustrating to use, especially if it contains multiple abstractions (sub-patches which are called from within a "master" patch). Very few of us are so financially enamoured (rich) to have the time to create such documentation or so philanphropic, and the creative process within such a flexible working environment is such that ideas frequently overtake the realisation of such ideas. Furthermore, my patches make use of many externals. Some of these are muli-platform, but others are not. Windows and OSX users (for example) will find that my patches do not work because the ggee library has not been ported to Windows! (Gunther, this would be a good thing!)

PD as a multi-platform application invites diversity of development amongst the community of users, who make everything from routing systems to music to multimedia and graphics with it. The lack of a common "clique mentality" (such as exists within the Apple Macintosh community, particularly with regards to MAX/Msp) can inhibit the sharing of source information (patches), yet in another more profound way it encourages this by being platform-independent and open-source. How many MAX/Msp sites contain source code (patches)? MAX/Msp allows the user to make an app out of his or her patch, thus making any abstractions or uses of objects unusable to the one who downloads this software. People are protective of their ideas, especially in a global media network such as the internet! Does open source mean open access to all? There are lots of issues with regard to this which extend far beyond the PD-user community, and the debate goes on!

I'm a french guy, I would like to participate on the possible translation

of PD

documentation in French, Do you think it will be happened?

ja kan prata en liten svenska, mais je voudrais a (speak) francais tres bon! Do it!

I'm working on an interactive (sensors convert to midi) sampler with PD, I

will

put it on the web. If anyone is working about the same idea, may be we can give ourself some

stuff.

I've made a modification of the pitch-shifter engine (pd documentation) combined with a playback engine, so that we can do any sample at any pitch with any timestretch parameter. I'll put it on my site when my site is up and running (sorry I can't do better right now!).

Best, Ed

I would love to have French translations of the Pd Docs. We are currently in the process of building the new pure-data.org and we aim to have it translated into as many languages as possible. The structure will be in place, it will just be a matter of people doing the translations.

.hc

On Wednesday, Jun 25, 2003, at 11:45 America/New_York, abel.jerome@free.fr wrote:

hI again,

I've seen some patches PD on websites recommanded on the mailing list and I'm a little disappointed. Just 10 or 15 patchs on the Web, it's a joke?

Tell me more about the PD communauty, maybe the main purpose is to create externals?

I'm a french guy, I would like to participate on the possible translation of PD documentation in French, Do you think it will be happened?

I'm working on an interactive (sensors convert to midi) sampler with PD, I will put it on the web. If anyone is working about the same idea, may be we can give ourself some stuff.

greeting,

jerome

---

PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list