Summary
I would like to request the ability for HALion to host third-party (and Steinberg) VST instruments as native layers inside a HALion Program, similar to how HALion currently layers its own sample-based and synthesis engines.
Background
HALion is already one of the most powerful software instruments available, combining multiple synthesis engines, sample playback, scripting, modulation, effects, and an extremely flexible layer architecture.
Modern productions and live performances often require several different virtual instruments. Today, this means loading multiple plugin instances inside the DAW, configuring MIDI routing, managing audio outputs, assigning effects, creating keyboard splits, and maintaining separate presets for every instrument.
Allowing HALion to host VST instruments directly would transform it into a true all-in-one performance and sound design environment.
Proposed Feature
Introduce a new layer type inside HALion:
- Sample Layer
- Synth Layer
- Drum Layer
- VST Instrument Layer (new)
This layer would allow users to load any installed VST3 instrument directly into a HALion Program.
The hosted instrument should behave like any other HALion layer and support features such as:
- Layer hierarchy
- Key ranges
- Velocity ranges
- Keyboard splits
- Layer stacking
- MIDI routing
- Layer enable/disable
- Integration into HALion’s mixer
- Audio routing through HALion’s insert and send effects
- Macro assignment where technically possible
- Preset saving as part of the HALion Program
Live Performance
This feature would be especially valuable for live keyboard players.
A complete stage setup could be contained inside a single HALion Program.
Example:
- Layer 1: HALion Acoustic Piano
- Layer 2: Padshop Pad
- Layer 3: Retrologue Lead
- Layer 4: Third-party Analog Synth
- Layer 5: Kontakt Strings
Instead of loading five separate plugins, the performer would only need one HALion instance.
This would simplify:
- Live setups
- Preset management
- Patch switching
- Plugin management
- CPU organization
- Backup and portability
Keyboard Splits and Zones
One of the biggest advantages would be the ability to create sophisticated keyboard splits and zones entirely inside HALion.
For example:
- C1–B2: Bass (third-party VST)
- C3–B4: Acoustic Piano (HALion)
- C5–B6: Synth Lead (Retrologue)
- C7–C8: Strings (Kontakt)
Everything would remain inside one HALion Program.
No complex DAW routing.
No multiple plugin tracks.
No complicated MIDI routing.
Just one preset containing the complete live keyboard setup.
This would make HALion an ideal central instrument for stage performances and greatly simplify working with hosts such as Steinberg VST Live, Cubase, or other VST-compatible applications.
Users could also combine keyboard zones with velocity ranges, enabling expressive performance presets where different instruments respond to different playing dynamics.
Sound Design
HALion already offers exceptional possibilities for sound design.
Adding hosted VST instruments would dramatically expand these possibilities.
For example, a single HALion Program could combine:
- Granular synthesis
- Wavetable synthesis
- FM synthesis
- Analog modeling
- Sample playback
- Third-party synthesizers
All under one preset with unified modulation and effects.
Unified Macro Controls
One of HALion’s greatest strengths is its Macro Page Designer.
If hosted VST parameters could be exposed to HALion’s macro system, users could build completely custom performance interfaces controlling several instruments simultaneously.
Example:
One Macro Knob could simultaneously:
- Open the filter of Retrologue
- Increase the reverb on a HALion layer
- Change the wavetable position of another synthesizer
- Raise the volume of a pad layer
This would create highly expressive performance controls that would otherwise require significant MIDI mapping.
Workflow Improvements
Hosting VST instruments inside HALion would significantly simplify many workflows.
Benefits include:
- One plugin instead of many
- One preset instead of multiple presets
- Easier backup
- Easier project portability
- Cleaner DAW projects
- Faster setup for live performances
- Simplified keyboard splits
- Unified sound management
Optional Enhancements
Possible future extensions could include:
- Plugin sandboxing
- Freeze/Bounce individual VST layers
- Multiple audio outputs
- MIDI filters per layer
- Automation mapping
- Parameter Learn
- Drag-and-drop assignment of VST parameters to HALion Macros
- Snapshot management
- Per-layer CPU monitoring
Benefits for Steinberg
This feature would further establish HALion as the central instrument platform within the Steinberg ecosystem.
It would be particularly attractive for:
- Live keyboard players
- Film composers
- Sound designers
- Electronic music producers
- Studio musicians
It would also encourage users to combine Steinberg instruments such as Retrologue, Padshop, Backbone, and HALion itself inside a single unified environment while remaining open to third-party VST developers.
Especially for users of Steinberg VST Live, this feature would provide enormous benefits by allowing complete performance setups—including layers, keyboard splits, and third-party instruments—to be managed from a single HALion instance.
Conclusion
HALion already provides one of the most advanced layering systems available in any software instrument.
Extending this concept to include hosted VST instruments would be a natural evolution of the platform.
It would simplify live performance, improve workflow, reduce project complexity, enable sophisticated keyboard splits and performance setups, and unlock entirely new creative possibilities for musicians and sound designers.
I believe this feature would make HALion not only one of the most powerful software instruments available, but also one of the most versatile VST-based performance environments on the market.
Thank you very much for considering this feature request.
