MIDI and notes
Is middle C C3 or C4? Check the MIDI number before transposing
A different octave label may describe the same MIDI note. Use a one-note file to separate display settings, actual transposition and instrument tuning.
Middle C can be labeled C3 or C4 depending on the software's display convention. Before transposing a part that appears to have moved an octave, check the MIDI note number. A different label can describe the same event.
This matters when you copy notes from a tutorial, move a part between DAWs, or ask an assistant to write a note by name. “Put it on C3” leaves more room for interpretation than “use MIDI note 60.”
Separate the event, the label and the sound
Three things are easy to confuse:
| Layer | What you are checking | What a difference could mean |
|---|---|---|
| MIDI event | The stored note number | A note was transposed or a different note was entered |
| Editor display | The name printed beside that note | The programs use different octave labels |
| Instrument output | The pitch you hear | Instrument tuning, sample mapping or pitch processing differs |
Check them in that order. Changing the event to compensate for a display difference changes the music you are sending to the instrument.
As a simple numerical example, a move from MIDI 60 to 72 is twelve semitones. Keeping the event at 60 while changing the editor's label is a different action. Write down both the number and the label while troubleshooting instead of treating the label as the whole result.
What Logic Pro's setting actually changes
Apple's General View settings guide documents Display Middle C As. Its C3 setting describes note 60 as C3; its C4 setting describes that same number as C4. The setting affects the description of notes in the editors.
Use that control to align the display with the convention you want to read. Do not move the region's notes merely to make a screenshot's octave name match.
The guide was checked on 10 October 2026. This is a documented setting, not a claim that we tested every Logic version or measured the defaults of other DAWs.
Use one known note to check a transfer
Download the MIDI note 60 file. We authored it directly for this lesson. It contains one note at velocity 90, starting at tick zero and lasting 480 ticks, with 480 ticks per quarter note. The tempo is 120 BPM and the meter is 4/4.
The file has no instrument selection, controller messages or pitch bend. Its event record gives you an independent reference for the expected note data. It is not a DAW export or an audio recording.
- Import it into a new scratch project, keeping any automatic transposition disabled.
- Inspect the note in an editor or event view. Record its displayed name and, wherever available, its numeric MIDI value.
- Assign a plain pitched instrument with a known tuning. Avoid a drum kit or a sampled phrase for this check.
- Repeat in the other application. Keep instrument and project transposition neutral.
- Compare the note data before comparing the sound.
If the labels differ while the numeric events remain 60, investigate display conventions first. If the events differ, inspect import, region and track transformations. If the events match but the sound differs, move downstream to the instruments.
The downloaded file is a known starting point. Opening it in an application is your check of that application's behavior; the file alone is not proof of compatibility with every DAW.
When it really is an octave problem
Keep a copy before changing anything. Find where the first difference appears: the source note, a region transform, a MIDI effect, or the instrument. Check one stage at a time.
For example, suppose an exported event is 60 but a re-export from the receiving application is 72. That gives you a concrete twelve-semitone difference to investigate. It still does not identify which import option or edit caused it.
If both files say 60, compare instrument settings. A pitched sample can be mapped with a different root note. A synth oscillator can have an octave offset. Those can change the result without changing the note stored in the clip. A drum map introduces another issue: the same number may trigger a different hit altogether.
Make the correction at the stage responsible for the difference. Otherwise you may compensate twice when a display or instrument setting changes later.
Give collaborators an unambiguous note reference
Instead of sending only “the bass begins on C3,” write “the first event is MIDI 48; my editor labels it C3.” Use the actual number and label from your project, and include a short audio reference when the sound matters.
The same practice helps with an assistant request. Specify the numeric pitch, which clip to edit, and which notes must stay unchanged. Inspect the returned notes before asking for the next change.
Once the pitch is settled, follow the MIDI and stems handoff checklist. It covers timing, instruments and audio references separately from the octave label.
Questions
- Is middle C C3 or C4 in Logic Pro?
- Logic Pro lets you choose how to display middle C. Apple's guide describes C3 and C4 settings for MIDI note 60. Changing that display convention is different from transposing a note.
- Should I transpose MIDI when the octave label changes in another DAW?
- Check the MIDI note number first. If both events are note 60, a different label alone does not justify transposing the part. If the numbers differ by 12, investigate an actual octave change.
- Can the same MIDI note number sound different on two instruments?
- Yes. Instrument tuning, oscillator pitch, sample mapping and pitch processing can change what you hear. Use the same known pitched sound and check those settings when comparing.
- What is in the downloadable middle-C example?
- One MIDI note numbered 60, velocity 90, starting at the beginning and lasting one quarter-note beat. The file includes a 120 BPM tempo and 4/4 meter. It contains no instrument, audio or pitch-bend events.