MIDI Middle C Octave Numbering in DAWs

While all Digital Audio Workstations (DAWs) agree that MIDI note number 60 represents the pitch of Middle C (approximately 261.63 Hz), they do not agree on how to label that note's octave. Depending on the software, MIDI note 60 is designated as C3, C4, or C5. This discrepancy stems from conflicting historical hardware standards rather than software bugs, yet it frequently causes confusion during cross-platform collaboration, hardware sequencing, and virtual instrument keyswitching.

The Origin of the Discrepancy

The MIDI Manufacturers Association (MMA) established the MIDI specification to assign note numbers from 0 to 127, defining note 60 as Middle C. However, the MMA never formalized an octave labeling scheme.

This omission led competing synthesizer manufacturers to establish their own conventions:

• Yamaha Standard (C3): Yamaha chose to designate MIDI note 0 as C-2. Counting upward, MIDI note 60 becomes C3.
• Roland Standard (C4): Roland followed Scientific Pitch Notation (SPN), designating MIDI note 0 as C-1. This makes MIDI note 60 C4.
• Alternate Systems (C5): Other developers chose to avoid negative octave numbers entirely, designating MIDI note 0 as C0. Consequently, MIDI note 60 becomes C5.

Because modern DAWs inherited different lineage from these hardware eras, these conventions persist today.

Middle C Across Major DAWs

DAWs typically adopt one of the three established conventions by default:

• Ableton Live (C3): Ableton adheres strictly to the Yamaha standard, displaying MIDI note 60 as C3.
• Steinberg Cubase and Nuendo (C3): Cubase defaults to C3, reflecting Steinberg's historical ties with Yamaha, though newer versions offer display options to alter this view.
• Apple Logic Pro (C3 or C4): Logic Pro historically defaulted to C3, but allows users to toggle the display between C3 and C4 in its display preferences to match Scientific Pitch Notation.
• Avid Pro Tools (C4): Pro Tools adheres to Scientific Pitch Notation and the Roland standard, consistently labeling note 60 as C4.
• Cockos REAPER (C4): REAPER defaults to C4, but provides a user-definable MIDI octave offset setting in its preferences.
• PreSonus Studio One (C3 or C4): Studio One provides a setting to switch between octave naming conventions, often defaulting to C3 or C4 depending on the version.
• Image-Line FL Studio (C5): FL Studio designates MIDI note 0 as C0, making Middle C (note 60) appear as C5 in the Piano Roll.

Practical Impact on Production Workflows

Because standard MIDI files (.mid) encode musical data as raw pitch integers (0–127) rather than text strings like "C3," transferring a MIDI file between two different DAWs will play the correct audio frequencies. However, the visual representation changes, causing specific operational challenges:

Virtual Instrument Keyswitches

Sample libraries (such as those hosted in Native Instruments Kontakt, Spitfire Audio, or Vienna Symphonic Library) rely on keyswitches—notes outside the playable range of an instrument used to trigger articulations like legato, staccato, or pizzicato. If a library manual states that a keyswitch is located at C0, an Ableton user (Yamaha standard) and a Pro Tools user (Roland standard) will play different physical MIDI notes if they rely solely on the named pitch, causing the articulation to fail.

Hardware Synthesizer Patch Management

External synthesizers often follow their manufacturer's specific naming standard. Triggering a patch change or drum map mapped to "C1" on an external Roland drum machine from a DAW set to C3 will result in a one-octave offset unless adjusted.

Resolving Naming Conflicts

To avoid octave-related issues across different environments:

1. Rely on MIDI Note Numbers: When documenting articulation maps, sample triggers, or keyswitches for other producers, specify the absolute MIDI note number (e.g., Note 60) rather than the octave name.
2. Configure Display Preferences: If your DAW supports it (such as Logic Pro, Cubase, or REAPER), adjust the MIDI display offset in the preferences menu to match the primary standard used by your collaborators or most frequently used sample libraries.
3. Calibrate by Ear: When mapping keyswitches manually, verify triggering via incoming MIDI monitor plugins to ensure the correct internal integer is transmitted regardless of the interface label.