[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.
A little precision : this bug happens when sound setting is on 48000kHz.
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./
----------begin_max5_patcher---------- 545.3ocyW00aaBCE8Y3WgEU6okhrMeTXZuzeGUSSDvqwUfAgcRSWUyu8guFR xhRItagz7hit2bsumyw95q4UWGu40qYROz2POfbbd00wAboc3za63UksNuLS Bg4IXOWO+IuYl+RwVq.2R9iaFbJVVUuTUxTvLH8dMtTuzvLoSOEQVoG5G8Az joxWvEO9yVVtxDSRjOdFhfi0+PuCL5F2NEdAj7N.cKkLj9eUKThrJHMd22x6 xwNfwEGhKc3R9ugvS8wZmu45pGl8+IIczfwWw1ftAea9K4kryu9jlBRhQYRw ioOgWaxijIJNk1fOE0oT3DRBYLpGc0Q8rESWwRLTrDP8ideEI4CpHzoVQ99F D1OZxJPBS.MIdrSIjnqMQ4KaPD+yulbGTrPwAflDNplDesoIeUePYpzDhoDZ 7ZGR5mll.q4TQ9PSS1ngwi1jkdTFNbMcdcUESX1n7tP7yhqDshYASJyLv9C2 jyryDfoml.A3Q6k8dD.VJuRt3vWABnQ6+uYkrdYa9f1ObsIZGhJXREWjo30h 8BpqeChrMlE7hBlXepWvkYyKY.aNdgg0vI1B3n0p8B5SGOQm.NU7hlZtP0uE kf02OQoTyiiS1ZsKMmO7mZA9OfjSodpeluUG2tPvgZi7jd4vSfE34.MbJwSn MxSzECNI1ta8ubYk4pzrllUrVY+ZBHoqUvS0sZy3YfIWXLgUr66DWwGhOzUu Zu49GjlKNpD -----------end_max5_patcher-----------
i get ya. might be a solution to put the [send~] and [receive~] outside the poly?
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
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.
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…