On Wed, 2008-07-16 at 12:01 +0200, IOhannes m zmoelnig wrote:
hard off wrote:
why do tilde objects work in vanilla pd, but the zexy tilde objects are so uncooperative?
which object gives you trouble? [noisi~], [limiter~], [dirac~]?
anyhow, zexy's objects are not uncooperative at all.
zexy is and was meant to be compiled as a multi-object library, just like Pd (kind of).
then Pd-extended came along and tore the happy family apart into single-object externals and the trouble began. i guess you are using Pd-extended?
and no, this is no rant about Pd-extended, the problem is a deeper one (and was almost solved in Pd-vanilla - but alas! in the end it was not),
what was the reason for that?
it just happens to be exposed very much by PdX's policy.
so, please be cooperative, compile zexy yourself (as a multi-object library - which is the default), load it and be happy.
last time i tested pd-extended, it was definitely not all tilde classes from zexy, that made troubles, but only [<~] and [>~]. probably there are some others, that have 'special' chars in their names. however, the rest was working well.
even while using pd-vanilla, i used to compile zexy as single-object externals in order to make my patches as troublefree as possible on pd-extended. i also used to use the hexloader and, iirc, i could instantiate [<~] and [>~] without problems (unlike pd-extended, that is why i switched back to a multiclass binary). anyway, my point is: it was once working here on my box without issues at all, even if i had zexy as single-objects externals. what does it need to make it work on pd-extended as well?
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de