paraprosdokian

I am having trouble with poly~ in a larger patch.

I have gotten this to work in a stand alone patch: poly~ receives signal, receives a [note $1] message approx every 500ms, which triggers enveloping of a bit of signal within the abstraction and transposition of that enveloped bit by the amount indicated in [note] message. (using [in~ 1] and [in 1] in abstraction, etc)

But, when I include this in a larger patch, it does not work (I've tried poly~ in abstraction, non-abstraction subpatcher, and totally un-encapsulated). However, if I reload poly~ by, for instance, double-clicking on this object and changing the number of voices, subsequently it works.

Within the poly~ abstraction, I see incoming signal. I also created a sprintf; on loading the big patch, each abstraction reports, but subsequently nothing (i.e., no control info entering poly~ abstractions until after I manually re-load the poly~ object).

There is nothing much else in the big patch that should conflict with poly~ (just some additive synthesis with saw~ waves etc).

Is this a dynamic loading problem? If I must re-load poly~, is there an easier way than double-clicking etc?

I have gotten this to work in a stand alone patch: poly~ receives signal, receives a [note $1]  message approx every 500ms, which triggers enveloping of a bit of signal within the abstraction and transposition of that enveloped bit by the amount indicated in [note] message. (using [in~ 1] and [in 1] in abstraction, etc) 

poly~ only works after double-click reload