What MIDI Actually Is
MIDI stands for Musical Instrument Digital Interface. It was standardized in 1983. It does not carry audio. It carries instructions. When you press a key on a MIDI keyboard, the controller sends a number between 0 and 127 to tell a synth what note to play, how hard, and for how long. That is the entire concept. Everything else is built on top of that basic message system. Learning MIDI from the bottom up is the only way to actually understand it. Most tutorials jump straight into DAW workflows, and that leaves a gap. You can program notes in a piano roll without knowing why they behave the way they do. I spent months troubleshooting timing issues before I realized I did not understand clock signals. That was the turning point. MIDI has five main message types you need to know cold. Note On fires when a key is pressed. Note Off fires when it releases. Pitch Bend shifts the tuning continuously. Modulation controls vibrato depth or other parameters depending on how the synth is assigned. Aftertouch responds to how hard you press after the initial strike. These are the building blocks. Everything else is velocity curves, CC mappings, or device-specific implementations.
Cable type matters more than people admit. The original MIDI standard used 5-pin DIN connectors with a serial protocol running at 31250 baud. It is synchronous, meaning both devices share a clock. USB-MIDI came later and abstracts that away, but the underlying message format stays the same. If you are working with older gear or hardware synths, you may still run into DIN ports. A proper opto-isolated MIDI interface prevents ground loop hum from ruining your recording. I learned that the hard way with a Roland Juno-60 and a cheap USB-to-DIN cable. The noise floor jumped by about 12 dB whenever the synth powered on. Switching to a Behringer Ultra-Cube MIDI interface fixed it completely.
The Message Structure
Each MIDI message is one to three bytes long. The first byte is the status byte. It tells the receiving device what kind of message follows. Channels run from 1 to 16. You can set your keyboard to output on a single channel or in multi-mode. Most DAWs default to channel 1, which is why some setups feel broken when nothing plays. The second and third bytes are data. For a Note On message, the second byte is the note number and the third is velocity. Middle C is note 60. Velocity zero is the same as Note Off in practice, even though they are technically different messages. This tripped me up for a long time. Some older synthesizers treat velocity 0 as a Note Off. Others ignore it entirely and play the note at minimum volume. Always check your gear manual before assuming how it handles edge cases. System Exclusive or SysEx messages are where things get complicated. They let manufacturers send proprietary data blocks for things like patch dumps, factory resets, and firmware updates. The format is open-ended and varies between brands. I once spent two hours trying to back up a Kurzweil PC3K patch library using a free SysEx tool that crashed mid-transfer. The file was corrupted. I ended up using the factory's own software on a different computer and got it done in twenty minutes. Stick to manufacturer tools for anything beyond basic MIDI data.
Get the Full Details
MIDI Clock and Timing
MIDI Clock ticks at 24 ticks per quarter note. Start, Stop, and Continue messages control playback across connected devices. This is how hardware sequencers synchronize drum machines and synth modules. The problem is that MIDI Clock is inherently imprecise. There is no quantization. Jitter accumulates over time, especially when multiple devices are daisy-chained through opto couplers. A drum machine and a synth connected directly will drift apart within a few bars. Using a dedicated clock generator or routing through your DAW's master clock usually keeps things tight. USB-MIDI changed the timing conversation. The host computer becomes the clock source, and devices sync to the DAW's internal timing rather than each other. This solved a lot of drift problems but introduced latency issues. Some cheap USB-MIDI interfaces have driver problems that add 10 to 30 milliseconds of delay. That is enough to make playing feel laggy. If your recordings sound off even when you are playing in time, check your interface latency settings and buffer size. Moving from 128 to 256 samples usually eliminates the perceivable delay without making your CPU work harder.
Common Pitfalls
Thru ports are a source of endless confusion. Every MIDI-out port has a corresponding Thru port that repeats whatever comes in. Daisy-chaining multiple devices through Thru ports works fine in small setups, but the signal degrades. Capacitance builds up across long cable runs, and timing errors multiply. I once ran a chain of five devices through a single Thru box and spent three hours diagnosing phantom Note On messages that kept firing randomly. Cutting the chain in half and splitting the output into two isolated cables fixed the issue. Keep MIDI chains under four devices if possible, and use isolated interfaces rather than Thru boxes for anything serious. Channel mode messages are another area where things break silently. Local On and Local Off control whether a synth responds to its own keyboard inputs or only to incoming MIDI. If you press keys and hear the synth but also hear it through your DAW, you are dealing with a local On issue. Toggle it to Local Off when recording to prevent double-triggering. Some keyboards remember this setting, some do not. Always check before you start recording. Real-time stream messages and non-real-time messages are distinct categories. Song Position Pointer and MIDI Time Code synchronization can cause your sequencer to jump to the wrong position if the wrong message type gets sent. I had a session rewind to bar 1 every time I opened it because a rogue MTC message was embedded in the project file from an old import. Saving a fresh copy and removing the problematic track resolved it.
Practical Workflow
Start with a simple setup. One keyboard, one interface, one synth. Get the basics working before adding complexity. Map your controller's CC knobs to the parameters you actually use. Spend time understanding what each knob controls on your synth rather than guessing. This alone will cut your programming time in half compared to trial and error. Quantize selectively. Full quantization kills groove. I usually set my DAW to quantize at 1/16th or 1/8th triplet and leave the feel intact. For drums, I nudge individual hits by ear instead of forcing everything onto the grid. The result sounds more natural and takes about the same amount of time once you get used to listening critically. Back up your SysEx data regularly. Patch libraries take hours to rebuild and most manufacturers do not support universal compatibility. A single corrupted file transfer can wipe weeks of work. Keep a labeled external drive with your Synth1, patches organized by category, and note the firmware version for each device.
MIDI is a protocol, not a product. Understanding the protocol means you can make any gear work together. The rest is just cabling decisions and patience.
