[bug?] when using [send~] in a [poly~] in Max Audio Effect

Mar 7, 2012 at 1:22am

[bug?] when using [send~] in a [poly~] in Max Audio Effect


Is it a bug ?

- put a [send~] object in a [ poly~] in a MaxForLive Audio Effect.
- change the size of the poly~ using ‘voices $1′ message

It works perfectly when Ableton Live (MaxForLive) is linked to Max5.
But it crashes when Ableton Live (MaxForLive) is linked to Max6.

Max6.0.4 & Max5.1.9


Please let me know if you encounters the same problem.
I already did a bug report on the website.

Mar 16, 2012 at 10:55am

A little precision : this bug happens when sound setting is on 48000kHz.

Mar 16, 2012 at 12:19pm

i believe it’s best practice to avoid [send~] and [receive~] inside [poly~].

there are a number of threads that variously deal with this.


Mar 16, 2012 at 1:16pm

Hello, yep thx for the information but in my case I have to use it because I use a trick to change phase only at the beginning of a phasor cycle. so it’s a big problem… f./

– Pasted Max Patch, click to expand. –
Mar 16, 2012 at 3:04pm

i get ya. might be a solution to put the [send~] and [receive~] outside the poly?

Mar 16, 2012 at 4:50pm

no, because each poly instance has his own cycle (because of the phase shifting), so it means it needs one system using the send-receive trick per instance.
you can find the entire patche here if you’re interested : http://www.maxforlive.com/library/device.php?id=1080

Mar 16, 2012 at 7:07pm

nothing better occurs to me at the moment than to substitute [tapin~ 0] and [tapout~ 0] for [send~] and [receive~]. but even that might not be ideal.

Mar 16, 2012 at 9:16pm

you’re right, if you’ve download the patch you have seen it’s exactly what I did but it’s a little bit more expensive for cpu…


You must be logged in to reply to this topic.