Plant MIDI CC: What It Is and How to Use It

Plant MIDI CC: What It Is and How to Use It

Plant MIDI CC:
What It Is and How to Use It

When PlantWave sends MIDI, it outputs two streams: notes and CC. The notes are straightforward, pitch and timing driven by the plant's natural variability. The CC is where sound design gets interesting.

CC Is a Plant Activity Monitor

PlantWave's CC output represents plant activity, how variable the plant's bioelectrical signal is in each measurement window. The PlantWave app labels this value "activity," and that's the right mental model.

Think of it this way: CC tells you how much is happening right now. A calm plant produces low CC. An active plant produces high CC. The value reflects the magnitude of variability in each measurement, not a directional sweep over time.

Technically (for those who want the firmware details): CC is derived from the pulse width range, the difference between the highest and lowest conductivity readings across a 9-sample window. The firmware then smoothly ramps toward the target value at 1 unit per 3–102ms, producing gradual transitions rather than abrupt jumps. For the full spec, see the PlantWave MIDI Specification.

Key Characteristics

  • Activity-proportional: Higher CC = more active plant (more variability in conductivity). Lower CC = calmer plant. CC reflects the magnitude of activity in each window.
  • Rarely reaches 127: Full-scale CC is a genuine moment of unusual plant activity. The typical operating range is roughly 20–80 under normal conditions. When CC does hit 127, it's worth designing around, that's a real event, not normal operation.
  • Never sits at zero: There's always baseline activity during active sensing. A CC stream stuck at 0 indicates a connection problem, not a quiet plant.
  • Smoothly ramped: Transitions are gradual, the firmware interpolates linearly, so you never get jarring jumps. This makes CC well-suited to parameters that benefit from organic, slow-building change.

Sensitivity vs. CC Range

An important distinction: sensitivity controls how often notes and events fire (the threshold for what counts as "enough change to trigger a note"), not the ceiling of CC values. Turning sensitivity up means more events, not higher CC. Higher CC values require a genuinely more active plant, sensitivity alone won't get you there.

The Canonical Example: Chain Selector

The most powerful way to use plant CC in Ableton is with a chain selector on an Instrument Rack. Map CC to the chain selector, then spread different instruments or effects chains across the CC range:

  • CC 0–30: Quiet pad, warm, sustained, minimal movement
  • CC 30–60: Layered texture, more harmonic content, subtle rhythmic activity
  • CC 60–90: Active ensemble, bright, complex, evolving
  • CC 90–127: Peak moment, dramatic, dense, the instrument the plant plays when something unusual happens

The result: the plant effectively mixes its own sound based on how active it is. Calm moments are quiet and warm. Active moments are bright and complex. The transitions happen organically because the CC ramp is smooth. No automation needed, the plant is the automation.

Best Parameters to Map

CC works best on parameters that respond to gradual, organic change:

  • Arpeggiators, running in "as played" mode, an arpeggiator quantizes plant notes in real time without imposing a pre-designed melody or ascending pattern. The plant's own timing shapes the phrase. When CC drives a chain selector that changes arpeggiator rate, plant activity directly shapes the rhythmic character of the phrase, faster activity produces denser phrases, quieter moments let notes breathe.
  • Chain selector (Ableton), the canonical example above
  • Filter cutoff, sweeps that open and close with plant activity
  • Reverb size / decay, space expands as the plant becomes more active
  • LFO rate, modulation tempo shifts with the living signal
  • Macro controls, map CC to a rack macro affecting multiple parameters proportionally
  • Delay feedback, small range, large textural impact
  • Effect send levels, route activity into a reverb or delay bus

Parameters to Avoid

  • Volume, creates uncomfortable level jumps when activity shifts
  • Low-pass filter with high resonance, can produce painful peaks at certain CC values
  • Pitch, unless you're deliberately seeking dissonance

The principle: give the plant control of character, not level. Small CC ranges produce spacious, evolving textures. Large ranges produce chaos.

CC Mapping in Ableton, The Workaround

Ableton's MIDI Map mode detects the last-moved controller. With PlantWave active, both notes and CC stream simultaneously, Ableton may pick up a note instead of the CC when you try to map.

Fix: Isolate CC Temporarily

  1. Unplug the electrodes from the PlantWave (stops signal, device stays connected)
  2. In Ableton's MIDI preferences, disable Track for the PlantWave input while keeping Remote enabled, this stops notes from being captured during MIDI Map mode while CC still flows through
  3. Enter MIDI Map mode
  4. Plug electrodes back in, Ableton sees only CC, map it to your target parameter
  5. Exit MIDI Map mode, re-enable notes, reattach electrodes

Alternatively, start with a template that already has CC80 (PlantWave's default) mapped to a chain selector or macro.

Configuration

Default CC number: 80. Default MIDI channel: 1. Both configurable via the PlantWave app (iOS/Android), web browser, or directly through the MIDI Bridge app. For the complete list of configurable parameters with defaults and ranges, see the PlantWave MIDI Specification.

FAQ

Is the CC output random?

No. It reflects real bioelectrical variability. The signal carries patterns that change based on light, humidity, time of day, and the plant's biological rhythms. It's a living signal, not noise.

Do different plants produce different CC?

Yes. Pothos tends to produce higher, more variable CC. Snake plants often produce steadier, lower values. Choose your plant the way you'd choose a performer, species matters.

Can I use CC from multiple plants?

Yes. Using the MIDI Bridge, assign each device to a unique channel and map each plant's CC to different parameters. No hard device limit, 4 confirmed stable in testing; practical ceiling varies by Mac hardware and Bluetooth environment.

For step-by-step Ableton setup (all 3 connection methods + multi-device routing), see How to Make Plant Music with Ableton Live. For safe CC mapping strategies in long-running sessions, see PlantWave for Installation Artists

Download the PlantWave MIDI Bridge, free for PlantWave owners.

Back to blog