Known Issues
<p>Answering some known issues with Audio Modeling products and services</p>
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?
- Are My SWAM Instruments Vanishing from the Ambiente Room Simulator a Bug?
- SWAM VST2 plug-ins not recognized in Komplete Kontrol, Reason and Ableton Live (macOS)
- First note of a phrase randomly not played (v2.5.3 and Flutes v1.2.3)
- AAX/Mac validation failure for Cello v1.1.0 and Woodwinds 2.6.0
- FL Studio - "Buffer size too small" message
- AAX plugins v2.5.1 and The Flutes v1.2.2 not recognized in ProTools/Mac
- 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?
- Camelot Crashes a lot and the error messages don’t tell me exactly what the problem is.
- Sounds are taking a long time to load inside Camelot. Why?
- Everytime I try to run Camelot, I get a warning saying that I’m offline. How do I fix this?
- SWAM instruments are not appearing in my DAW on macOS. Why?
- Camelot shows me that the CPU is overloaded and it crackles and crashes. How can I fix this?
- My apps are not seen by Camelot. Why?
Experiencing CPU Issues When Running Multiple Instances of SWAM String Section. / Is My Computer Powerful Enough for SWAM String Sections?
v(1.0)
The realism and expressiveness of the SWAM String Sections instrument set come with a level of CPU intensity. As a result, it's essential to ensure that your computer meets certain requirements for optimal performance.
For a single instance of any section plugin in SWAM String Sections, you'll want a modern computer equipped with at least a 2.5 GHz 4-Core CPU. However, if you plan to run additional instances simultaneously, you'll need both a more powerful processor and a low-latency audio driver or device, such as ASIO. This is especially crucial if you intend to play the instrument in real-time.
While less powerful systems may still function adequately, they might necessitate the use of larger buffer sizes to handle the CPU load. However, this can lead to higher latencies, which could affect real-time performance.
It's important to note that the potential for CPU issues does not necessarily equate to an impediment for music production. There are effective workarounds that can help mitigate these challenges. Consider using the "freeze" feature available in some digital audio workstations (DAWs) or bouncing single MIDI tracks to audio. These methods can reduce the CPU load and help you maintain a smooth and efficient production workflow.
Furthermore, it's worth emphasizing that our products are continually evolving. We are committed to reducing CPU load and optimizing our instruments to make them more powerful, realistic, and efficient. Our technology has room for improvement, and we are dedicated to pushing the boundaries of what's possible. As we move forward, expect even greater enhancements and an even more efficient experience.
In summary, while SWAM String Sections offer exceptional realism and expressiveness, they do have specific CPU requirements, especially when running multiple instances. With the right hardware and some practical techniques, you can continue to create beautiful music without significant interruptions, and the future holds the promise of even greater improvements.
Other articles in this category
- 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.
- Are My SWAM Instruments Vanishing from the Ambiente Room Simulator a Bug?
- SWAM VST2 plug-ins not recognized in Komplete Kontrol, Reason and Ableton Live (macOS)
- First note of a phrase randomly not played (v2.5.3 and Flutes v1.2.3)
- AAX/Mac validation failure for Cello v1.1.0 and Woodwinds 2.6.0
- FL Studio - "Buffer size too small" message
- AAX plugins v2.5.1 and The Flutes v1.2.2 not recognized in ProTools/Mac
- 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?
- Camelot Crashes a lot and the error messages don’t tell me exactly what the problem is.
- Sounds are taking a long time to load inside Camelot. Why?
- Everytime I try to run Camelot, I get a warning saying that I’m offline. How do I fix this?
- SWAM instruments are not appearing in my DAW on macOS. Why?
- Camelot shows me that the CPU is overloaded and it crackles and crashes. How can I fix this?
- My apps are not seen by Camelot. Why?