Swam solo strings
Here you will find everything related to the installation, activation, updates, release notes and manuals of our Virtual Instruments and Applications.
Product & License Management
- SWAM VST2 plug-ins not recognized in Komplete Kontrol, Reason and Ableton Live (macOS)
- FL Studio - "Buffer size too small" message
- Windows 10 update 1511 invalidates SWAM authorization
- My SWAM plug-ins are not found by Ableton Live on macOS. Why?
- My SWAM VST2 plug-ins are not showing up in Cubase. Why?
- see all 6 articles >
Sales, Billing, Offers
- Why SWAM iPad and Desktop Versions are Separate Purchases
- I already own one or more SWAM Solo Strings v2 instruments. How does your new release promotion for SWAM Solo Strings v3.0 apply in my case?
- What’s the price difference between the prices listed on your website and the price in other currencies?
- I’m not satisfied with the product. Is there a return policy?
- If I already bought a SWAM instrument (desktop version), can I buy the other ones in the same family at a discounted price?
How many SWAM instances can I run at the same time?
Because SWAM instruments use physical modeling technology, they are more CPU intensive than regular plug-ins. It’s possible to run more than one instance of a SWAM instrument at a time, but depending on how powerful your system is, you might run into issues like unexpected dropouts or latency.
The best way to proceed if you’re limited by your CPU’s power is to render each track containing a SWAM instance separately as an audio file before moving on to work on the next one. This way, you’re always working only with a single instance of a SWAM instrument open at a time.