WHAT’S NEW / RELEASE INFORMATIONS
RELEASE 1.0.9

1. A dedicated LFO keep control of the new vibrato funtion, assignable to
aftertouch via Users Settings page: the oscillator modulates the basic
pitch of all Alieno sound generators and affects Strums detune value too,
slightly increasing when a strong key pressure is detected. That all gives
more life to the overall sound and will surely give more expression to your
leads and bass lines.

2. New intelligent randomize function: produces a random patch (high quality
algorhythm from double-triangular distribution) for the single generator
you’re operating on, leaving untouched settings of other modules.
To perform a randomization: for the Strums, use the new violet eye-button; for
the Core, click on machine’s name.
Both will activate a dropdown menu that features also a reset function to
recall a useful basic setting for the module.

3. Re-coding of many elements under the hood: envelopes, Warp effect, Lumilux
filter, Strums & Core voicing: that all ends up in better CPU performance,
particularly on slower computers.

4. User settings expanded to allow more customization, including a new
ship style (upper & lower cockpit skin) and new GUI animated effects, notable
when User applies on pitchbend or aftertouch vibrato.
Some other new functions includes the ability to choose between legato and
retriggered note-stealing system, aside the old velocity on volume, oscilloscope
and oversampling on/off options.
Note: In off-line mode (read: when rendering to audio) oversampling is automatically
activated and the oscilloscope bypassed, for maximum quality and minimum idle-times.

5. A new User controls section allows to select and browse through two
different MIDI CC#s maps to access most of Alieno parameters from user’s
remote hardware controller, there’s a GM compatible mapping and a M-Audio
Oxygen8 compatible map.
The Map section of the page allows to monitor the assigned CC#s with
a dedicated mini-browser.
User settings and user controls data are now stored in two separate .txt
files, located in the same folder where the plugin resides. These files are generated
from the plugin itself whenever the User make some changes and
automatically recalled at each load.