clankill3r

I worked on a suitcase that can be transformed into a table which has a big program running behind it to track things.

The last step is to produce some sound as a demo. I'm kind of stuck on this for some time now, polys and max is not easy if your more used to work with codes of line and classes.

I added a screenshot to explain a little of the sketch.

Even when i disconnect the "mute 0 1" (which mutes all as you guys probably know better then me), then still i hear no sound. So my guess is that the unmute goes wrong.

If i send a "mute 1 0" to only unmute the first voice then i still hear no sound but i see all values change (also in poly 1).

If i have the thing that mutes all disconnected and i send a "mute 0 0" to unmute all then i have sound.

I worked on a suitcase that can be transformed into a table which has a big program running behind it to track things.
The last step is to produce some sound as a demo. I'm kind of stuck on this for some time now, polys and max is not easy if your more used to work with codes of line and classes.

i-have-no-sound-with-polys-please-help-i-want-to-graduate-in-13-hours

Wild guess, I just looked at the screenshot:

Because of right to left order, you always switch on the one voice you need forst and then turn off all voices.

Wild guess, I just looked at the screenshot:
Because of right to left order, you always switch on the one voice you need forst and then turn off all voices.
right?


I receive the OSC frameCount message before the other data. And i mute on the FrameCount message.

No it's not that :(
I receive the OSC frameCount message before the other data. And i mute on the FrameCount message.


If it helps, here is the log of one time going over a image:

https://dl.dropboxusercontent.com/u/17630770/playImageLog.txt

I also added the image so you guys have an idea what is going on.

It reads the image from top to bottom and sends the y position and the length of the white.

As you can see at the end of the image it sends 2 lines of data cause the "scanline" is intersecting both blocks at a certain time.

The frameCount is followed by the data, if any. This goes fast, then it takes around 30ms before it receives the next frameCount message.

I also added the image so you guys have an idea what is going on.
It reads the image from top to bottom and sends the y position and the length of the white.
As you can see at the end of the image it sends 2 lines of data cause the "scanline" is intersecting both blocks at a certain time.

The frameCount is followed by the data, if any. This goes fast, then it takes around 30ms before it receives the next frameCount message.


On phone so I can't see the poly~ patch, but assuming that the mute message is going to a thispoly~, I think the problem is that mute isn't a targeted message. Usage with thispoly~ is "mute 0" or "mute 1" because the muting operation is happening inside the voice so there's no need for a voice number. (E.g it's being generated by ADSR~'s third outlet). Right now you're muting the targeted voice since it's just interested in the first nunber after mute. (which here is non-zero, causing it to mute the voice; the zero after it is just ignored) Try a message box with "target $1, mute 0" instead.

Also, if you are just trying to switch audio on and off, muting the whole poly~ voice might be overkill. You could use gate~ or *~ to turn on/off audio output.

On phone so I can't see the poly~ patch, but assuming that the mute message is going to a thispoly~, I think the problem is that mute isn't a targeted message.  Usage with thispoly~ is "mute 0" or "mute 1" because the muting operation is happening inside the voice so there's no need for a voice number. (E.g it's being generated by ADSR~'s third outlet). Right now you're muting the targeted voice since it's just interested in the first nunber after mute.  (which here is non-zero, causing it to mute the voice; the zero after it is just ignored) Try a message box with "target $1, mute 0" instead.  

Also, if you are just trying to switch audio on and off, muting the whole poly~ voice might be overkill.  You could use gate~ or *~ to turn on/off audio output.


I also now what the problem is now, it has to do with OSC-route, i will make a new post for it.

thanks, i unmute in the poly now.
I also now what the problem is now, it has to do with OSC-route, i will make a new post for it.


just skip using OSC-route, for what you're doing you can easily get by with just normal [route].

I do not have time to look in the patches but the message "mute 0 1" or "mute $1 0" does not exist. It should be "mute 0, 1" then "mute 1, 0".

When you put a comma in a message box, you're able to send many messages.

For example "mute 1, 0" is like two message: "mute 1" then "0"

The mute message active audio in the instance, and the value (1 or 0) to [thispoly~ ] frees the instance.

See the documentation or help patch … well explained …

Hi,
I do not have time to look in the patches but the message "mute 0 1" or "mute $1 0" does not exist. It should be "mute 0, 1" then "mute 1, 0".
When you put a comma in a message box, you're able to send many messages.
For example "mute 1, 0" is like two message: "mute 1" then "0"
The mute message active audio in the instance, and the value (1 or 0) to [thispoly~ ] frees the instance.
See the documentation or help patch … well explained …


but the message "mute 0 1" or "mute $1 0" does not exist

don't have time to confirm this for max5, but in max6, these messages do exist, but are used outside the poly~("mute 1 1" turns on muting just for voice#1 according to the helpfile).

from within a poly~ voice, the message "mute 0, 1" is actually two messages, one to mute the voice, and the second(1) to turn the busy-state on(these are two different things, setting the busy-state is not the same as muting audio).

just to keep from introducing any confusion :)

(clankiller, if you're still having probs, peter mcculloch's advice is most comprehensive)

don't have time to confirm this for max5, but in max6, these messages do exist, but are used outside the poly~("mute 1 1" turns on muting just for voice#1 according to the helpfile).
from within a poly~ voice, the message "mute 0, 1" is actually two messages, one to mute the voice, and the second(1) to turn the busy-state on(these are two different things, setting the busy-state is not the same as muting audio).
just to keep from introducing any confusion :)

(clankiller, if you're still having probs, peter mcculloch's advice is most comprehensive)


I fixed it, i still had problems but I did graduate :)

i have no sound with poly's, please help, i want to graduate in 13 hours!