Interface Functionality Issues And Feedback

Hello,

Sorry for the long post. I have compiled a laundry list of issues with Cubase’s interface functionality that I have noticed over the years. Other users have already pointed out graphical issues with the interface, the following issues and feedback focus more on interface functionality and consistency:

  1. Many parameters can’t be adjusted on multiple tracks at a time (track delays, drum and expression map assignments, MIDI sends assignments, link group assignments, ASIO latency compensation, type of newly created events, etc.) or on multiple entries at a time in many windows (generic remotes, expression and drum maps, etc.).

  2. Many important windows lack a search function (expression and drum map editors, generic remote, macros in the key command window, etc.).

  3. Inability to reorder entries in many windows (logical editor, generic remotes, expression and drum maps, etc.), or only possible to reorder them one at a time (drum map assignments), or by clicking a button (macro commands, workspace organizer, etc.) or opening a menu (visibility configurations, tool bar, info line, etc.) instead of via direct drag and drop.

  4. Can’t assign inputs/outputs incrementally on multiple tracks (used to be possible, no longer working on my system).

  5. Can’t save most presets, need to “save as” every time (logical editor, keys commands, etc.). This increases the risk of accidentally overwriting the wrong preset.

  6. Can’t delete or rename presets directly from certain preset menus (track inserts, track presets, etc.).

  7. Can’t resize important sections of certain windows (output section of the expression maps window).

  8. Can’t resize columns in certain windows (key commands window) or automatically resize columns to fit the largest element in the column by double clicking (logical editor, drum map editor, etc.).

  9. Ignoring important conventions for no good reason (inverted horizontal scrolling).

  10. Using custom symbols for conventional functions (control room activation button - I discovered this feature by accidentally clicking on it. I would’ve been aware of its existence immediately if it had a conventional symbol like the tempo track activation symbol).

  11. Scroll bar covering important functions (inspector).

  12. Parts of menus appearing outside of the screen (MIDI channel menus).

  13. Inability to disable mouse wheel parameter adjustment globally causing accidental modification of important parameters.

  14. Can adjust some parameters by clicking and dragging (track volume, panning, delay, etc.) but not others (many info line parameters like time signature, marker ID, etc.).

  15. Can select an item by releasing the mouse in some pop-up menus (audio track extensions, new MIDI part type, insert retrospective recording, drum map, etc.) but not others (track routing, MIDI channel, expression map, etc.).

  16. Mouse click is ignored when clicking outside a pop-up window to close it for some windows (routing, plugin selection, etc.) but not others (MIDI and audio record modes, set up window layout, configure meter settings in control room, etc.). This forces the user to always click in a neutral area.

  17. Can type in the search field immediately after opening certain pop-up windows (track search, track inserts), but not others (inspector track routing, logical editor presets, etc). This issue causes accidental edits.

  18. Cubase doesn’t remember many window positions forcing the user to adjust them each time (inserts preset management window, metronome setup, profile manager, project synchronization setup, etc.).

  19. Clicking on certain window toggle buttons when the window is opened doesn’t close it (track search, setup window layout, expression map setup, process tempo on tempo track, etc).

  20. Positioning elements in different areas of differently windows for no apparent reason (presets at the bottom left in the preferences and at the top right in the key commands).

  21. Permanent elements positioned below optional elements in a menu causing them to be pushed to the bottom when optional elements are added (controller menu in the MIDI editors).

  22. User needs to Ctrl + click a soloed track twice to solo it exclusively.

  23. Opening the drum or expression map editors directly from a track opens the first map in the list instead of opening the one already assigned to the track. I often spend more time scrolling to find the right map than I do making the adjustment and sometimes accidentally edit the wrong map.

The lack of basic functionality, inconsistency and poor design are costing users a lot of time and money. None of these issues are a big deal individually but collectively add up to become a major problem.

It’s very important to reduce the number of steps needed to perform an action as much as possible because many a mickle makes a muckle. A famous composer once told Greg Ondo: “Every click costs me a dollar”. Eliminating a single step can make a massive difference (last issue for example). Most important are making sure that every single action which can be performed on a single item can also be done on multiple items at a time, and a good implementation of all the basic functions like search, move, resize, delete, rename and save (not just “save as” which increases the risk of overwriting the wrong preset) throughout the entire program.

Consistency is extremely important as well because it’s impossible to develop a fast and reliable workflow in such a complex program without perfectly predictable behavior. A single inconsistency can greatly impede workflow. If the user clicks on a pop-up search menu and immediately starts typing, they need to know for sure that the search field is activated so they won’t cause accidental edits. So if a decision is made to position the preset menu at the top right of windows, or to select a menu item by releasing the mouse, or to use a specific activation icon for example, it’s better to commit to that decision and implement it throughout the entire program immediately, than to treat each section independently or wait for a specific section of the program to get an update 10 years down the road before making the change. Otherwise, you will inevitably end up with a really inconsistent program and the laundry list of issues above. It’s important to be consistent with other programs as well (horizontal scrolling for example), unless you have a good reason not to.

Steinberg’s interface functionality standards are seriously inadequate and the current rate of improvement in this area is way too slow. Something as basic as being able to move items is being treated as a luxury rather than a necessity (the ability to move tracks in the mixer was just added in version 14) and consistency doesn’t seem to figure at all in the development process (for this area). Even windows which have been recently updated still lack basic functionality (can’t reorder lanes in the logical editor, no macro search function in the key commands window). A preference to disable mouse wheel parameter change was recently added but only for the top section of the mix console (with no indication that it affects only the top section), no preference for the bottom section and no global preference were added. It’s very frustrating that even when these types of issues are finally addressed, we often end up with a half-baked solution.

Basic interface functionality and consistency should be considered a top priority. Adding new plugins like a shimmer reverb or a tube compressor seems to be deemed more important even though we already have great third-party options to fill those needs (including free options). On the other hand, we have no way of solving most of the issues above using third party tools like AutoHotkey (we shouldn’t have to even if we could).

3 Likes

A lot of things to be tested in depth, on my end, to confirm what’s in your list. Beside this, are you using a MacOS setup or a Windows one ?

But, and as a Windows 10 user, I have recognized already a lot of its items, especially the ones related to the presets management and dialog windows behavior. Steinberg rightly made the general windows management to be more compliant to the Windows standard (don’t know if it’s also true for the MacOS one) : I think it’s time to do the same thing for the Windows interface components (menus, behavior of the Tab and Esc keys, dropdown lists content display, etc. ).

This, with fixes to the strange behavior of some windows, the Color Picker one being the first that comes to mind, even if it seems that work has been done, lately, to make it more functional.

So, I can just acknowledge your post as, indeed, there are a lot of fixes to be made concerning the UI consistency and sadly, the improvements are indeed too slow to come.

OTOH, and it’s the main problem, I think : we have to keep in mind that only very few new users will come simply for a consistent UI, when actual sales are involved. Features will always gain more traction… :neutral_face:

Oh, they must be on Windows. Otherwise they would not complain about inverted horizontal scrolling.

I overlooked this little detail… :grin:

I have this problem on Mac and not on PC

Yes, Cubase would need to take one full new version just for the interface and QOL improvements. I don’t have hope that this will ever happen.

Cubase gives that feeling of a “20 years old software with no old devs left and new ones are left with no documentation” - a problem that is much too common these days.

1 Like