clankill3r

If i open the poly's then they all have the same values.

 is never higher then 2 at the moment so i only expect 3 poly's to be used since i target them.

If i open the poly's then they all have the same values.
In my program that sends the OSC values /n is never higher then 2 at the moment so i only expect 3 poly's to be used since i target them.

all-polys-get-triggered-with-same-input-at-the-same-time

see 'target' and 'mute' descriptions in poly~ helpfile or reference(in sidebar of helpfile if you have max6), says sending '0' with mute/target messages sends message to all instances. specific voice instances are referenced starting from 1).

try using the 'trigger' object to trigger appropriate ordering of mute, target, and regular messages.

see 'target' and 'mute' descriptions in poly~ helpfile or reference(in sidebar of helpfile if you have max6), says sending '0' with mute/target messages sends message to all instances. specific voice instances are referenced starting from 1).
try using the 'trigger' object to trigger appropriate ordering of mute, target, and regular messages.


I increased the number by one before sending the OSC values so that's fixed now.

And indeed, only the correct poly's are set!

However, i hear nothing so i guess the un mute goes wrong:

Where $1 is equal to the target i want to un mute.

I increased the number by one before sending the OSC values so that's fixed now.
And indeed, only the correct poly's are set!

i don't have 'osc-route' object, so i don't know exactly what it does, but it still seems to have it's left outlet connected to a bang which then 'mutes all' as your comment describes. you sure, maybe, that's not being triggered right at the start or maybe even frequently along with the 'framecount'?

(if so, that might be your prob. if that's not your prob, i'm not sure... but you could try reworking the muting so it happens within the poly~ voice instead(see helpfile for thispoly~ object, and also see the old poly~ granular example here:

i don't have 'osc-route' object, so i don't know exactly what it does, but it still seems to have it's left outlet connected to a bang which then 'mutes all' as your comment describes. you sure, maybe, that's not being triggered right at the start or maybe even frequently along with the 'framecount'?
(if so, that might be your prob. if that's not your prob, i'm not sure... but you could try reworking the muting so it happens within the poly~ voice instead(see helpfile for thispoly~ object, and also see the old poly~ granular example here:
max/examples/sampling/granular ))

I think it's easier to mute all poly's every new frame cause i have no clue which poly's have to continue and which ones not.

It doesn't matter if you can hear it a little in the sound. I'm more worried about having no sound now.

I continue here to bump it a little since i'm running out of time :(

https://cycling74.com/forums/i-have-no-sound-with-polys-please-help-i-want-to-graduate-in-13-hours/

I think it's easier to mute all poly's every new frame cause i have no clue which poly's have to continue and which ones not.
It doesn't matter if you can hear it a little in the sound. I'm more worried about having no sound now.

https://cycling74.com/forums/i-have-no-sound-with-polys-please-help-i-want-to-graduate-in-13-hours/


all poly's get triggered with same input at the same time