hello, i've made a new pmpd version. There is 3 new objects : pmpd, pmpd2d and pmpd3d. this 3 objects should replace MSD. most of the time, they are compatible. there is few differences anyway : - few messages get renamed (both on input or output) - there is a difference on the calculation of tLink Damping - there is now a damping associate with each masses - there are more messages to get simulation data
I encourage anyone to switch from MSD to pmpd, since MSD will not be maintained.
help / examples / sources can be found on pd svn.
Cyrille
It would be nice to have a second outlet on [pmpd], [pmpd2d] and [pmpd3d] like on MSD objects. The 54_pmpd_wave.pd example doesn't work here. [pmpd] seems to have a problem. Do test and interaction objects work with [pmpd], [pmpd2d] and [pmpd3d] masses ? ++
Jack
Le jeudi 24 février 2011 à 19:04 +0100, cyrille henry a écrit :
hello, i've made a new pmpd version. There is 3 new objects : pmpd, pmpd2d and pmpd3d. this 3 objects should replace MSD. most of the time, they are compatible. there is few differences anyway :
- few messages get renamed (both on input or output)
- there is a difference on the calculation of tLink Damping
- there is now a damping associate with each masses
- there are more messages to get simulation data
I encourage anyone to switch from MSD to pmpd, since MSD will not be maintained.
help / examples / sources can be found on pd svn.
Cyrille
Pd-announce mailing list Pd-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
cyrille henry -
Jack