What Is a MIDI Event List Editor in a DAW?

A MIDI event list editor is a specialized, text-based editing window within a digital audio workstation (DAW) that displays musical and performance data as an ordered chronological ledger. While graphical editors like the piano roll represent notes visually across a timeline, the event list provides raw, numerical data for every single MIDI message transmitted. This guide explains how an event list editor works, the types of data it displays, and the practical scenarios where producers and audio engineers use it over traditional visual tools.

Inside a DAW, every action performed on a MIDI controller generates specific digital commands. The event list editor captures these commands and arranges them in a spreadsheet-like view, organized linearly from the start of the project to the end. Each row in the list represents an isolated MIDI event, while the columns break down the exact parameters of that event into clear, editable values.

The columns of an event list editor typically include:

• Position/Time: The precise timestamp of the event, usually measured in bars, beats, and ticks (subdivisions of a beat, often up to 960 ticks per quarter note).
• Channel: The specific MIDI channel (1 through 16) assigned to the instruction.
• Event Type: The category of MIDI message, such as Note On, Note Off, Continuous Controller (CC), Pitch Bend, Polyphonic Aftertouch, Program Change, or System Exclusive (SysEx) data.
• Value 1 / Note Name: For note messages, this shows the musical pitch (e.g., C3, F#4). For controller messages, this displays the CC number (e.g., CC 1 for Modulation, CC 7 for Volume, CC 64 for Sustain).
• Value 2 / Intensity: For note events, this shows velocity (0–127). For CC messages, it shows the controller value (0–127).
• Length/Duration: The exact lifespan of a note, measured in musical time or ticks, showing when the Note Off message is triggered.

The primary advantage of the event list editor is surgical precision. Visual interfaces like the piano roll or automation lanes can make it difficult to locate tiny errors, such as two notes overlapping by a single tick, accidental double-triggers, or microscopic velocity fluctuations. In an event list, these issues appear instantly as sequential rows of numbers, allowing users to alter values simply by typing over them.

Furthermore, the event list provides visibility into non-note messages that graphical editors often obscure or hide. If an external synthesizer behaves unexpectedly due to errant Program Change commands, reset messages, or stray sustain pedal triggers, the event list editor exposes these background commands instantly. Most DAWs also include filtering tools within the event list, enabling users to isolate specific types of messages—such as viewing only Pitch Bend data—and delete or transform them in bulk without affecting the surrounding musical notes.