I’m trying to use the Cubase Pro 14.0.10 Score Editor for the first time. I’ve brought it up on a piano part that has a fairly full range of notes in it. For example, here is the intro of the song in the Key Editor:
I’m guessing there may be some preference somewhere that I’m not finding, but I’ve done some searching through the documentation (and also some browsing), googling, and searching these forums, with no luck.
When this happens, it’s due to a bug in the internal display quantization calculation where the position of one note causes other notes on the track to disappear. Please could you DM the score to me and I can find (and hopefully fix) the problem note. It’s possible that I might have already fixed this specific issue in our internal build.
Hello, I am having the very same problems, F1 notes not showing on the bass clef staff. I have tried lengthening some of the notes in the key editor, but to no avail. I see notes already in the score get immediately changed when I touch them in the key editor, but the F1 notes, are shown in the key editor but not rendered in the score, even when i make them longer in the key editor. Any suggestion? Cubase Elements 14.0.30
I don’t know, but this seems like a different issue, or at least a vastly different symptom, than the one at the start of this thread, where there were no notes whatsoever, in the bass clef of the grand staff. From your screen shot, I’m wondering if perhaps the F1’s note on is slightly before the start of the clip (e.g. if the clip starts on an exact measure boundary). Maybe that could be a reason why it wouldn’t show in the score editor?
What instrument is this? Is it possibly out of range? The instrument definition can be configured to hide out of range notes in the event they are keyswitches or something.
Thanks for looking at this. It’s pretty crucial for me and I’ve got lots of affected scores. Is there a workaround to avoid you becoming part of our workflow! The notes are fine in the key editor (I think). Thanks
Thanks Paul. I’ve tried looking in Interpretation but nothing worked. But I have found something which I think may be helpful and I’d be interested in your view or whether this might be a step to a solution.
I went into Key Editor and selected a random note and then selected all the events and set them to the same length eg 0.0.1.0. Going back into Score Editor I seem to have the notes displayed although the durations are not correct of course.
I’m not Paul, but check out the solution portion of this thread for my case above:
In particular, Paul found a specific note in my project that was very short, and there was some bug in Cubase that made all notes beyond that point disappear. He suggested lengthening that note (which I did by just a little bit, not to an entire 16th note) did make a difference, and it did.
Your observations here that lengthening all the notes made a difference (but, of course, threw the note lengths off more or less entirely) makes me think that there is some similar problem.
This leads me to wonder if doing something with a MIDI script could provide a less extreme workaround. For example, searching for all notes (in the selection, which could be all notes in the track) lower than some small value, then adding some (small) number of ticks (or is it “tics”?) to the length could accomplish the same thing with a less extreme result.
Alternately, what if you select all notes in the clip, then use the info display and just add one tick to the length field (which should do a similar thing for all notes, I think)? And keep doing that until the problem goes away (which would give you an idea of how big the difference needed was. That would at least be less extreme and more likely to keep the note values similar to what they should be. (I don’t know if there is an easy way to do this type of selection only on notes below some length threshold, but, if there is, that would probably even be better. Of course, you could also visually look for really short notes and try lengthening them one at a time to see if that makes a difference, but, if there are a lot of short notes, that could be more of a pain, and if it is not just one note causing the symptom, then you might never find which ones are triggering the issue.)
Thanks rickpaul. I did play around in the logic and list editors but don’t feel very confident about what I achieved. Here’s the cpr. It’s the piano part that isn’t displaying with all the notes below C4 being cut off (I tried disabling the filters for clef ranges too). I didn’t find any ultra short notes although I do play a lot of notes!
If you could advise Paul or not Paul that’d be great.
After assigning some instruments (I don’t have full HALion, so that was missing, and I had to check on MIDI ports, I’m seeing the same thing as @PaulWalmsley. In particular, in the Key Editor, I looked for the lowest notes, the D2 as Paul mentioned, zoomed in on those, and selected them:
Then I brought up the Score Editor, making no changes in settings whatsoever (no clue if there may be any default settings that could be different from your setup – I don’t think I’ve changed any default settings), so it would highlight those notes, and, as far as I can tell, everything looks okay, certainly no massive blank areas:
In case it matters to you or Paul for context, I am on Cubase Pro 14.0.32 running on Windows 10. I replaced the HALion instance with HALion Sonic and assigned the YAMAHA S90ES Piano patch to the third channel (I did not set up any other patches).
Here are the Layout settings I see in the Score Editor:
