SWAM Viola is an incredibly realistic, real-time controllable, expressive virtual viola. Developed by Audio Modeling using SWAM technology, it guarantees the same natural reactions as a real instrument.
SWAM Viola is instrument modeled with algorithms, recreating the behavior of the real acoustic instrument. There are no pre-recorded samples—that’s why there are endless expressive sound combinations you can achieve.
For example, assign the bow pressure to a knob of any MIDI controller, and create your own expressive music!
SWAM Technology overcomes the limitations that are typical of traditional samplers through a combination of innovative performance techniques and concepts of physical and behavioral modeling, with no samples required.
SWAM Viola only weighs a few Megabytes. As a producer, composer or live performer, you can use SWAM Viola for any musical genre by layering it in a sections with no artifacts and simply selecting different timbres for each instance.
All the following parameters are controllable in real-time (through MIDI) or by a Digital Audio Workstation:
SWAM Engine digitally handcrafted acoustic instruments are never a simple recording of notes via sample libraries, but rather a set of real virtual instruments based on their traditional counterparts. Our technology allows you to fully control the expression of any virtual acoustic instrument. You won’t need any Giga-sized pre-recorded library: the smallest footprint is enough to guarantee the perfect organic consistency resulting from the endless expressive parameters that are unique of every live performance.
These instruments exploit our proprietary SWAM-S engine, a powerful Physical Modeling technology derived from the Digital Waveguides approach.
AU, VST, VST3, AAX 64bit
10.7 – 10.14 (Mojave)
Windows 7, Windows 8, Windows 10
Required space after installation: 15 MB for two plugins
RAM occupancy: about 15 MB for each instrument instance
The realism and expressiveness of the SWAM instrument requires a computer with at least a 1.6 GHz Core 2 Duo CPU for running a single plugin instance. Less powerful systems may also prove satisfactory, but may require larger buffer sizes, involving higher latencies.