I created a bass instrument, ran chords to MIDI on the track, set chord follow to single note bass, then disabled chord follow to get my bass notes.
I pulled up the key editor to add articulations lane with my expression mapping to change the performance.
What I did not know or noticed until I click the articulation lane fold down was that it was taking all the notes that were clumped together from the chord track.
Basically, the key editor becomes VERY slow and basically unresponsive because the expression map was trying to handle multiple notes per articulation change. I guess Cubase just does not like that right now:
There’s not supposed to be more than one entry per group. But the situation in your screenshot can still occur in certain situations I believe (I’ve seen it before in a few screenshots with others), since the notes themselves get tagged with the articulations, there are certain scenarios where you can end up with an invalid entry with multiple active lanes in a group because the note itself has multiple articulations attached and those articulations shouldn’t be able to coexist in the map as configured, but since the note already has them attached, it doesn’t want to remove any of the articulations at random to try to make it “consistent” since it doesn’t know which one you might want to keeep.
I’m just wondering how you got that in your specific case. But you should clean up the unwanted entries so that there is only one lane active in group 1 at any time.
It was happening when converting chord track to midi, than changing to single note: bass. The chord following, instead of just taking the bass note from the chord conversion, it takes them all and hides the others behind the “bass” note. Even without the slowness the expression map is causing, it causes other issues like just trying to move around in the editor with these hidden notes.
I wish there was a project function to “clean up hidden notes after conversion” or something like that, but I am not very proficient with the PLE yet.
Ok actually, thank you for pointing me in the right direction…I have seen that function menu, but after trying it and reading the manual, Delete Doubles, is more appropriate here. When I try to delete overlaps, that can cause the note to get cut which is not what I want. Delete doubles works perfect even if there are more than two exact note event instances stacked.
Before I was trying out, thin data, which did not work either.
