Cubase 16 out now!

Thank you all for your feedback. While some of the reactions are certainly not what we had hoped for, I would like to provide a little more context on the thinking behind Cubase 16.

One of our main priorities for this release was to improve existing workflows rather than simply introduce more “shiny new things,” as some of you have called them.

I understand that a redesigned Settings dialog is probably the opposite of an “shiny new feature”. However, this was an important step, both from a technical and a usability perspective. The new search functionality alone makes it significantly easier to find and adjust settings, especially in an application as comprehensive as Cubase.

Tempo Detection is another good example. Improving it has been a frequent request from the community. We didn’t just introduce a new detection algorithm, but also redesigned the entire workflow to make the process faster, easier, and more intuitive.

And there are many more examples: renaming MIDI controller lanes, importing M4A files, additional sends and cue sends, easier setup of external instruments and effects, the UI overhaul of the Pool window, Strum and Stretch in the Key Editor, and Instrument Stacks. These are all improvements that address requests from our community and make everyday tasks easier for many users.

There are also smaller quality-of-life improvements that might not immediately catch your attention, such as assigning key commands directly from context menus, adding insert plug-ins via key commands, or removing bypassed and deactivated plug-ins from a project with just a few clicks.

Of course, we also want to continue innovating. The new spectral AudioWarp algorithms, developed in-house by our HALion team, are a good example of technology that we believe opens up exciting creative possibilities.

So, Cubase 16 is perhaps less about one big headline feature and more about the sum of many improvements across different areas of the application.

It’s also worth remembering that we develop several editions of Cubase for a very broad range of users, from beginners and songwriters to professional producers, engineers, and composers. A feature that might not be relevant to your personal workflow could make a significant difference to someone else’s.

None of this is meant to dismiss the criticism or suggest that there isn’t more work to do. We know there are still longstanding requests and areas where Cubase needs to improve. We take that feedback seriously, and it continues to influence our priorities.

Please keep sharing your feedback, and in particular, let us know which workflows you would like to see improved. Ideally, create a dedicated topic for your suggestion, or add your comments and votes to an existing one. This helps us better understand your priorities and identify areas where improvements would make the biggest difference.