Page 1 of 1

Poly Vs. Mono gate

PostPosted: Mon Oct 15, 2018 1:48 pm
by Rocko

Please see attached image. In it I have two similar channels:

A. Poly Oscilator --> Combiner --> ADSR
B. Poly Oscilator --> ADSR --> combiner

Both receiving their 'frequency' parameter from a 'midi to poly' module.

The 'A' setup does not 'trigger' the ADSR (as it is not connected to a GATE or TRIGGER) so when a key is pressed, nothing really happens, unless the 'Sustain' and 'envelope' are none zero.
The 'B' setup triggers the ADSR even though no GATE or TRIGGER is attached.

Why is it so ?

Re: Poly Vs. Mono gate

PostPosted: Mon Oct 15, 2018 4:31 pm
by Spogg
The upper path contains an envelope generator in the blue mono stream. It can never be triggered by the poly (white) system.

The lower path will work as shown because in the preset properties the “Gate” option isn’t ticked. If you tick that option you would need a poly Gate signal to fire off the ADSR while a note is played. The Gate option allows you to fire off ADSR envelopes under your control, rather than the default situation where the software does it based on MIDI notes being played.

Each new MIDI note opens up a new poly channel with its own i.d. number. These are running in parallel until joined together with a combiner. So if you play a 4 note chord the software creates 4 identical poly streams in memory, so 4 oscillators and 4 ADSRs in your example. The mono stream doesn’t operate in that way. You just get what you see in the schematic.

It’s not so easy for me to explain, but I hope this has helped a bit.



Re: Poly Vs. Mono gate

PostPosted: Wed Oct 17, 2018 12:13 pm
by Rocko
It helped a lot, thanks !