Not sure if this is supposed to happen, but I was just trying to edit some midi chords after dragging them down into a midi track. I also had the chord track selected when I hit enter to edit. Well…Cubase did not like that too much and pretty much crashed. I tried to hit abort, but it was too late:
This always happens when multiple chord events are selected on the chord track and then the chord editor is opened, for example, by double-clicking.
This has happened to me several times, and it’s annoying.
Luckily, I was able to cancel the process each time (I think it was with the esc key, but I’m not entirely sure).
Let’s play: Is it a bug… or is it jazz?!
That’s Bebop - 41k progressions in a 4-bar pattern would be ballad mode.
![]()
There needs to be a point where Cubase realizes you are not living in multiple parallel universessesses, and responds with, “ok I think you have had enough of this.”
This is again a consequence with the divided track list and the selection behavior of it. If you have something selected in the top track list, it simply doesn’t get deselected when you click on some part in the bottom half. I don’t know if this is was “by design”, but it only leads to problems, not only with the thousands of chord progressions, but e.g. when setting a color for a selected part/event I often inadvertently color in a marker or chord symbols because it is still selected.
No doubt…I am very annoyed with it myself. I usually put the marker track in the upper division, and am constantly accidentally deleting my marker tracks because I tend to double click onto a marker position, and it automatically highlights the marker track. Trying to get it to deselect after that is a pain and then I delete another track not even realizing I also just deleted my marker track.
I hope they add a preference to only select tracks in main project window when selecting events because, I like and use that feature, I just dont need it on utility tracks. Or have it only select audio/instrument tracks or something like that. Or maybe there is, and we just don’t know about it?
I think the better option would be to simply automatically de-select anything in the top track list when you select something in the bottom track list and vice verse. Just as it would happen if you don’t use divide track list (unless you use shift click to select multiple). I think that would be a behavior that users would expect. I cannot see any advantage of the current behavior.
I run into the same issues with the divided track list. I’m not sure Steinberg anticipated that users would use the divided track list as a simple “pin to top” type of feature. That’s basically how I use it at least.
Another thing that bothers me with it is how it scrolls around its upper and lower boundaries when dragging and dropping an object. It makes it cumbersome if your upper track list is rather short in height, contain tracks you just want hidden away and you just want to move a marker e.g. I proposed a setting to disable auto scroll of the upper track list a while back, but I’m not sure that is the proper solution.

