Feature Request Poll - Your input is needed - Results are online

Audio Connections overhaul or External FX Plugin w/flexible routing [RECORDING]


Improve Hardware Remote Plugin Control in Cubase

  1. Allow any MIDI device to be setup as a controller
  2. Replace Quick Controls with a system where users can map all plugin parameters to a controller
  3. Store controller mapping for those plugins automatically
  4. When a plugin window is active and a remote control assignment exists - that plugin is active for remote control - this would be “Plugin Control Mode”
  5. Create a “Host Control Mode” where users can easily assign hardware controls to DAW parameters and control those
  6. Allow users to combine controllers if desired (example: a synth has more parameters than a single controller - I use two different hardware controllers to control the single synth)
  7. Allow users to quickly map their MIDI devices by pressing a MIDI Learn button, and moving a controller - this will make setting up controllers a breeze

This will allow users to map as many knobs, faders, MIDI controllers as they have available to plugin parameters or Cubase itself and quickly switch between mappings/plugins just by changing the focus of the plugin window or between Plugin and Host Control Modes.

This sounds like fun but I’m way too drunk to understand it. Here goes!!!

Info line transpose algo FREE… which has no support!

External Synchronization per project not global. [OTHER]

Maybe this would be a place for an official Reddit Steinberg community page? Up voting there.

Save Folder Track Preset, saves all contained tracks+routings [Other/All]

Horizontal mouse wheel should scroll the mix console. [EDITING] https://www.steinberg.net/forums/viewtopic.php?f=285&t=157101&p=862553#p862553

The scroll bar is far too tiny to click and drag, so there is currently no way to scroll the mix console.

Eliminate mix console focus. [EDITING] https://www.steinberg.net/forums/viewtopic.php?f=285&t=162338

The concept of a channel focus separate from channel selection makes it too easy to act on the wrong channel.

Songwriting tool.

Notepad where you can add chords and lyrics etc.

Save mp3 export ID3 tag settings per project. [OTHER]

… and several more threads…

Multi quick control (assign multiple parameters to a single controller) [MIXING/OTHER??]


Ok. It’s a wrap. We got 50. Here is the poll:


Great initiative!

Also very good that the poll is so flexible in setting the points. But there should be a maximum number of points to assign to a single feature (maybe there is, havn’t tried?).

Many good features here, will need to think about the points… :slight_smile:

I’ll also take the opportunity to note this very useful request.
There’s no need to vote about it, as it could be implemented in just 5 minutes or so (just a tooltip update, add the change value too):

  • Tool Tip +/- When Changing Automation Values. [EDITING / MIXING]


  • Tooltips when you mouse over lanes in the Drum Editor and Expression Map.

  • The ability to colour/shade code the lanes in the Drum editor and Expression Map.

Whenever I use the drum editor, or the expression map, I always have to go through the time consume process of going to the left side of the editor window to see what instrument or articulation the lane is assigned to. Mousing over anywhere on the lanes with tool tips changing to reflect the assigned names would solve this situation. For me, now that ARA is added, if Cubase does this then it would be the perfect DAW.

FWIW, my votes…

Allow Free Warp On The Project Window			11
Automation saved with TrackVersions			 3
Bezier curves in midi editor				 3
Clarification of all the remote control features	17
Eliminate mix console focus				17
Gapless Audio Engine					11
Improve The "Save As Template" Function			 9
Rack presets						17
Ripple Edit						 9
Triplet/Dotted grid snap in audio editor		 3

Now, impatiently waiting for the global results… :sunglasses:

Done! However, my number 1 request isn’t there: more key commends. Especially Snap ON and Snap OFF. Toggle switches suck as I have to look for the minuscule snap icon 1,000 times every day! I’m sure I can’t be the only one.

Thanks for doing this Matthias! I think it’s important to prioritize some of the common user requests. It’s hard to gauge priorities based on people adding a +1 on a forum, and the idea of having a hundred points that can be assigned any which way is EXACTLY how to do it. I may want a few things, but I don’t rate those things equally. That’s where another competitor with a FR voting system fails; they weigh all votes equally.

I think when you look at the requests, there’s a bit of overlap (a few having to do with Remote Control or Control Surfaces, a few having to do with Smart Tools and Track Templates/Import Session Data) but I think a theme will clearly emerge when it comes time to do analysis on the results (e.g. “Remote Control needs an overhaul” or “we need to take a look at streamlining how users can reuse tracks and import them into new projects as templates”).

Anyway, my “big” items were:

Improved Remote Control for Plugins
Smart Tool
External FX overhaul

Then a few other things got the remaining points like:

Import Session Data
Move tracks in Mixer
Plugin Aliases
Tabbed plugin windows
Ripple Editing

I may have misunderstood: you want a Key Command for Snap On/Off? There is one. J (by default).


Cubase is missing a few Key Commands I’d like (for instance, I want to be able to assign key bindings to different sections of the Browser to switch from Effects to Instruments for example) but otherwise has a very comprehensive Key Binding system. It’s a strength, not a weakness IMO. Then again, it is weird when you find there isn’t one for something.

fyi, the one that is probably the single most popular request on this forum didn’t make it on to the list:

Get rid of the mouse wheel fader movement: https://www.steinberg.net/forums/viewtopic.php?f=285&t=148023

This shouldn’t even be a feature request. It should have been implemented when the new automation handling was introduced in CB 9.5.

What’s the point of being able to use the range tool to quickly create a volume automation range when you can’t see the values you are shifting up/down by. Still a two step process.

Hoping to see this added soon.