Holy crap. That is weird. Do you know or have a theory as to why they have this strange design and/or limitation? I mean... I have never used a software within this category that won't allow you to modulate a delay (or similar). If anything I find parameters that can't be modulated because it's too CPU-crazy or it's by mistake. This seems like a design decision?blowfly wrote: Wed Feb 03, 2021 10:54 pm No, you're correct.
But there's a trick to have Delays on KG level though: use FX Racks.
But it only works with OSCs with in-built VCAs: FM Osc and Drum Osc.
UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!
-
- KVRer
- 10 posts since 27 Mar, 2008
-
- KVRer
- 15 posts since 6 Jan, 2010
You named it.
If you would like to, say, modulate the Decay time for a reverb in a 16 voice Program you'll end up in having 16 Reverbs (plus all the other parts of the Program), which could be a bit of a problem for the Cpu.
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
Keygroup level means you would have a delay per voice, which would be tremendously RAM and CPU intensive.
- KVRist
- 102 posts since 14 Jan, 2014
Rumor: The retriggering envelope at Layer level "hack" will be officially incorporated in Falcon 2.2
Falcon user since 2015
-
- KVRer
- 10 posts since 27 Mar, 2008
The CPU issue makes sense but their decision to limit the routing of modulations to only go in one direction is sort of arbitrary. Clearly we should be able to put a delay at the layer level and then send an ADSR modulation from a keygroup, outward to that layer. I'm finding the design of their software to be robust but unusual in very particular ways.EvilDragon wrote: Thu Feb 04, 2021 10:46 am Keygroup level means you would have a delay per voice, which would be tremendously RAM and CPU intensive.
-
- KVRer
- 10 posts since 27 Mar, 2008
Oh thank goodness. What is this hack?newuser2014 wrote: Thu Feb 04, 2021 12:32 pm Rumor: The retriggering envelope at Layer level "hack" will be officially incorporated in Falcon 2.2
-
Sampleconstruct Sampleconstruct https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=191286
- KVRAF
- Topic Starter
- 16733 posts since 12 Oct, 2008 from Here and there
Assign a keygroup to a re- triggering multi-envelope on layer level and set the envelope to legato mode. Then use that envelope to modulate whatever you want to. It's not polyphonic but helpful.estevancarlos wrote: Thu Feb 04, 2021 3:41 pmOh thank goodness. What is this hack?newuser2014 wrote: Thu Feb 04, 2021 12:32 pm Rumor: The retriggering envelope at Layer level "hack" will be officially incorporated in Falcon 2.2
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
That's because at layer level there's no polyphony (all voices are summed into a pair of audio outputs), and keygroups are all about polyphony.estevancarlos wrote: Thu Feb 04, 2021 3:40 pmThe CPU issue makes sense but their decision to limit the routing of modulations to only go in one direction is sort of arbitrary. Clearly we should be able to put a delay at the layer level and then send an ADSR modulation from a keygroup, outward to that layer. I'm finding the design of their software to be robust but unusual in very particular ways.
-
- KVRer
- 10 posts since 27 Mar, 2008
Let's see. I'm fairly new to Falcon. One week so far. I may not understand your instruction. I have the multi-envelope on the layer. Which envelope should be set to legato? The multi-envelope? Or is that one set to retrigger? Thanks in advance.Sampleconstruct wrote: Thu Feb 04, 2021 4:28 pmAssign a keygroup to a re- triggering multi-envelope on layer level and set the envelope to legato mode. Then use that envelope to modulate whatever you want to. It's not polyphonic but helpful.estevancarlos wrote: Thu Feb 04, 2021 3:41 pmOh thank goodness. What is this hack?newuser2014 wrote: Thu Feb 04, 2021 12:32 pm Rumor: The retriggering envelope at Layer level "hack" will be officially incorporated in Falcon 2.2

- KVRist
- 102 posts since 14 Jan, 2014
- KVRist
- 419 posts since 11 Jan, 2014
The workaround of how to do this is covered here...estevancarlos wrote: Wed Feb 03, 2021 7:40 pm Not sure if this is too off topic but is there a way to assign an ADSR envelope to a delay parameter? It sounds SO reasonable. Takes two seconds to pull off in Arturia's Pigments. I can not do it in Falcon because:
1) The delay FX are not available at the keygroup level
2) The ADSRs are not functional outside the keygroup level
Am I missing something?
https://falcontinuum.com/article/polyph ... -envelopes
-
Sampleconstruct Sampleconstruct https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=191286
- KVRAF
- Topic Starter
- 16733 posts since 12 Oct, 2008 from Here and there
My wording was misleading, set it to legato.estevancarlos wrote: Thu Feb 04, 2021 9:49 pmLet's see. I'm fairly new to Falcon. One week so far. I may not understand your instruction. I have the multi-envelope on the layer. Which envelope should be set to legato? The multi-envelope? Or is that one set to retrigger? Thanks in advance.Sampleconstruct wrote: Thu Feb 04, 2021 4:28 pmAssign a keygroup to a re- triggering multi-envelope on layer level and set the envelope to legato mode. Then use that envelope to modulate whatever you want to. It's not polyphonic but helpful.estevancarlos wrote: Thu Feb 04, 2021 3:41 pmOh thank goodness. What is this hack?newuser2014 wrote: Thu Feb 04, 2021 12:32 pm Rumor: The retriggering envelope at Layer level "hack" will be officially incorporated in Falcon 2.2
![]()
-
Sampleconstruct Sampleconstruct https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=191286
- KVRAF
- Topic Starter
- 16733 posts since 12 Oct, 2008 from Here and there
Another hack: if you have a patch with hundreds of keygroups, each one using its own ADSR amplitude envelope you can add an ADSR on Program level, then select all keygroups, delete all the individual ADSRs and assign the keygroup volume parameter to the ADSR on Program level, this will save a significant amount of CPU power.
-
- KVRAF
- 2481 posts since 28 Mar, 2005
CPU when you modify this ADSR with a macro or thought a script as there are fewer envelope to "touch", but at playback there shouldn't be any difference or maybe minor thanks to a better cache optimisationSampleconstruct wrote: Fri Feb 05, 2021 2:11 am Another hack: if you have a patch with hundreds of keygroups, each one using its own ADSR amplitude envelope you can add an ADSR on Program level, then select all keygroups, delete all the individual ADSRs and assign the keygroup volume parameter to the ADSR on Program level, this will save a significant amount of CPU power.
Memory, yes.
-
- KVRer
- 15 posts since 6 Jan, 2010

