Forums > MaxMSP

External control of poly~ properties

Jul 21 2006 | 5:28 pm

I’m having some trouble controlling parameters of a poly~ object I’ve created in the main patcher. In the patch I’ve built I have a poly~ object acting essentially as a bass drum, controlled by a rudimentary step-sequencing subpatch. The subpatch controls amplitude, which is sent with a "note" message to trigger the poly~. When I introduced controls over the frequency of the oscillator and the frequency of an svf~ filter, it seems as though the messages were only sent to the instance of poly~ occurring when the changes were sent. I attempted to resolve the issue by sending a bang at the same time as the "note" message to the numbers in the main patcher controlling pitch/cutoff in the poly~, thinking this would make sure the numbers were sent to all instances of the poly~, but this resulted in some other strange behavior. The patch is kind of involved but I can post it if need be. Any suggestions?

Jul 22 2006 | 2:24 pm

Jul 23 2006 | 3:44 pm

I dug around the poly~ help file a little more and figured out it was in
fact a "target" message I wanted to use, specfically "target 0" to target
all instances. The sequencing object I built itself is working fine with
just a "note" command in front of it, so at the moment everything I wanted
to accomplish is working fine. Thanks for the help.

On 7/22/06, Holland Hopson wrote:
> A few things to try…
> ?Are you sending all your messages with the "note" command (i.e. "note amp
> freq etc.")?
> ?Should you be using midinote instead? If I remember correctly, note works
> well when the poly~ instance has a defined duration; midinote is needed when
> the poly~ instance relies on a message to turn it off.
> ?Depending on what you’re trying to accomplish, the "target" message may
> be the way to go.
> —

Viewing 3 posts - 1 through 3 (of 3 total)

Forums > MaxMSP