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.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article