Navigating Editor Windows

So I like to work with my editors on a second monitor. It seems like there should be a command for simply “open editor” that gets Cubase to jump to the proper editor window based on the selected content (audio > sample editor, midi [no drum map] > key editor, midi [drum map] > drum editor, pattern > pattern editor).

There is a command called “open/close editor” that is close but even though I have the “Use Drum Editor when Drum Map is assigned” checked in the preferences, it opens to the Key Editor every time if a midi event is selected regardless of whether a drum map is loaded. Also, this command isn’t ideal because it closes the window if it happens to already be open, which is user error I know but something I am definitely prone to do.

Can anyone think of a work around? I’m fairly comfortable using Keyboard Maestro too if that helps

Maybe I’m misunderstanding what you’re looking for–but by default, when I select an event and hit “Return”, it opens the Key Editor if it’s MIDI, the Pattern Editor if it’s a pattern, the Drum Editor if it’s got a drum map assigned, and the Sample Editor if it’s an audio event. That doesn’t work for you? Did you possibly modify the key command?

@XLColdJ Thanks for the reply. I tested this by saving my presets and resetting to Defaults. By default the Return key is set to “open/close editor” I’ve experimented with this command in the past and retested a bit this morning and it’s very close to what I want it to do, if you have the windows open the in full screen or on separate desktops (if not the windows just kind of pile on top of one another into a mess)

The only thing that doesn’t seem to work is opening midi parts with and without drum maps loaded. The first time I open the window it does register this correctly. Midi events with drum parts open the drum editor window, and those without open the key editor window.

However after this, I’m never taken to the drum editor window once the windows are open. If they are open and I press the “open/close editor” command, I’m always taken to the key editor window regardless of whether the track has a drum map loaded or not.

Am I doing something wrong? I have double checked (triple checked) that I have the “Use Drum Editor when Drum Map is assigned” but I still get this behavior. Can anyone confirm this? And if this is intended behavior what is the logic behind it?

What is on your 1st monitor? The Arrange Page? If the Arrange Page is open, can’t you simply double click on a Instrument Track Part to get the Key Editor to open or double click on a Instrument Track Part (with the drum map assigned) to get the Drum Editor open in the 2nd monitor?

Your objective is to keep all 3 editors, the Key Editor, Drum Editor, and Sample Editor open on the 2nd monitor? (Since in full screen on the 2nd monitor they are on top of each other. You can only see the focused editor)

What presets are you saving? Are you referring to Preferences to default?

Also since “full screen” with Mac behavior is different than the Windows Maximize function it might help if you state your OS?

I use 4 displays and unless I’m misunderstanding your objectives, this should be very straight forward.

@Greg_Purkey Thanks for the reply. My first monitor is on the arrange page yes. I then have all of my editor windows (drum, key, sampler, pattern) open in full screen on a second monitor. When I double click on any of the regions it takes me to the proper window in the second monitor, with the exception of midi tracks with drum maps loaded. These still take me to the key editor, regardless of whether I get there by double clicking on the event OR by using the “open/close editor” command.

Perhaps its an issue of how I’m loading the drum maps? Or something to do with the Visibility Tab? Again the first time I double click on a midi event of track with a drum map loaded, I’m taken to the drum editor so it seems like CB knows there’s a drum map loaded. But after that, every time it takes me to the key editor…?

Again thanks everyone for taking the time to read and consider the post.

Cheers

*I have “open/close editor” set to a custom key but until I have my workflow for navigating windows figured out it’s gonna be hard for me to commit to a particular key. As of right now it’s on the ⇧W key but I don’t think any of this should have an effect on this issue.

**For some reason the inherent MacOS command for putting windows into Full Screen mode does not work for Cubase. And since Cubase have not provided a command for this internally, it only works via mouse click which I’ve set to a click on image command in Keyboard Maestro. It’s quite fragile though. Regardless of whether I have the each of the editor windows in full screen, or each set to fill the screen (window maximize?) on it’s own desktop the behavior is the same. Not sure how much of this information is relevant to the situation at hand but here it is anyway…haha.

I did a test, and yes, I couldn’t get the drum editor back as intended because the drum editor, with the proper drum hits shows up as a Key Editor even though in the Inspector, you have a drum map installed. I wonder if this behavior changed when new features were added to the Key Editor a few versions back?

I don’t think it matters about doing this on a 2nd display. I tested this all on a single wide screen display. Left half was the arrange page, and right half was Key Editor and Drum Editor, both in Windows Restore Down as opposed to maximize mode. What you describe happens on just 1 display here. Note that neither editors have the bar focused.

If you desire others to suggest a solution, it may be helpful to create a step-by-step reproduction so anyone can follow along. I think I’m following you, but not positive.

On the Arrange Page, select a track, then select a part from that track. Then with the same track selected, click on a part in another track. Watch the visibility tab in both open editors to understand the behavior.

To achieve your objective, which I think is pretty common, have you tried the Key Commands Editors>open Key Editor and Editors>open Drum Editor for the purpose of giving focus? Also a PLE called De-slect All Tracks may be helpful if being forced to create a macro.

Here is a macro I use in Metagrid that uses key commands, controller lanes, a PLE, and workspaces. (While I have 4 displays, only 2 displays are shown for this example. ) Note that this starts with my default workspace. Arrange page on the left side, (for this example the right side is blank) and typical meters as well as the History window are on a monitor above.

