Modulation keeps disappearing from the CC lanes. I open Modulation from the drop down menu at the bottom for it to appear in the lanes… even if I record with modulation, I have to bring it up, and then a little latter, when I come back to that track, it doesn‘t show up again and I have to manually bring it up again… that‘s very annoying… velocity and CC11 are always there. Is there any explanation/fix for this?
In the project window some midi blocks appear fatter than on other tracks, at same track height, with no overlapping notes or anything… is this normal? Couldn‘t find a satisfying answer online…
I meant CC1 (not modulator), modulation, sry was maybe not clear
By fatter I mean, the midi blocks (in project window view, not in piano roll) don‘t have tha same appearance, in one track they just look thicker (vertically) than others… if I change it to lines, they all look the same, I visually prefer blocks, though
I’m sorry, but without being able to see what you are seeing (hence the screenshot request), I can’t tell what you are trying to describe. The MIDI PARTS you see in the Project always fill the the entire Track Height. I don’t understand what “look thicker” might describe. Similarly I don’t follow “change it to lines.”
I can post a screenshot when my machine is running again, sleeping now
In preferences you can choose if you want the midi data displayed as blocks or as lines, or even as notes, if im not mistaken, or even no data display at all… that‘s what I mean by change to lines.
So, here‘s a foto. As you can see, Violins2 have noticeably thicker midi blocks… it‘s no big deal, admittedly, I’m just wondering if there‘s any practical explanation for this kind of behaviour… thx.
The note height thing probably relates to the combination of track height and pitch range within the relevant parts. I just tried an experiment, with the following visual results at the exact same track height (4 rows):
It is quite clear that the bottom row notes are vertically thinner. Wny would that be?
The top passage has a pitch range of F1 to G4 in the area I’ve clipped (it is actually a bit wider than that outside the screenshot boundaries (F1 to C5). By contrast, the bottom clip’s pitch range is only C4 to A4. I think Cubase tries to make the notes as high vertically as it can in the track’s height in view of the range of notes in the clip. It obviously can make for thicker notes if the range is narrower.
If you do much comping of MIDI, you’d likely also notice that, when you cut clips into shorter segments, they may look quite different in this respect, with the shorter clips only needing to reflect the range of the notes in that versus on the entire clip they came from (which might be an entire track’s length if you tracked the part from start of the song to finish). In that context, it can actually be a bit disconcerting, since the relative vertical position of clips in different lanes doesn’t necessarily tell you much about their pitch. Here’s an example of what I mean, not using lanes, but just slicing the top clip up a bit into areas with narrower and wider ranges:
Here it’s pretty easy to see that the second clip from left has the tallest notes, leftmost clip has the second tallest, and the other two are in the same ballpark. However, if you zoom in enough vertically, those differences seem to disappear. Here are the same segments of the top track’s clips zoomed all the way in:
I don’t really notice any differences here, so maybe Cubase only makes these distinctions when the track height is short enough (which is almost always the case in the comping context I mentioned since I need to fit all lanes on the screen at once).
I’ve seen this, too, and it seems to relate to where you make the lane change and closing editor windows. Here’s one scenario:
I double click on a MIDI clip, which brings up the lower zone key editor. However, I need more space, so I bring up the full screen key editor. I add the modulation lane there and write information in it (or edit information that is already there). Now I close that window and close the lower zone (which still shows the default pitchbend lane). Later (potentially immediately later, I want to change some modulation I’ve just edited, so I do the same sequence to get to the full-screen editor – it is now showing the pitchbend lane instead of the modulation lane.
However, here is another scenario. I start as before, but, before going to the full screen key editor, I add the modulation lane to the lower zone. Now I go to the full screen key editor, where the modulation lane is already there. I make my changes and close things down as before. Now I want to make more changes, so I double-click on the clip again, and it now shows the modulation lane in the lower zone, still showing it when I get to the full screen key editor.
Thus, it seems to me that whatever is active in the lower zone for a specific track (or clip?) is what will be the default next time. If you make those lane visibility changes in the full-screen key editor, they’ll only persist while you are in the full-screen key editor. Once you close it, you’re back to whichever lane(s) were chosen in the lower zone key editor.
Side note: I find this frustrating as I’d almost never edit controller information in the lower zone, but I do sometimes edit note information in the lower zone, so I don’t just want to make the double-click action always open the full-screen key editor (even if that’s what I end up using the majority of the time). I don’t know what would happen in this context if the full-screen editor was my default for the double-click. That is, would changes I make there then be permanent, or would the lane visibility always revert to the defaults since I wouldn’t be using the lower zone editor at all?
Rick, thank you for taking the time to reply to my post.
Yes, what you say about the MIDI clips makes sense. I guess it’s just confusing because it’s kind of useless and not something you’d be used to from other DAWs.
I’ve also come up with a similar explanation for how the lanes behave. I’ve noticed that if I just open/close the MIDI clips directly in fullscreen, without even touching the lower zone (by hitting the Enter key), it seems to stay consistent. For the other cases, I’ve now set a key command for “Show Used Controllers,” so I can quickly display all the lanes without having to click through the menus.
