I love Cubase and love this forum but find it inefficient to collect feature requests properly ! Steinberg looking at this?
Also many requests here should perhaps be in a Cubase 14 UPDATE as opposed to a future C15 version.
And in a good system Steinberg would filter, what is implemented goes down, what isn’t gets moved to C15 wishlist.
My 2 cents. I love using Cubase and wish for some ironing and workflow enhancements MUCH MORE than for new plugins !!
I don’t think I saw this, but being able to rename the inserted plugins from their defaults.
So, when adding a UAD Compressor, we could overwrite that name with “light compressor” or something more meaningful. If you change that Plugin then that name would go away.
If you read the UAD Compressor, then the insert would say “UAD compressor” until or if you decide to enter in your own name.
Also, show missing inserted plugins with a different colour in the inserts than the standard inserted plugins to help when dealing with old projects.
I´m with you. That would be really nice. But…
What if you add an EQ before the Compressor - should Cubase rename the FX according to the first insert slot that has changed now? Or keep the name as long as the first insert is not removed from the chain? What if you know from the start that you´ll need the EQ to be the first in the chain and your FX is wrongly named after that EQ?
It IS annoying to rename the FX track after checking out different options, no doubt. Just saying, it´s tricky to come up with consistent rules…
I honestly think this should be #1:
VST2 support
Please copy the list and add your feature requests at the bottom.
Sandbox plugins to prevent crashes.
Option to place the cursor on clicked point on event.
Option to choose all algorithms for VariAudio.
Summing folders
Audio interface attached to project, not to Cubase itself.
Save and restore ALL audio connections with one click
Set meters as VU meters (Logic)
Clip launcher
Support for CLAP (plugin format)
Automate last touched parameter.
Lyric track.
Global display zoom (similar to Ableton).
Minimize the risk of user preferences getting corrupted
Update expression maps
Rewrite VCA faders to have them function like proper VCA (and without bugs)
Implement an optional scroll lock on the upper track list when the track list is divided
Do not automatically add newly created channels to existing channel visibility configurations
Introduce a selection mem/zap (similar to zoom mem/zap) that stores and recalls selected tracks/channels/parts/events
Reconsider the graphical design of the mix console
Unlimited inserts and sends
Channel EQ with 8 filters.
Gate plugin with threshold lower than 60dB (synths have noise below that and its nice to hear full reverb tail).
Modulators controls to module other modulators.
Plugin Chainer: Merge effects. (eg. Merge synths or effects like Waves StudioVerse)
Folder/ Group track merged into one.
Expression Maps overhaul. (including per articulation negative track delay).
Add expression map controls in the Logical Editor.
Digital Performer Chunks for larger film scoring projects.
Further/advanced Dorico Integration.
Muted events with a darker shade of the current color rather than white.
Combine multiple instruments into one rack and one midi and to have modulators control any parameter of any synth instrument in that rack.
Multiband splits and parallel splits.
Always on top.
VU meter on tracks (similar to 10)
Nameable CCs
Option to disable Video Engine “enhancements”.
Left-click the title bar of the inspector for drop down color menu rather than Alt-Click.
Remove default automation parameters and have users choose their own.
Preset list: Select preset using up and down arrow keys
Using Tab to select the next instrument in the instrument list (Can apply to other dropdown items as well).
Multi-sequences each with independent tempo, time sig and video track, housed under one project file, like Digital Performer’s ‘Chunks’ feature.
Fixed height for folder tracks
Ableton style plugin containers with routing options for Parallel/multiband processing on one track.
Pitch automation for audio clips.
Have an undo function for VST instruments.
Global undo/redo controls (not separate for mix console).
Add global modulators that can control parameters on different tracks.
Implement modulation assignment similar to Bitwig, where you can drag up or down to simultaneously set the modulation amount.
Make the modulation amount easier to control instead of a tiny bar.
Make ‘hide all automation’ behave the same as ‘hide automation’ but for all tracks, instead of reseting all automation visibility when reopened
Allow volume automation to ‘detach’ from fader, without having to automate a separate volume plugin
Always show parameter values, not just on hover.
Allow sample track to export slices to drum machine track.
Have automatic tail detection for bounces and Offline Processing, that extend the bounce range automatically.
Tightly integrated Hardware Midi Controller.
Full and proper Ripple Edit
Gain Reduction meters in Channel meters
Plugin Renaming (Similar to Studio One)
Missing plugins can be highlighted with a different color
Addition of a MIDI input transformer on every control in MIDI remote.
Addition of controller conditions (if mixer open and full screen, the midi remote controller activate the mixing page. If this instrument open, the controller reacts this way, control these parameters)
Double-click on volume faders/parameters to do something, input a valor, or reset to 0.
VST 2 Support
Fix problems in Direct Offline Processing like not always generating a tail
Fix the Dialogue tabbing misbehavior\
Fix flatten real time processing which mess up timing no matter the algorithm used.
Fix VCA channel losing its values upon reopening of project.
Fix the bugs in MIDI Remote
Fix batch flatten processing on multiple events which results in pops and whole parts broken.
GUI consistency across all menus. (media bay, media pool, preferences)
Legible text everywhere
I’d love to be able to rename VST3 plugins in the plugin manager. Some companies give silly long names to their synths. I would love to keep things clean and tidy.
I don’t think it would be that complex.
You enter your name, hit return. That is the name of that particular instance of that particular plugin. If you drag that plugin instance up or down, the name stays the same, just in the location you drag it to.
If you delete that plugin and then re-add it, anywhere in the channel inserts, you get the default name of the plugin.
I’d love be be able to rename the synth itself in my list of plugins, so i don’t have to do it every time, when open an instance. It’s a feature that has been requested for quite a long time now.
Fix the freaking scroll issues on Mac version of Cubase !!!
It would be more effective, if there was some sort of poll or voting feature on the forums. Not on the whole topic but on individual features presented. Each user could have X amount of votes (let’s say 5), and if they changed their minds they could switch their votes around.
And the main topic could also be malleable, enabling the topic creator to assimilate suggestions from other users, to be voted on.
And Steinberg could easily discern, which features are the most requested ones, not be overwhelmed by a myriad of new feature requests, but primarily focusing on developing the most requested ones.
This could also be used to address the most annoying bugs, as well. The most voted-on bugs should take on the first priority in being fixed. And when those bugs are fixed, they could be crossed off the list or marked as “fixed”, making room for other urgent bugs on the priority list.
The more votes a feature or a bug gets, the higher it climbs to the top of the most important/urgent to-do list. This way Steinberg could get an easier overview of what’s urgent, what’s important, etc.
Win-win for everyone, I’d say.
Yes, it could be a good habit to develop on Steinberg’s side to distinguish between what’s broken and has to be fixed as a current version patch, as opposed to a new feature that is reserved for the new, paid update.
Agreed, but only on the condition that new workflow enhancements don’t erase old ones. If a new workflow enhancement is introduced that conflicts with the old one, there should be a setting or a preference to choose between those.
And the same principle should apply to things like interface customization or enhancements. They should never permanently remove old things that people have gotten used to in favor of new implementations. Always leave an option or a setting to let people choose between them.
+1 for this! Negative articulation delay would be HUGE. That would seriously cut down the number of needed tracks. Was really hoping for it in C14. Sigh.
(Deleted by User)
How about, I don’t know, a program that actually effing works? How about that?
Please don’t make this type of empty comment on the internet.
I hope you realise Cubase works very well for most people.
If you have an issue, raise it properly with info and system details.
Good luck and best wishes.
screen estate GUI idea :
with one top left button in any window I could get a crossmark and once I draw a rectangle and release, that window would be cropped to that area ! Only one button at the top left to switch back to full view, back and forth with cropped view.
I just made a post for this but I don’t think you can do it, so I’ll add it as a wishlist.
Be able to control a modulator with a CC sent from a controller keyboard knob or slider.
Yes - you can modulate that from another modulator. I can, anyways.
Page 992 of the manual: “…A modulator can also modulate the parameters of another modulator…”
What I can’t do is modulate the modulators from a knob or slider with a CC from a controller keyboard.
If that can be done, I haven’t found it yet. The modulator needs a ‘midi learn’ for itself, as well as for other external parameters.
There might be some kind of workaround - maybe?
I tried to assign another LFO to this parameter but ‘Learn’ seems to ignore it in my case. Not a biggie. At least it works for you 
-bussed folders
-clip launcher
-improved chord pads