Version
You can control the amplitude envelope of the Wwise Synth One by adding an Output Level RTPC modified by a Modulator Envelope. The Modulator Envelope provides properties to modify the Attack, Decay, Sustain, Release (ADSR) in addition to Attack Curve, Sustain Time. You can also use the Modulator Envelope to stop playback with the envelope. Many of the properties of the Modulator can be randomized and modified by RTPC.
From the RTPC Tab for the magic_blast_synth_element, use the Selector to add the Output Level parameter which will be modified by a new Modulator Envelope ShareSet.
By default, the mode for the newly created Modulator Envelope is set to ShareSet.
Designer Note | |
---|---|
Envelope objects can be created as Custom or ShareSet. Custom objects are stored in-place, directly inside the object that has it. ShareSets are stored in a separate work-unit and can be re-used across objects. |
The minimum and maximum RTPC values of Modulator Envelope in the Sound Property Editor affect the base and top of the ADSR envelope (nil and peak values). Swapping the min and max values reverses the ADSR.
The properties available to the Modulator Envelope are:
Attack Time
Defines the time taken for initial run-up of level from nil to peak, beginning when the key is first pressed (in seconds).
Default value: 0.2
Attack Curve
Adjusts the Attack Curve from its linear default slope (50%) to either:
an exponential-style envelope (0%) where the rate of change starts slow and then increases
a logarithmic envelope (100%) where the rate of change starts fast, then decreases
Default value: 50
Decay Time
Defines the time taken for the subsequent run down from the attack level to the designated sustain level (in seconds).
Default value: 0.2
Sustain Level
Defines the level during the main sequence of the sound's duration, until the key is released (in percentage of the range).
Default value: 100
Release Time
Defines the time taken for the level to decay from the sustain level to zero after the key is released (in seconds).
Default value: 0.5
Scope
Controls how Envelopes are created:
Voice: An instance of an Envelopes is created for every voice of the synth when used in MIDI context.
Note/ Event: An instance of an Envelopes is created for every playing instance of the synth when used in MIDI context.
Default value: Note/Event
Trigger On
The actions/MIDI events that may trigger the envelope (that is, enter the attack phase):
Play: either a play action or a MIDI note event
Note-Off: only a MIDI note-off event
Default value: Play
Auto Release
Determines if the envelope requires an action/MIDI event to exit the sustain phase and enter the release phase. If set, the envelope exits the sustain phase after Sustain Time. If not set, the envelope exits the sustain phase following a certain condition:
The envelope may be released by the game via a Release Envelope event.
An envelope may also enter the release phase via a MIDI note-off event, provided the envelope was triggered by a MIDI note-on event.
Default value: False
Sustain Time
Defines the time which the envelope will remain in Sustain before the Release is applied (in seconds).
Default value: 0
Stop Playback After Release
If set, the playback of the associated sound is terminated after the release phase is complete.
Default value: false
Modulator Envelope Properties can be accessed using the Modulator Editor:
Designer Note | |
---|---|
Additional information for working with Envelopes can be found in the Wwise Help Document: Wwise Help > Interacting with the Game > Working with RTPCs > Working with Envelopes |
The combined power of synthesis, modulation, and parameterization is at its best when used in conjunction with the dynamics of gameplay. With so many options to modify and affect the properties of sound within the project, it is important to understand the impact these can have on your platform's memory and CPU performance.
A modulator's processing time depends on its RTPC usage. For most properties, a modulator is evaluated once per audio sample. However, for the property voice volume, the associated modulator is evaluated at every frame. Use modulators selectively as they can consume a significant amount of a platform's memory and CPU. Always work within the constraints of your target platform.
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageRegister your project and we'll help you get started with no strings attached!
Get started with Wwise