Why a Layer-Level Modulation Envelope Does Not Respond to MIDI Notes in UVI Falcon
In UVI Falcon, a layer-level envelope may fail to retrigger from MIDI notes because its destination is a layer or program parameter. An envelope stored on the layer can still retrigger when assigned to a keygroup, oscillator or keygroup-effect parameter. Check the destination before moving the envelope or changing MIDI settings. UVI Falcon — Structure
This guide is for sound designers troubleshooting a patch that plays normally but lacks the expected note-triggered modulation. The task is to identify the failing connection, restore per-note movement and decide when shared layer modulation needs a different control method.
What does “layer-level envelope” actually describe?
Separate three questions: where the envelope is stored, which parameter it controls and what restarts its contour. Those settings describe different parts of the patch.
Falcon distinguishes a layer, which groups keygroups, from the keygroups that start voices. Its manual explicitly ties note retriggering to the destination: envelopes assigned to keygroup-level parameters retrigger with notes; envelopes assigned to layer or program parameters do not. Thus, seeing an envelope under the Layer node does not by itself explain its behavior. UVI Falcon — Structure
Write down the complete assignment before editing: for example, “Layer envelope → layer filter cutoff” or “Layer envelope → keygroup filter cutoff.” That small inventory prevents changing the source while leaving the consequential destination untouched.
Is the problem triggering, assignment or audibility?
An envelope needs an active assignment before it changes the sound. Falcon provides assignment power controls, a modulation ratio and optional sub-modulation that changes that ratio. A disabled assignment or zero effective depth can resemble a trigger failure. UVI Falcon — Interface
Use this diagnostic sequence on a saved copy of the patch. Change one condition at a time so each result answers a specific question.
| Check | Action | What the result tells you |
|---|---|---|
| Basic playback | Play the intended notes with the suspect modulation disabled. | If the sound is missing, resolve playback before testing its contour. |
| Audible destination | Hold a note and move the destination manually. | If the movement produces no useful change, choose a clearer test target. |
| Active assignment | Enable the assignment and use a clearly nonzero ratio. | This removes an inactive connection as an explanation. |
| Destination scope | Identify whether the target belongs to a layer or keygroup. | This determines which retrigger behavior to expect. |
| Note pattern | Compare separated notes with overlapping notes. | This helps isolate overlap-dependent behavior. |
For the manual-movement test, listen for a specific change, such as a darker-to-brighter filter sweep. If that change is already difficult to hear, an envelope driving the same control is a poor diagnostic. Establish an obvious result before restoring subtle settings.
How do you restore a separate envelope response for each note?
For individual note articulation, test a destination inside the keygroup. You can keep the source organized on the layer while changing what it controls, subject to Falcon’s downward modulation hierarchy. UVI Falcon — Structure
The following is an illustrative filter test, not a report of a measured preset. Begin with a simple sound that sustains long enough to hear a one-second change.
- Add an Analog Filter to the keygroup effects and choose low-pass mode.
- While holding a note, move Cutoff manually until the difference is obvious. Analog Filter provides low-pass, high-pass and band-pass modes, with cutoff adjustable from 20 Hz to 20,000 Hz. UVI Falcon — Effects
- Right-click that keygroup filter’s Cutoff control, choose Add Modulation and select the existing layer envelope. Enable its assignment and set a useful positive ratio. UVI Falcon — Interface
- For an Analog ADSR test, use ADSR mode, an attack around one second, high sustain and a short release. These are illustrative settings intended to make the rise easy to hear. UVI Falcon — Modulators
- Play several separated notes, then hold one note while adding another. Compare their beginnings before restoring the original contour.
If this test works, reintroduce the original patch’s settings individually. Keep the working test assignment available until the intended destination behaves as required. That gives you a reference when a later change makes the movement disappear.
Why can Retrigger mode still appear ineffective?
Trigger mode describes how a modulator responds to an available trigger. It does not remove the destination-level condition described above. Changing a menu to Retrigger therefore cannot, by itself, establish note retriggering for a layer parameter. UVI Falcon — Structure
Falcon’s Multi Envelope offers Retrigger, Legato and No Retrigger modes. Retrigger restarts the contour on each trigger; Legato changes behavior for concurrent triggers; No Retrigger runs continuously with playback-related restarting. Analog ADSR offers Retrigger and Legato. Check the options documented for the particular module you are using. UVI Falcon — Modulators
Use two short listening passes. First, release every key between notes. Then repeat the phrase with deliberate overlaps. Record whether the contour restarts in each pass. A difference between those passes points toward trigger behavior; identical failure in both passes sends you back to assignment and destination checks.
For Multi Envelope, also inspect looping and release behavior. The manual documents a default loop and explains that release-loop settings determine whether note-off leaves it. Continuing after release is therefore a separate question from failing to restart at note-on. UVI Falcon — Modulators
What if you want one sweep across the entire layer?
Define the intended gesture before rebuilding the patch. Do you want every note to begin its own sweep, or do you want a single sweep across the combined sound? For the second task, decide whether a newly played note should restart that shared movement or join the movement already underway.
For a phrase-wide gesture, host automation is an available option: Falcon allows parameters to be assigned to host automation slots. For a shared Analog ADSR gesture, its manual Trigger button can be controlled through automation or modulation. These provide explicit control paths when ordinary note retriggering does not suit the destination. UVI Falcon — Interface, UVI Falcon — Modulators
Choose a repeatable test phrase before drawing automation: hold one note, add another halfway through, then release both. Decide what each event should do to the sweep. This makes the musical requirement concrete and avoids repeatedly adjusting envelope stages to solve an undefined triggering rule.
Does every synthesizer use the same layer rules?
Check the instrument’s own architecture. For example, Spectrasonics’ Omnisphere documentation describes dedicated polyphonic amplitude and filter envelopes for its layers, alongside four shared monophonic modulation envelopes per part. That terminology describes a different arrangement and cannot establish Falcon’s routing behavior. Spectrasonics — EDIT PAGE - Envelopes
For your finished Falcon patch, verify three things with the actual musical phrase: the intended notes sound, the contour starts when expected and overlapping notes behave as intended. Keep the working destination and trigger settings documented with the patch so the next edit begins from a known result.
