String Sections
Here you will find everything related to the installation, activation, updates, release notes and manuals of our Virtual Instruments and Applications.
General Information
Product & License Management
How To...
- I Don't Hear a Difference When Adjusting the "Players Accuracy" Parameter... Is It Not Working?
- Why Are There Few Presets for the Strings Sections?
- Can I Use the Room Simulator for SWAM Solo Instruments?
- Can I Reuse a MIDI Preset Created with SWAM Solo Instruments?
- I Can't Achieve a "Scratch" Sound Effect Like in Solo Instruments, Is That Correct? / Increasing Bow Pressure Doesn't Produce a Scratch Sound Like in Solo Instruments.
- see all 10 articles >
Grow Your Knowledge
Compatibility
Known Issues
- Ensure the Divisi Number Is Different When Adding Multiple Sections of the Same Instruments Playing at Unison
- Why Do I Sometimes Hear Portamento, Especially in Fast Runs? / How to Control and Limit Portamento in SWAM String Sections.
- Experiencing CPU Issues When Running Multiple Instances of SWAM String Section. / Is My Computer Powerful Enough for SWAM String Sections?
Why Do I Need to Accept/Give Permissions for "Incoming Network" After Installation?
v(1.0)
The instances of SWAM String Sections communicate with each other using the Open Sound Control (OSC) protocol. To achieve synchronization and enable various functionalities, it's necessary to accept incoming network connections.
By allowing these incoming network connections, SWAM String Sections can identify the presence of other sections in the virtual room, position them accordingly, implement essential automations like anti-phasing, and provide centralized control from a single instance. This enables a seamless and optimized orchestral experience and ensures that all sections work harmoniously together.
Accepting these permissions is a crucial part of ensuring that SWAM String Sections function effectively and that you can harness their full potential for your musical compositions.