1. Didja accidentally blow through the whole, "We're using our real names" thing on registration? No problem, just send me (Mike) a Conversation message and I'll get you sorted, by which I mean hammered-into-obedient-line because I'm SO about having a lot of individuality-destroying, oppressive shit all over my forum.
    Dismiss Notice
  2. You're only as good as the harshest criticism you're willing to hear.
    Dismiss Notice

Cubase show CC1 on automation lane

Discussion in 'Tips, Tricks & Talk' started by Matthias Calis, Dec 6, 2017.

  1. Hey folks, just wanted to share this quick tip with you guys.

    I am about an hour and a half into Mike's excellent Template Balancing masterclass and I noticed he has his CC1 data displaying under the MIDI track. I recently commited to playing my sounds in instead of drawing them in with the mouse (yes, I used to do that) and I realized that if I am playing in sounds, I am not going to open the MIDI editor much, where I usually see my CC data.

    Cubase, by default, overlays the CC data over the MIDI clip (showing it as bars), but you can put it on an automation lane.

    1. Go to MIDI > Midi Controller Automation Setup
    2. Set the Record Destination to Automation Track
    3. Done! (Well, ofc, you need to show the lanes. If you don't know how, hover over the bottom left side of your instrument/midi track. A downward triangle should appear that you can expand. By default this will reveal the volume lane. You can click on the "Volume" text and change it to "CC1 Modulation" (or any other CC for that matter).

    Alternatively, see the screenshot below!

    Also, I happened to notice that Cubase (I have Cubase 8.5 pro) includes a "MixerDelay" plugin (at least I think it's included in the default package). The cool thing with this plugin is that it can show the delay distance in centimeters and meters, which is a much more useful indication than samples or ms.

    So yeah, if you followed Mike's excellent masterclass and want to use his delay trick in Cubase, I recommend reaching for the built-in MixerDelay.
     

    Attached Files:

  2. #2 Aaron Venture, Dec 6, 2017
    Last edited: Dec 6, 2017
    Great post!

    You've touched on delay distance and this reminded me of a neat little freebie I ran into some time ago. Since you guys seem to have talked about distance during the class, maybe this will be of use. It does much more than just delay the signal.

    https://www.tokyodawn.net/proximity/
     
    Paul T McGraw likes this.
  3. Aaron Venture likes this.
  4. Thanks Paul, great post and I will check that out tomorrow before the session.
     
  5. You've been drinking again.
     
    Matthias Calis likes this.
  6. #6 Matthias Calis, Dec 7, 2017
    Last edited: Nov 7, 2025
    I only know one Paul and he's always very excited

    Is it bad I can actually hear Paul Thomson's voice in my head?
     
  7. I suppose this way the controller information is no longer part of the midi data and will not be exported.
     
    Matthias Calis likes this.
  8. Not actually yesterday...:)
     
  9. Oh, so that's the problem!
     
  10. Why:p
     
    Aaron Venture likes this.
  11. Hadn't thought about that. But yes, I think you're right. For me, this is not a problem as I rarely need to export MIDI.
     

Share This Page