WillyC

Firstly, apologies if this has been explained/corrected in one the plethora of poly~ threads. I couldn't find a clear/satisfactory answer anywhere, so am hoping someone can point out what it is I have missed....

When I load a patch containing a poly~ object WITH DSP RUNNING the poly~ patch will not respond to midinote messages. If I turn off and then back on again the DSP, the patch suddenly does start to work. Below are a very simple parent patch, and an offending patch (to be saved as sinevoice~) that is loaded by the poly~ object.

Can anybody else confirm this behaviour with the example given?

If so, could you explain why poly~ doesn't behave properly until the dsp is restarted? How might one get around this without restarting dsp?

I am using Max 5.0.5 on Os X. Curiously this problem only cropped up today when updating an old Max 4 patch - I'm sure the patch used to 'just work' when loaded in Max 4

unexpected-poly-behaviour

This is not related to the use of poly~. It used to be this way, that when you closed the last patch with singals, dsp would autmatically turn off. With the last update (or so) the functionality has been added to allow dsp to be running even when there is no patch open, and my theorie is that it's related to this. In my experience, patches opened (mac) are not added to the dsp chain. You need to toggle dsp off and on again. Just now I discover that patches opened through the Open dialog (which I hardly ever use) work fine but patches opened from the finder with a double click results in the described behavior. Furthermore I noticed that some patches are capable of turning off the dsp, like the simple-compressor from the effects folder in the examples. Honestly, this thing has been bothering me quite a bit, especially doing development when I'm switching between several patches all the time. On www.jvkr.nl/shelves you find a neat little DSPstrip patch that switches dsp with the esc-key. Saves a mouse click.

Unexpected Poly~ Behaviour