What is CC11 — and how it differs from CC1

The short answer: CC11 is expression — the fine, fast shading of loudness within a note or phrase. CC1 is the mod wheel, which orchestral libraries almost always map to dynamics: the broad arc that also crossfades the tone from soft to bright. CC1 decides which performance you hear; CC11 shapes how it moves moment to moment. You need both, and they should not be doing the same thing.

What CC11 actually is

CC11 is MIDI Continuous Controller number 11, named "Expression Controller" in the MIDI specification. Like every MIDI CC, it carries a value from 0 to 127, and you can send it as often as you like while a note is sounding — which is the whole point. Note velocity is fixed the instant a note starts; CC11 keeps moving after the attack, all the way through the note's tail.

In the original design, expression was a secondary volume control: a scaling factor applied under CC7 (channel volume), so an engineer could set a fader once with CC7 and let the performer shade underneath it with CC11. That heritage still shows. In most orchestral sample libraries CC11 behaves as a level trim — it changes how loud the sample is, without changing which sample layer you are hearing.

That last distinction is the one that trips people up, so it is worth stating plainly: pulling CC11 down makes a note quieter, but it does not make it sound softer. A fortissimo string sample turned down with CC11 is still a fortissimo tone — bright, dense, full of bow noise — just played at a lower level. It reads to the ear as a loud performance behind a closed fader, not as a gentle one.

What CC1 does instead

CC1 is the mod wheel. Nothing in the MIDI spec says it must mean "dynamics" — on a synth it usually means vibrato — but the orchestral sample library world converged on CC1 as the dynamics control, and that convention is now near-universal.

The reason it matters is that CC1 is typically wired to a dynamic crossfade. The library holds several recordings of the same note — one played pp, one mf, one ff — and CC1 blends between them. So when you push CC1 up you are not just raising the level: you are fading toward a genuinely louder recording, with the harder attack, the brighter tone, and the extra bite that a real player produces when they lean in. The timbre changes, because the performance changed.

Why you need both

Because they fail in opposite directions.

Ride CC1 alone and every change in loudness drags the tone colour with it. You cannot make a small, quiet gesture — easing a note's tail, dipping a fraction at a bow change — without also dulling the timbre, because CC1 is crossfading you toward the soft samples. Small moves become tonal events instead of expressive ones.

Ride CC11 alone and you get the mirror problem. The level moves, the tone never does, and the whole passage sits at one fixed colour. A crescendo drawn entirely on CC11 gets louder without ever opening up — the unmistakable sound of a fader being pushed rather than a player digging in.

The working division: CC1 for the arc, CC11 for the detail. CC1 draws the long shape of the phrase, where the music is heading and where it relaxes. CC11 handles the faster, smaller shading that lives on top of that shape — the tapering tail, the lift on a syncopation, the dip where the bow reverses, the subtraction where a wind player takes a breath. Together they behave like a performance. Separately, each one is half of one.

How to ride them in your DAW

The mechanics are the same everywhere; only the vocabulary changes.

Logic Pro

Both controllers live in the MIDI Draw lane under the region — switch the lane menu to Modulation (CC1) or Expression (CC11). The usual workflow is two real-time passes with a hardware fader or mod wheel: record CC1 first while listening to the phrase shape, then a second pass for CC11 detail. The pencil tool draws curves by hand if you prefer. Note that Logic's own Volume lane is CC7, not CC11 — a separate control that most libraries also respond to, and one you generally want to leave for mixing.

Cubase / Nuendo

CC1 and CC11 appear as controller lanes in the Key Editor, and the Expression Map system can drive articulation switching alongside them. Cubase users often set up the two lanes as a fixed pair in the track's automation view so both are always visible while editing — worth doing, since the whole skill is watching the relationship between the two curves rather than either one in isolation.

Two general habits pay off regardless of DAW. First, thin your recorded CC data — a live fader pass generates far more events than the music needs, and dense lanes are miserable to edit later. Second, check what your library actually listens to. The CC1/CC11 convention is strong but not absolute, and vibrato in particular lands on different controllers in different libraries: a curve drawn on CC21 does exactly nothing in a library that expects vibrato somewhere else.

Where Palpito fits

The honest position first: hand-riding CC well, by a composer with the time and the ear, is unbeatable. Nothing here replaces that. What it costs is hours — a couple per cue, repeated for every section — and those hours are what Palpito gives back.

Palpito is a small offline app that reads your MIDI part and drafts phrase-aware CC1 and CC11 curves for you. The shaping is tempo-referenced, library-aware, and articulation-aware: it knows a horn does not breathe like a cello, that strings dip a little where the bow reverses, and that vibrato has to be routed to the CC your particular library actually listens to. It is deterministic — the same input always gives the same result — and it is a draft you refine, not a black box. Fully offline, no cloud, no AI, no subscription. The core app is free.