vicarious

I try to make a very simple synth using a cycle~ and a rect~ which I want to feed with a chord via keyslider but I cannot make it work properly.

I try to make a very simple synth using a cycle~ and a rect~ which I want to feed with a chord via keyslider but I cannot make it work properly.
I attached the patches  I made.
Can anyone help?

poly-and-oscs

You should look into the "note" and "midinote" messages to [poly~]. Also the "target" message.

 instance (probably the first one) all the messages.

What you could to do is, use the "midinote" message to pass pitch and velocity values you want at the next free instance i.e. "mininote 60 100" and as in the poly~ example, if you want to change the values of the [adsr~] you need to send once the message "target 0" to [poly~]. This message makes it so every message in the inputs, goes to 

 of the instances, thus controlling the adsr in every voice.

The edited patches work now, check them to see one of the ways to do it!

You should look into the "note" and "midinote" messages to [poly~]. Also the "target" message.
What you are doing is just sending to one instance (probably the first one) all the messages.

What you could to do is, use the "midinote" message to pass pitch and velocity values you want at the next free instance i.e. "mininote 60 100" and as in the poly~ example, if you want to change the values of the [adsr~] you need to send once the message "target 0" to [poly~]. This message makes it so every message in the inputs, goes to all of the instances, thus controlling the adsr in every voice.

The edited patches work now, check them to see one of the ways to do it! 

your explanation helped understand a couple of things.

There are two things that I noticed in the chords patch you sent me.

First there is an object named thru, Max says this object does not exist, and the second one is that I cannot play a new note until the last one finished its envelope

your explanation helped understand a couple of things.
There are two things that I noticed in the chords patch you sent me.
First there is an object named thru, Max says this object does not exist, and the second one is that I cannot play a new note until the last one finished its envelope


The [thru] object is actually just a subpatch, having just an inlet to an outlet, just to group the max cables - reduce the mess! You can just omit it, only connect the cables going to [thru] at the point the outlet of [thru] is connected.

If you see the comment in the "chords-edit" patch, the reason you cannot here more notes is because, the poly~ has 6 instances. The [poly~ two_oscs_edit 6 ....] means that you create 6 instances of the "two_oscs_edit".

You can send at poly~ the "steal 1" message that allows a "midinote" message to use an already busy instance or, just crank up the number of instances.

Having 6 instances and using 3 with every key press (you send the note, and note + 3 and note +7, that is using an instance for each one) is "eating" up 6 instances with only 2 keys pressed. If you don't enable voice stealing (steal 1) you have to wait until the adsr~ if finished, settings the instance to "not busy", so it can then be used again by the "midinote" message.

The issue usually when using the "steal 1" is that if an instance hasen't done playing its audio, and gets "re-triggered" it might produce a "click" in the sound (not good) depending on how it produces audio.

In your case because you are using sine/square generators, and the [adsr~] doesn't necessarily starts from "0" every time its re-triggered, it probably wont make clicks and it would be better (CPU-wise) to just use the voice stealing.

Just add a "@steal 1" at the end of the [poly~] obejct (or send to it the message "steal 1").

If you see the comment in the "chords-edit" patch, the reason you cannot here more notes is because, the poly~ has 6 instances. The [poly~ two_oscs_edit 6 ....] means that you create 6 instances of the "two_oscs_edit".
You can send at poly~ the "steal 1" message that allows a "midinote" message to use an already busy instance or, just crank up the number of instances.
Having 6 instances and using 3 with every key press (you send the note, and note + 3 and note +7, that is using an instance for each one) is "eating" up 6 instances with only 2 keys pressed. If you don't enable voice stealing (steal 1) you have to wait until the adsr~ if finished, settings the instance to "not busy", so it can then be used again by the "midinote" message. 

The issue usually when using the "steal 1" is that if an instance hasen't done playing its audio, and gets "re-triggered" it might produce a "click" in the sound (not good) depending on how it produces audio.
In your case because you are using sine/square generators, and the [adsr~] doesn't necessarily starts from "0" every time its re-triggered, it probably wont make clicks and it would be better (CPU-wise) to just use the voice stealing.
Just add a "@steal 1" at the end of the [poly~] obejct (or send to it the message "steal 1").

Thank you Nick...everything works right now,

but I mentioned that when I had 6 instances of my patch when I sent the ''steal 1'' nothing happened, then I changed the poly~ instances to 3 and the message to ''steal 3 '' work just fine...After all I guess the poly ~ object is not clear to me how it works

Thank you Nick...everything works right now,
but I mentioned that when I had 6 instances of my patch when I sent the ''steal 1'' nothing happened, then I changed the poly~ instances to 3 and the message to ''steal 3 '' work just fine...After all I guess the poly ~ object is not clear to me how it works


Yes, I guess [poly~] has a lot of things to understand and might be overwhelming, but once you get the hang of it all will be simpler!

The "steal 3" is the same as sending "steal 1". You can either enable voice stealing (steal 1) or disable it (steal 0), its an attribute of [poly~].

You could enable it from the [poly~]'s inspector, or add it in the object directly like [poly~ my-super-patch 6 @steal 1].

I am not sure why it didn't work. Maybe if you changed the [poly~] it reloads the patch, and the cycle and rect amps would need setting again (they are set from the [loadmess 0.5] when the patch first opens).

If you replace the poly~ text with this "poly~ two_oscs_edit 6 @target 0 @steal 1", then close and reopen the patcher, it should work without any more messages.

Yes, I guess [poly~] has a lot of things to understand and might be overwhelming, but once you get the hang of it all will be simpler!
The "steal 3" is the same as sending "steal 1". You can either enable voice stealing (steal 1) or disable it (steal 0), its an attribute of [poly~].
You could enable it from the [poly~]'s inspector, or add it in the object directly like [poly~ my-super-patch 6 @steal 1].

I am not sure why it didn't work. Maybe if you changed the [poly~] it reloads the patch, and the cycle and rect amps would need setting again (they are set from the [loadmess 0.5] when the patch first opens). 

If you replace the poly~ text with this "poly~ two_oscs_edit 6 @target 0 @steal 1", then close and reopen the patcher, it should work without any more messages.


Poly~ and Oscs