Swam solo strings
Here you will find everything related to the installation, activation, updates, release notes and manuals of our Virtual Instruments and Applications.
- Are you planning to create any Ensembles like Strings Ensembles and Brass Ensembles in the near future?
- Is it possible to control SWAM instruments using only note-on velocity?
- SWAM Solo Strings v3 main features improvements
- Warning! Expression controller non received
- Where can I find a free VST/Host?
- see all 7 articles >
Product & License Management
- Can I keep my SWAM instruments on an external drive?
- Can I use SWAM instruments without a physical MIDI controller?
- How do I create ensembles using SWAM instruments?
- Is there a way to access the reverb module to modify the default reverb type on SWAM instruments?
- SWAM with Camelot Pro (macOS / Windows)
- see all 11 articles >
- FL Studio - "Buffer size too small" message
- 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?
- SWAM instruments are not appearing in my DAW on macOS. Why?
- SWAM VST2 plug-ins not recognized in Komplete Kontrol, Reason and Ableton Live (macOS)
- see all 6 articles >
Sales, Billing, Offers
- 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?
- I’m not satisfied with the product. Is there a return policy?
- If I already bought a SWAM instrument, can I buy the other ones in the same family at a discounted price?
- What’s the price difference between the prices listed on your website and the price in other currencies?
SWAM VST2 plug-ins not recognized in Komplete Kontrol, Reason and Ableton Live (macOS)
Note: this article applies to discontinued SWAM Solo Woodwinds v2 and SWAM Solo Strings v2 products
SWAM VST2 plugins (Solo Woodwinds and Solo Strings) are not recognized in Komplete Kontrol, Reason, and Ableton Live on macOS.
The reason is that Komplete Kontrol, Reason, and Live are ignoring symlinks (e.g. aliases).
Our SWAM components have been made with a technique called “polymorphism”, i.e. a single component is an Audio Unit, VST, and AAX at the same time. The SWAM installer installs a single component in /Library/Audio/Plug-Ins/Components and uses a symbolic link (i.e. alias) to it for the VST plugin in /Library/Audio/Plug-Ins/VST. The VST plugin file is not a real VST component, but it refers to the component in the folder /Library/Audio/Plug-Ins/Components.
This technique is used by other plugin developers and vendors. Symlinks are currently supported by many popular DAWs.
To solve the issue, a manual procedure is needed. Please proceed this way:
- Go to [HD]/Library/Audio/Plug-Ins/VST and delete all "SWAM * 64bit.vst" files. Even if they seem like regular files, they are only Aliases (i.e. pointer to other files). They should have a little arrow on the icon.
- Go to [HD]/Library/Audio/Plug-Ins/Components and copy all "SWAM * 64bit.component" files (just copy, not paste).
- Go to [HD]/Library/Audio/Plug-Ins/VST again and paste the copied components there.
- Rename all the "SWAM * 64bit.component" (the ones you have just pasted) to "SWAM * 64bit.vst", for example: "SWAM Tenor Sax 64bit.component" -> "SWAM Tenor Sax 64bit.vst" (i.e. change the extension from .component to .vst). Be sure that the system does not automatically append the extension ".component" at the end (e.g. SWAM Tenor Sax 64bit.vst.component).
- Launch Komplete Kontrol / Reason / Live.
We are in touch with Native Instruments, Propellerhead, and Ableton support—we hope for a quick fix.
Note: in Ableton Live, there is no need to use VST2. Just activate the support of AU plugins.