Option to enable MIDI CC curves by defualt (aka. linear ramp by default)

Cubase
1

I have to say Cubase 11 is the best upgrade I have received so far. Rock solid here - except for a few bugs which I hope get fixed rather soon, like the MIDI CC curve bug when you change the tempo.

I am really enjoying the MIDI CC curves. Soooo much better.

Now, I was wondering if there is a way to tell Cubase to use the MIDI CC curves by default, i.e. always use a linear ramp between two points unless instructed to do otherwise? Would be great to have that as an option somewhere.

Doing mostly orchestral stuff there is little use of a jump in CC values.

Thanks!

1 Like
2

Agreed that this would be very useful and reduce tedium.

3

Controller Lane Setup Menu > Type of New Controller Events

1 Like
4

Done.

image
image713Ă—700 79.2 KB

2 Likes
5

Awesome!! Now I guess Steinberg only needs to fix the strange Tempo map bug which currently renders those ramps/curves a bit less useful.

I hope they are quick. Otherwise, this is really great!

Thank you for the hint!

6

This isn’t working for me. I close the edit window after changing the curve property up the top to ramp (because it keeps changing back to step) then come back and its at step again! I have the setting described by steve always set to ramp.

I would never want step. I’d like to know who here would. It has no use yet Nuendo 12.0.50 keeps defaulting back to it. Its a constant battle.

FR: A setting in preferences to NEVER use step! EVER!

On the rare occasion that we need a sharp jump its easy to draw in ramp mode by pulling the point directly next to the previous point.

2 Likes
7

Yes, please! This would be extremely nice. I fight with step vs ramp A LOT. This feature would save me so much time.

8

It looks like Cubase will go full ramp mode (with optional step) in Cubase 13.

9

Actually I came here looking for the opposite setting, to have it default to Steps. I work with CC controllers all the time, and most of them are on/off switches, so 128 levels doesn’t make sense for my workflow. Good that I found what I was looking for.

10

I have a dilemma. Certain controllers (midi that is) NEED to be in step, and others in Ramp. Steinberg recognise this with the list of exceptions in the manual. For example CC64 is excluded from ramp, and is always step. Why? Because it is a pedal that has a binary state - down or up. Ramp causes controller data to “travel” over time and you do not want this in this case.

Now, I also use the Una Corda pedal (AKA soft pedal or left pedal) ALL the time, and have it mapped to all sorts, such as mutes on with strings, etc etc. THIS pedal needs to be in STEP always.

I also use certain other controllers to manipulate sounds, for example cc01 thru around cc16. These control VSL dimensions, etc, and it’s great because CC’s are chased, unlike note triggers. When I flick back on the time line, all my sounds are updated.

I want the ability to decide for myself which controllers are fixed ramp, and which are fixed steps. It’s a feature request I guess.

Thanks