None of my notes were showing up in the key editor for my ‘Celeste’ track even though I could clearly see the events in the MIDI track above. I must have troubleshot for 20-30 minutes before I stumbled on the solution. All I did was click ‘Select All Events’ and then the MIDI notes somehow magically reappeared in the key editor window.
ALL of my other tracks were fine (they are all MIDI tracks) and all the events were showing up as well as the notes in the key editor except for the one track (Celeste) that I mentioned above. I have no idea how the notes ended up being invisible. It appears they were that way when I imported the MIDI file that I exported from Dorico.
I haven’t done any ‘takes’ or anything like that which could have led to them being hidden. I imported all of the MIDI data from Dorico 6 Pro and didn’t do any crazy visibility stuff there either.
I am having that same problem after the update. Even when I glue the two parts together, only one shows. All I get is the velocities, in white. I’ll try your suggestion to fix it, but it is annoying!
This image also shows the very annoying new “no contrast background” of the selected midi part in the key editor with the loop cycle activated. Steinberg, please fix that!!!
Could you give us bigger picture, please? I would like to see the whole screen to see, where are the MIDI Parts placed in the arranger. I would also like to see the Activate Part for Editing in the Key Editor.
Sure! I lightened the color scheme of the key editor, so that I can better see my midi parts (still not optimal, much prefer the previous darker background when loop-cycle is activated). But, you can see this little midi part is still missing visually. The midi is still there and plays, it just won’t show.
For these two tiny parts, whichever one I click on first, that one shows and the other doesn’t. So if I click on the first one, it shows. If I click on the second one, then the second one shows and the first one is empty (just the white velocity lines).
I assume this is just a bug related to opening a previous project (15.0) into the update (15.0.20). It does not affect new midi written in 15.0.20. But I have a lot of projects in progress, and this is a problem for sure.
Sorry for the delayed response, but when I did the ‘glue’ tool thing I had did a select all of whatever notes there may or may not have been in the track, but it didn’t find anything, so that was a non starter for me.
But clearly I can see from all the other user responses that this problem is not isolated to me.