what are PMSG functions for?
Chuck devs, what are PMSG functions for, as part of the class import process? Most of the PMSG functions that I see (in ugen_stk.cpp, ugen_xxx.cpp) just return TRUE; Graham
Hi Graham!
what are PMSG functions for, as part of the class import process?
The .pmsg was intended to be a general function for UGen's which allows one to pass string messages whose interpretations are solely defined by a particular UGen. For example, for a class such as Filter, it could take a formatted string via .pmsg to to set coefficients. The same pmsg string could mean something completely to another UGen. For the now, the .pmsg is not implemented to do anything interesting. It's just sitting there, probably waiting for strings operations to be implemented. As far as the import is concerned, a empty function returning TRUE is usually provided, though even this may not be necessary. I hope this help explain it. Best, Ge!
Good to hear from you, On Thu, 7 Sep 2006, Ge Wang wrote:
what are PMSG functions for, as part of the class import process?
The .pmsg was intended to be a general function for UGen's which allows one to pass string messages whose interpretations are solely defined by a particular UGen. For example, for a class such as Filter, it could take a formatted string via .pmsg to to set coefficients. The same pmsg string could mean something completely to another UGen.
Is it something specifically used to serialize/deserialize the state of a UGen? What does the P stand for? Does that mean there are also NPMSGs that do the same thing? :) So maybe they would work like this: StifKarp k => Filter f => dac; f.pmsg( "0.2 0.1 0.4; 0.2 0.4" ); or something more like this, like an alternate namespace: f.pmsg( "coefs", "0.2 0.1 0.4; 0.2 0.4" );
For the now, the .pmsg is not implemented to do anything interesting. It's just sitting there, probably waiting for strings operations to be implemented. As far as the import is concerned, a empty function returning TRUE is usually provided, though even this may not be necessary.
I'm still not sure I get it. But your explanation helps put it in perspective. (I'm working on a new UGen) best, Graham
Good to hear from you,
Same to you!
Is it something specifically used to serialize/deserialize the state of a UGen?
I don't think so. It's mostly intended to provide an alternate, and un-typed api for a UGen.
What does the P stand for? Does that mean there are also NPMSGs that do the same thing? :)
Huh huh. Um, I can't remember what the P in pmsg stands for anymore. As for them npmsg's... it's unclear whether they are equivalent to pmsg's - another open problem in chuckian theory.
So maybe they would work like this:
StifKarp k => Filter f => dac; f.pmsg( "0.2 0.1 0.4; 0.2 0.4" );
Yup!
or something more like this, like an alternate namespace:
f.pmsg( "coefs", "0.2 0.1 0.4; 0.2 0.4" );
That too, though pmsg, for generality is always one string. So it's more like: f.pmsg( "coefs 0.2 0.1 0.4; 0.2 0.4" ); The UGen can define the protocol freely.
I'm still not sure I get it. But your explanation helps put it in perspective. (I'm working on a new UGen)
I think the key idea is that .pmsg is, so far, pretty worthless, hahaha. Though it sounds like you've gotten how they are to work as much as there is get. We'd love to hear about the new UGen, too! There are a few new ones, mostly out-of-the-box filters, coming in 1.2.0.7 as well. Best, Ge!
participants (2)
-
Ge Wang -
Graham Coleman