I know Cubase 16 just came out, but it seems plenty are disappointed (me included), its become like a subscription really, we don’t even know if bugs from v16 and earlier are resolved!
Perhaps some of these (or most of) can be added to v17, feel free to add your ideas:
Media bay update, to be more like Loopcloud or Luke Bond Hypercrate, ideally the option to add as an insert with it’s own audio channel so that FX can be applied when auditioning loops to see how they fit the project. Of course, with the usual ability to lock down tempo, time stretch to fit project bpm, filter key (transpose if necessary) and similar loops based on rhythm or instruments. I don’t think anyone would mind if local “AI” is utilised in making this experience better! To be also able to do some basics edit, like chopping it up, then dragging the desired loop/sample into an audio track.
Flexible and a more advanced MIDI editor/Piano roll, check out MIDISketch for inspiration, this takes MIDI editing to a whole new level!
CPR project file inspector, Dom Sigalas has released a very good looking inspector (Mac only for now which is a shame), this or something similar should be part of Cubase (albeit can be launched separately as a tool if need be), if Dom can do it (no doubt vibe coded) then it’s embarrassing that Steinberg have not done so in all this time!
Rename or create aliases for plugins
Utilise GPU for some processing (like MediaBay processing, stem separation etc) if available on the users computers. I have an Nvidia GPU, amazing how much faster stem separation is with it than using the CPU alone!
Better CPU core utilisation, this is from others, not had the issue with my AMD 5950X, can handle it like a champ with my projects but lots of complaints, and since the silly price increases for computer parts, we may be stuck for some time with our computers, so need to squeeze as much out of them as we can!
Better information for crashes, maybe a built-in utility explaining exactly why it’s crashed instead of reading the dump file/crash logs which is cumbersome, and some will not realistically understand. Which plugin caused it, maybe offer a sandbox plugins feature to avoid a repeat?
Rename lanes (incredible this wasn’t a feature right from the introduction of lanes!)
Please add other requests, no idea how Steinberg decide, but hopefully they even do a poll to decide on the next 10-20 big features as requested by the users! No need to be secretive about what’s coming!
Thanks
I’d like to see attention shifted to the comping process. It works well enough, but for example, it’d be great to be able to give comps grades, without having to mess around with the somewhat onerous to use (in my hands) coloring process,
That’s just one idea … I leave it to the creative programmers with vision to blow my mind … please!
been asking for this for years now. I would’ve much rather had a redesigned mediabay than the audio pool or settings menu, given that I need to use mediabay with much greater frequency. I wish I could separate loops from one-shots and it was just generally easier to search.
Another great UI reference is XO by XLN audio, where you can think about samples in musical space and make surprising connections you normally wouldn’t when looking at a spreadsheet (which is basically what mediabay feels like)
The old Audio Pool and Preferences menu, along with some loading dialogs, were the last parts of Cubase built on the original GUI framework. Everything else had already moved to newer style dialogs, presumably in a newer framework. I’m sure they had to keep lots of old code around that was responsible for rendering and handling those old dialogs that now can hopefully be excised. Cleaning up the code base of ancient artefacts is good for all of us.
Don’t get me wrong, I’m not complaining they refined those. I welcome the changes. I just think for a major version paid update, Mediabay needs an overhaul and is something I use 99% more often in my day.
Updated note expression with a snap to center on next note feature. This is great for drawing pitch and cc changes but it’s currently a bit clunky.
Media Bay - I would love to see user created favorite folders and ability to right click sounds and alias them to the favorite. If it come across a sound I like then “Add to Fav Snares” or “add to fav risers.”
To my way of thinking, the MediaBay, and/or Audio Pool, need to be connected to the cloud so that limited file synchronisation can take place, that is audio files in the very least.
I don’t really use the MediaBay, so what would you propose, here?
I am thinking implementation of something more akin to a cloud-based sound library, Steinberg could involve 3rd parties in this, with sound effects, one-shot samples and so on but with a built-in sample player and editor.
From business perspective, Steinberg needs to serve new beginner customers as well as advanced professionals. I would advice them to expand their already existing tools in Cubase 17 to be even more beginner friendly.
Tools that would lead people to embrace more music theory and song writing theory while producing in Cubase. No need for resource heavy AI agents or engines. If anything AI should serve to build knowledge not laziness IMO.
For example expand existing tools to learn cadences, rhythm subdivision (regular and irregular groups), show intervals filter in melody, more lyrics functions, add theory examples in new help window.
These can all be easily implemented in Key Editor as filters and new features. In HALion Sonic you could add a new “learning” tab with simple music theory analysis from suggested chord pads, bigger keyboard so people can actually see chord construction from those chord pads.
Also dedicated “Composer Tools” functions on RMB in Key Editor with melody functions from selection (reverse, mirror, inversion, transposed inversion, retrograde, .. )
The Grand 3 GUI could be expanded for practical rhythm practice, accompaniment patterns, left right hand dexterity (the biggest pain of any beginner) on piano, simple music theory examples.
In short make people ACTUALLY play in your “playground”. Find customers REAL pain and offer a solid solution for this pain and people will all flock to Cubase.
Any AI assisted workflows, would need to hook into the application, so we are likely to see API access first, and unless that takes place, any talk of AI interacting with the program, is premature.
No, but thanks, will do. I still think Steinberg should be offering a built in solution, I know most of the times it’s plugins causing them, but sandboxing plugins should also be considered.
Why not combine the Pool and the Media bay? Put project files at the top of the mediabay into its own section when a project is open.
Get rid of loop and sound browser.
Turn it into something like @SoundOf mentioned. Hypercrate looks nice, but there are some really good media/sound/audio management tools out there now.
Something like Atlas or waves Cosmos for managing or browsing samples in a more intuitive way. Something that can insta create a random kit for the drum machine based on what you feed it.