How to Use MIDI Control Data in Cubase

[@DenianArcoleo]

I think some kind of award for clarity in teaching is due here. Thank you for this invaluable lesson.

[@OneManAndHisSongs]

That's very kind of you to say, thanks for the feedback!

[@NickFromNetherlands]

Your 3 videos will explain midi data ,midi notes and Automation very well . Thanks

[@nolet99]

Thank you very much!! Midi cc stuff has been a longtime mystery for me, and now you have made that problem go away. Very clear tutorial 👍

[@OneManAndHisSongs]

You're very welcome!

[@svenisaksson3970]

Note that CC64 is just a normal controller. It's not limited to just 2 (on/off) values. Altough it's generally, but not always, used that way. It can contain any value between 0 and 127. My Kawaii VPC1 controller keyboard has this dynamic perdaling capabillity. This allows me to do, what is called half and quarter pedaling on a real piano. This means I don't fully press the pedal. Of cause the instrument must be able to respond to this dynamic pedaling, for this to work. Not many do, but there are a few. However, this can bite you. I recomend that you are careful and only use the values of 0 and 127 for normal pedaling. If you use any other value (say 63, which would be interpreted as pedal down by most instruments) would be interpreted as pedal half down, by an instrument that reads dynamic pedaling. So would a value of 65, that would be interpreted as pedal up by most instruments. Thus, the pedaling might not come out as you intended, if you play back the project with another instrument.

[@OneManAndHisSongs]

Fair enough, thanks for the clarification. I think I did squeeze in a 'typically' when referring to the on/off nature of the command! It's correct that the "normal" case is as described - but, as you quite rightly point out, it is just another CC value like any other, so it would have benefitted me to make that point more clearly.

[@radi0n]

The way of teaching is brilliant. The only minus for me is that you don't use Bitwig :)

[@OneManAndHisSongs]

Thank you! Yeah, sorry, I'm strictly a one DAW kinda guy. (the hundreds of hours it takes to learn, I'm always amazed at anyone who has time for more than one!!)

[@GaryMatthews1]

A fantastic tutorial video again. Your explanation of the chosen subject matter is top notch, very complete and easy to understand. Thx

[@OneManAndHisSongs]

Thanks for all your support, it really helps :)

[@bradrisley3036]

Anthony, I cannot express enough how grateful I am for you. I have recently switched from Pro Tools to Cubase and your content was an invaluable resource for making that decision. And videos like this one are icing on the Cubase cake! I try to read manuals, but the clarity with which you explain these technical concepts (CC, Automation, MIDI, etc.) brings it all together in a way that helps it to make sense to me and stick in my brain. The time and effort you're putting into what you do is making my life easier and more productive. Many thanks!

[@OneManAndHisSongs]

Wow, that's very kind of you, thank you so much! I'm glad my style appeals to you - hopefully my forthcoming 'Expert' series will appeal to you as well :)

[@sashko-fomin]

There's a much more serious bug in Cubase (or just a very poor implementation) than the one at 17:35. The ramps and curves for MIDI CCs translate to discrete values with a very low sample rate which produces a horrible stepped effect for a parameter you want to modulate like filter cutoff. I mean, the resolution of MIDI 1.0 on its own is not good enough but Cubase's ramps and curves make it even worse. There’s a bug report on Steinberg's forum where they promise to fix it but most likely it'll take forever. I compared how these ramps for a filter cutoff sound in Cubase an Ableton Live. It’s just night and day. The "advanced" music production system as Steinberg likes to describe most of their products doesn't have a decent implementation of a feature that directly affects sound quality.