[PD] [pmpd] - meaning of messages

cyrille cyrille.henry at la-kitchen.fr
Mon Feb 28 18:09:42 CET 2005

hello ben,

B. Bogart wrote:
> Hi Frank,
> I'll take a crack at this, Please correct me where needed Cyrille!

> Hmmm indeed there is a single object called "pmpd" I am not sure what 
> this does, but sounds like it allows you to make a physical model 
> without having to connect patch-cords and use pmpd component objects. 
> I'm going to guess all these answers are the same in pmpd as in [mass] 
> [link] etc..
you're right!

> The ID in [mass] is used as a receive name so that the render signal can 
> be sent without connecting a cord. Same goes for [link] At the top of 
> most pmpd examples is:
> [metro]
>  |
> [t b b]
>  |    |
> [s m] [s l]
> Where the ID of the masses is "m" and the ID for links is "l".
> This means you can control the rendering of different structures based 
> on thier ID name.

exept that the t b b is internal of the [pmpd] object.
so you do not "nead" the id.
it's just usefull if you wish to change the rigidity of a link etc...

> I'm guessing the In and Out stuff has to do with comunicating from the 
> internal physical model to the outside patch.

> Frank, is there a strong reason you are using the pmpd object, and not 
> using [mass] [lia] etc?? Much easier to start here and I think make many 
> things clear...
> So Cyrille, what is the [pmpd] object? Why is there no help for it in 
> CVS? What is it for?
i send an announce for this few mounth ago.
every thing i got is on the cvs (3 exemples are the only avalable help)

i made this for diferents reasons :
it's a way to improve automatic structure creation.
but the 1st goal was to be able to do audio objects.
the 2nd goal (thanks to frank) is to make things simpler for data 
structure connection.

as frank say yesterday about data structure, mouse handling mead to be 
improve befor i can port pmpd exemple with data structure, but i would 
really love to have some bouncing structure replacing some boring fader 
to control an audio synthesis.

anyway, there is no real doc because they are not really finished.
i commited them to the cvs in order to collect idea from user.

0.07 could not be compatible with 0.06 : use it at you own risk!


> Hope I helped a bit Frank.
> B>
> Frank Barknecht wrote:
>> Hi,
>> I have a couple of questions regarding the [pmpd] object. It is not
>> quite clear to me, what the messages to this object mean exactly.
>> Actually I'm very confused about them.
>> As I see it, there are basically four messages possible to create the
>> dynamic system: mass, link, in, out.
>> All of these take IDs as arguments. I don't understand the meaning of
>> those IDs. For example to create a mass, one uses messages like:
>> mass ID MASS X
>> MASS and X are easy, but what is this "ID" used for?
>> "link" also takes IDs as argument, but it seems to ignore the ID given
>> to a mass on creation, instead it seems to use its own IDs and it has
>> an ID itself:
>> Where do I get the mass IDs from? In my experiments, it seems just
>> have to keep track of them myself, and they have nothing to do with
>> the ID I gave to a mass earlier. Or do I get it wrong?
>> Outlet creation (and inlet creation respectively): As I understand it,
>> the format is:
>> AMPLITUDE seems to be a scaling factor. OUT-ID I don't understand at
>> all: what use does it have? Am I right to assume that OUTLET is
>> numbered from 0 to max-outlet-number, where max-outlet-number is the
>> second argument of pmpd minus one? And then MASS-ID: Does it start
>> from 0 as well? Or from 1? Where do I get this ID from? In my
>> experiments, it seems to have to be the MASS-ID I used when creating
>> the "link"s.
>> Sorry for my confusion...
>> Ciao

More information about the Pd-list mailing list