How to select notes in the Logical Editor that have specific CC data?

How to select notes in the Logical Editor that are:

  1. have CC110 data written to it (This is just a free control code)
  2. that have control code data within range of 70 to 80

On this picture I already can select notes if they have a VELOCITY within range of 70 to 80. How to achieve this with control codes

Pretty straightforward to select only the CC values in the range you require but you will not automatically be able to select the notes that fall in that range of CC

That’s so unfortunate. Could we turn this question into a feature request?

I’m desperately looking for this feature. If it’s not possible, I’ll have to look for another tiny software solution.

Did you figure it out?

I’m trying to convert Roland E-Drums Hi Hat data into General MIDI data. So I need to select specific notes that have specific CC data (foot pedal down/up)…

One issue is that the cc data is its own independent MIDI Message and not some element in a MIDI Note On/Off Message. However Velocity is actually a required element in a MIDI Note On/Off Message. So when you look at a MIDI Note Message it will always have one and only one Velocity value associated with that Note Message. Further there will never be a MIDI cc Message that is part of a Note Message.

So you can Select Notes based on Velocity because that’s a characteristic which Notes posses. And since they have no cc Values you can’t Select based on that

I’m guessing what you are really trying to do is to Select Notes based on when they occur relative to a cc Message? Can’t think of an obvious way to do that off the top of my head.

Thanks Raino. Yes I’ve done a lot of research and realizing this cannot be done on Cubase (or Logic). So I’m looking for a different solution. I’ve found a few interesting solutions (links below) on Ableton and Reaper, but I can’t find the option on Ableton, and have 0 knowledge of Reaper…

Perhaps if you let us know what you are trying to accomplish overall folks could offer some suggestions. What are you starting with & how would you like it to end up?

Here’s what I’m trying to accomplish, simply:

Convert [Note D#1 with a simultaneous MIDI CC4 value of <60] to Note C#5
Convert [Note D#1 with a simultaneous MIDI CC4 value of >60] to Note D#5

And this means what exactly? Not trying to be pedantic, but the specific details are important. Do you mean that both MIDI Messages occur at exactly the same time, or that the cc Message occurs between the start & the stop of Note Message, or even before? Either way using the LE seems iffy at first glance.

What is your use case? Perhaps there’s a different approach.

By simultaneous I mean that the CC4 value at the time of the note ON is <60 or >60.

My use case:
I’m using a Roland VH-11 hi hat trigger.

When it is hit, a MIDI note is produced. The CC4 control represents the pedal that opens and closes the Hi Hat.

I want Cubase to recognize a CC4 of >60 as an open hi hat and trigger an open hi hat sound.

Oh, you should look at using Expression Maps for that. It can use the cc value to select which articulation gets used.

As mentioned earlier MIDI CCs are independent and not associated with MIDI note messages. A MIDI note message in MIDI represents a note on, the velocity and a note off message. The length of the note is the time between the note on and note off messages. MIDI CCs are completely independent of notes and are applied to every note on the MIDI channel.

MIDI 2.0 can have note based MIDI CC data which is basically built upon Note Expression data. The problem is that your drum controller like the nearly all MIDI controllers is that it is not MIDI 2.0 so you have to work with the restrictions of the device. The real issue is the original MIDI spec that the drum controller is designed to work with.

If CCs could be treated like a (CPU-)register, then we could look up the last value that was written into any CC (I would omit RPNs and NRPNs here). It is basically what any hardware synth does.

However, I am not sure how much time I would spend on developing MIDI 1.0 features in Cubase with the advent of MIDI 2.0, given the limited development capacities Steinberg has.

SOLVED:

I was able to solve this issue by importing the MIDI into Ableton Live and using a Max4Live device called “Note Transpose Depending CC” to filter the info as needed. I then recorded the output to another track, and exported it back to Cubase.