Q&A with Key Developer Alexander Gross

What makes Cubasis 3 stand out from other music production apps?
Packing features and content for a specific musical style into an app is one thing. Designing a multi-tool that meets expectations of musicians coming from many different musical styles, while making all features accessible from the get-go with an intuitive user interface, that’s what we aim for with Cubasis 3.

How will users notice the performance improvements in Cubasis 3.2?
iOS musicians who make use of Audio Unit plug-ins will notice that Cubasis 3.2 is able to process a lot more of them without running into performance issues. As a side-effect, this greatly improves the stability of complex projects. On top of that, all users will notice that the DSP usage of most projects has dropped quite a bit, especially on devices with many CPU cores.

What are the challenges of making Cubasis available for both iOS and Android?
The number of supported devices goes up from around 30 (iOS) to almost 2,800, so we had to pick a few dozen popular Android devices for development and quality assurance. We had to improve the UI layout due to the increased range of possible screen sizes and learn about the peculiarities of some manufacturer’s modifications of the Android OS. The biggest challenge however is the way iOS and Android handle low-level audio and performance-critical code differently. All in all, we do our best to keep the user experience as similar as possible on both platforms.