Next Event: Loading...
w/ ---
00: 00: 00: 00 Get Started
Calendar
View upcoming events and classes
Information Panel
Beat Kitchen at-a-glance
Guide Hardware and Recording Primer
Chapter 17 updated

Controllers and External Hardware

A controller doesn’t make sound — it sends instructions (Chapter 16 covered the protocol). A hardware synth does make sound, and getting that audio into your DAW requires routing. An effects processor takes sound in and sends a modified version back out. This chapter is about the practical side of connecting, routing, and using external hardware in a production setup.

Controllers

A MIDI controller sends note and control data to your DAW or to hardware instruments. No sound engine inside — just keys, pads, knobs, and faders that generate MIDI messages.

Keyboard controllers: 25, 49, 61, or 88 keys. The key count determines how much range you have without octave shifting. Weighted keys feel like a piano; semi-weighted and synth-action keys are lighter and faster. If you play piano, you’ll want weighted. If you’re programming beats and triggering synths, lighter action is fine.

Pad controllers: Grids of velocity-sensitive pads for finger drumming, clip launching, and sample triggering. Akai MPC, Native Instruments Maschine, and Ableton Push are the major players. Each has deep integration with its paired software — Push with Ableton Live, Maschine with its own software, MPC with its standalone OS or as a plugin.

Fader/knob controllers: Physical faders and rotary encoders for mixing, plugin control, and DAW navigation. Motorized faders recall positions when you switch tracks; non-motorized faders are simpler and cheaper.

Breath controllers: Generate MIDI data from breath pressure. Useful for realistic wind instrument expression that a keyboard can’t replicate.

Mapping

Most controllers send generic MIDI CC messages. MIDI mapping is the process of assigning each physical knob, fader, or pad to a specific software parameter — a filter cutoff, a fader, a mute button. Some controllers auto-map to their paired DAW (Push maps to Ableton automatically). Most require manual mapping or downloadable templates.

Hardware Synths

A hardware synth has its own sound engine. Audio comes out of physical outputs. To record it into your DAW:

  1. Connect the synth’s audio outputs to inputs on your interface
  2. Connect MIDI (USB or 5-pin DIN) so your DAW can send note data to the synth
  3. Arm an audio track in your DAW and record what the synth plays back
  4. Optionally, sequence the MIDI in your DAW and let it play the hardware — software sequencing, hardware sound

Latency: MIDI over USB is effectively instant. MIDI over 5-pin DIN has a small but measurable delay — a few milliseconds. If you’re layering a hardware synth with software instruments, check the timing alignment. A few milliseconds of offset can make a chord feel mushy.

Effects Processors

Outboard effects — hardware reverbs, delays, compressors, EQs — process audio externally. The routing is a hardware insert:

  1. Send audio from your DAW to a physical output on your interface
  2. Route that output into the processor’s input
  3. Return the processed signal from the processor’s output back to a different interface input
  4. Record or monitor the returned signal on a new track

The round-trip through D/A conversion, the processor, and A/D conversion back adds latency. Your DAW’s automatic delay compensation should handle this, but verify by checking the returned signal’s alignment against the original. If the processed track is late, manually nudge it forward or adjust the DAW’s compensation settings.

Hybrid Setups

Mixing hardware and software — “hybrid” production — gives you the tactile feel and sonic character of physical gear alongside the flexibility and recall of a DAW. But it introduces complexity:

  • More routing to manage — every piece of hardware needs audio connections and possibly MIDI
  • Gain staging at each boundary — every time a signal crosses between analog and digital, levels need to be right
  • No instant recall — hardware settings aren’t saved with the DAW session. You have to photograph knob positions or document settings manually. Close the project and you lose the sound unless you’ve printed the audio.
  • More cables, more potential noise, more troubleshooting

The practical advice: start simple. Add one piece of external hardware at a time. Learn its routing thoroughly before adding the next. Document your signal flow. A diagram of your studio’s routing — drawn on paper or in a notes app — is worth more than you’d expect.

What to Practice

  1. Map a controller. Pick a software synth and manually map four knobs on your controller to four parameters — filter cutoff, resonance, attack, release. Play with the physical knobs while a sequence runs. Feel the difference between clicking a mouse and turning a knob.
  2. Record a hardware synth. Route a hardware synth into your interface and record its audio output while playing MIDI from your DAW. Check the timing — is the audio aligned with the MIDI? If not, adjust.
  3. Set up a hardware insert. Route a track from your DAW out through a physical output, through any piece of hardware (even just a cable loopback), and back into a different input. Record the return. Check for latency offset and adjust.
  4. Document your setup. Draw a routing diagram of everything in your studio — every device, every connection, every cable type. Label audio and MIDI connections separately. This diagram becomes your troubleshooting reference.

This Course

Take This Course Live →

Like what you're reading?

Everything in this guide is yours to keep. But reading about it isn't the same as hearing it, doing it, and having someone who's been at this for 30 years tell you why it matters in your music. This is one chapter of a live course — small group, cameras optional, taught by someone who gives a shit.

View the Hardware and Recording Primer Course →
Leave feedback on this chapter
← All Guides

Beat Kitchen At-A-Glance

Our Socials