But whenever I wish to choose to open the Drum editor, and assuming that track is focused, I press 1 button in Metagrid, and the configuration changes. Arrange page has gone to my top display, Drum Editor to where the Arrange page previously existed, a zoom macro to zoom out vertically in the Drum Editor and closing of the History window.

macro 34

The bad part is that without Metagrid I don’t think you can do all of this, but maybe enough? Cubase macros are great, but with this type of macro, you need small time delays between steps in macros which are not offered in Cubase.

Anyway, I don’t know why the drum editor looses focus unless it’s something I’m not seeing above. But I can’t help but think by using the open key/drum editors that should create focus, you can achieve what you desire.

I think that this may be the culprit.
What happens if you asign a drummap to the track?

So here’s a recreation of the issue. Hopefully it helps clear up exactly what’s going on. I would be VERY interested if anyone else could recreate this behavior on their system. Is this intended behavior and if so, what the hell is the logic behind it.

@Greg_Purkey (not Greg Ondo from the Cubase livestreams by chance?) Thanks for all your insight. It’s a bit hard to tell exactly what’s happening in the video you uploaded but essentially you’re using configurations to jump between window sets? Sorry if I’m misunderstanding that. Yeah, custom configurations might be an option but before I resort to that it would be nice to try to resolve this through simpler means. I can’t really imagine how a PLE could help resolve this is issue directly (i.e. without the use of configurations) but I am definitely open to any suggestions.

BTW I am Metagrid Pro user, as well as Keyboard Maestro (and BetterTouchTool and Karabiner haha), which the deeper I dive into, the more I realize how powerful these tools can be. A lot of spinning plates though :face_with_spiral_eyes:

@Buer Yeah, cheers I think there’s one loaded in there but I could be doing it wrong…? Again it does open the Drum Editor when the Key Editor is closed, but if Key Editor is open it jumps to that screen every time.

If the windowed Key Editor is already open, double clicking a MIDI Part or using the command Open Editor will open that part in the existing Key Editor window regardless whether or not a Drum Map is assigned to the parent track.
I believe this has always been the behavior.

@mlib Thanks for the reply. This is exactly what I feared. This doesn’t seem like the most optimal workflow but maybe there is some rational to it? Is there some benefit to this that I’m not seeing.

I can’t think of one either. I’m guessing it is an oversight.

So…how can we make the developers aware of this issue? Seems like an easy fix

Also if they could add a command for entering full screen mode, or at least for Mac (not sure about Windows). The native macOS command doesn’t work. Or a preference to open editor windows in full screen by default?

And I know I’m on a bit of rant here sorry but it would also be nice to have command that is simply “open editor” (and probably a “close editor” command too) in addition to the “open/close editor” command. That way the window doesn’t close if you accidentally press the command when the window is already open.

If you tag this thread as a feature request and state clearly what you want the feature(s) to be, there’s a chance that someone from Steinberg will read it.

1 Like

I was thinking it changed years ago, but you’re probably right. Too many years have elapsed. :laughing:

But which editor? Open Key, Open Drum? To close, assuming it’s focused, I use Windows ctr+w. There must be the equivalent on Mac?

Work-around:
Since you use Metagrid, this should be easy because you have the advantage of longer macros with delays which Cubase does not have.

Yeah, sorry…the .gif is quite rough to completely see what’s going on.

In that .gif, I have 2 displays. One on top of the other. The bottom one is a wide screen.

Look at the bottom display. Starting out, on the left side of the bottom display is the Arrange Page with a Toontrack vst track in focus. On the right side of the bottom display is just Windows wall paper. (I tired to eliminate as much non-relevant stuff for this example)

On the top display you see Cubase Supervision in the upper right. Below are VU meters. On the upper left side of the top display is the History page. I make lots of mistakes so it typically stays open.

Now, press 1 button in Metagrid.

The Drum Editor moves to the lower display in full screen. The Arrange Page has moved to the upper screen, and the history page has closed.

I do whatever editing I want, then with a Metagrid default Workspace button, go back to “normal” mode.

The following Metagrid macro is probably worthless to you because every persons configuration is different. I’m using 4 displays, and 2 of them in link mode. However I’m confident you could take these ideas and achieve what you desire.

With the track and part in focus:

bring to front
.5 delay
open drum editor
controller lane set up #1
.3 delay
workspace 8
.4 delay
open drum editor
.3 delay
history
.3 delay
ctr+w (windows close)
ctr+sft+M (windows maximize)
zoom to locators
.5 delay
macro 224 (zoom out many times)

This works for me. And for the smart people to hopefully chime in, I’m always willing to eliminate steps or do anything that makes the macro smaller as long as the result is the same. I’m here to learn.

I have different macros that open editors that are dependent on my cursor, locators, and one that opens range duration.

Also, fwiw, I am just using Metagrid Legacy. I’m scared of Metagrid Pro however I have found a person who is willing to help me make the transfer in 2026.

Merry Christmas!

@KT66 Great! Now, how do I do that exactly :sweat_smile:? I’ve been looking around the Steinberg page and asking ChatGPT how to do it here for half an hour. Can’t seem to figure it out

Sorry to ask again but can anyone walk me through the process of how to tag this thread as a feature request? Seems like it would be very simple but not sure where/how to do it :sweat_smile:

Click the small pencil icon on the top of this page by the thread title.