If a long MIDI note sounds from its beginning but stays silent when you start halfway through it, playback is skipping its start. In GarageBand for Mac, begin before the note, create a new note onset, or use an exported audio version for later-position listening.
Why can a visible MIDI note be silent?
A MIDI region contains instructions for an instrument rather than recorded sound. Apple makes this distinction in its guide to importing audio and MIDI files. A long bar in the editor therefore represents a note’s timing and duration; it does not contain a continuous audio recording that playback can enter anywhere.
The symptom described here is consistent with missing the note’s starting event. Apple explicitly explains in its Logic Pro Chase Events documentation that MIDI notes beginning before the playback position may not be heard. Logic Pro can look backward for those events using MIDI chase. That explains the mechanism, but its settings instructions belong to Logic Pro.
For GarageBand, treat that explanation as a diagnostic hypothesis: if the same note plays when playback crosses its beginning and remains silent when playback starts inside it, the starting position is the meaningful difference. This article addresses that specific outcome on a Mac.
Confirm that playback starts inside the note
Double-click the affected MIDI region to open the Piano Roll Editor. Apple documents this editor as a time grid containing colored bars for MIDI notes. Inspect the individual note’s left edge, rather than relying on the region’s outer boundary. See Intro to the Piano Roll Editor.
Use this illustrative arrangement to understand the test; these are synthetic notes, not measured results:
| Event | Start | End |
|---|---|---|
| Long note C4 | Bar 2, beat 1 | Bar 6, beat 1 |
| Short note E4 | Bar 6, beat 1 | Bar 6, beat 2 |
| First playback test | Bar 1 | Continue through bar 6 |
| Second playback test | Bar 4 | Continue through bar 6 |
First start before bar 2 and listen through the long note. Then stop, place the playhead at bar 4, and start again. To position it, click the lower part of the ruler. For more precise placement, Apple also documents entering a position in the LCD. See Move the playhead.
If C4 sounds in the first test, disappears in the second, and E4 still sounds at bar 6, that pattern supports the missed-start explanation. If neither note sounds even when playback begins before both, this particular diagnosis is insufficient. Establish that the notes can play normally before changing their timing.
Does GarageBand have a documented MIDI chase switch?
Apple’s current GarageBand for Mac guide does not document a user-selectable MIDI note chase control. Its Audio/MIDI settings page describes device selection, Audio Units, MIDI driver reset, and controller selection; it provides no note chase procedure.
The documented boundary matters: Reset MIDI Drivers reloads MIDI devices after a lost connection. Apple does not describe it as a way to recover a note whose beginning precedes playback. Likewise, the File > Project Settings > MIDI and Chase procedure appears in the Logic Pro guide, so it should not be presented as a GarageBand menu path.
This documentation supports a practical limit: there is no Apple-documented GarageBand switch to recommend for automatic mid-note triggering. The supported GarageBand paths below either include the original onset, change the note data, or turn the rendered result into audio.
Keep the long note intact by starting earlier
For checking the original uninterrupted note, move playback before its left edge. You only need to go far enough back to include the relevant note beginnings; returning to the project’s beginning is unnecessary when all required notes start later.
For repeated listening, use a cycle range that includes those beginnings:
- Press
Cor click theCyclebutton. - Drag across the upper part of the ruler to define the range.
- Place its left boundary before the earliest note you need to hear.
- Extend its right boundary beyond the passage you are checking.
- Start playback before that earliest note and listen through the passage.
Apple documents moving the yellow cycle strip and resizing either edge in Use the cycle area. Positioning its start before the note is the application of those controls to this problem; Apple does not describe cycle mode as a MIDI chase feature.
In the synthetic example, a cycle beginning at bar 1 includes C4’s onset at bar 2. A cycle beginning at bar 4 omits it. With several overlapping long notes, inspect all their left edges and include the earliest required onset. This preserves the existing note arrangement while making repeated checks predictable.
Create a new onset when a fresh note is acceptable
If you want the instrument to begin a new note at bar 4, edit the MIDI data explicitly. First save a separate project copy if you want to retain the uninterrupted version for comparison.
For the synthetic C4 example:
- In the
Piano Roll Editor, select C4 and drag its right edge back to bar 4. Command-clickthe C4 row at bar 4 to add another note.- Drag the new note’s right edge to bar 6.
- Check that both notes remain on the same pitch row and meet at the intended boundary.
- Start playback just before bar 4 to audition the new onset.
Apple documents Command-click insertion in Add notes in the Piano Roll Editor, and edge dragging in Edit notes in the Piano Roll Editor.
You have now written two notes. This creates a deliberate restart at the boundary; it does not reconstruct the original long note’s already-developed sound. Compare playback across that join before keeping the edit. Also inspect for accidental gaps, overlaps, or pitch changes.
Why splitting the region needs an extra check
A region split is not a documented promise to preserve a continuous note while making it playable from every later position. Apple states that notes at a MIDI region’s split point are shortened there. It also describes a conditional dialog offering choices to keep, shorten, or split notes. See Split regions.
To split, select the intended region in the Tracks area, position the playhead, then choose Edit > Split Regions at Playhead. Afterwards, reopen the resulting MIDI regions and inspect the note bars. Verify whether a note actually begins at the desired restart point. Do not assume the dialog always appears or that dividing the region alone produces the note arrangement you intended.
Use rendered audio for listening from later positions
When the task is to inspect a later portion of the existing sound, an audio version is useful. Apple explicitly supports exporting instruments and effects to an audio file and reimporting that file. This gives you a rendered result to inspect without asking a software instrument to recover an earlier MIDI onset.
For a straightforward full-project reference:
- Keep the original MIDI arrangement intact.
- Choose
Share > Export Song to Disk. - Choose a location and select
AIFForWAVE. - Leave
Export cycle area, or length of selected regions (if Cycle is turned off)unchecked to export the entire project. - Click
Exportand listen to the result before using it as your reference.
These controls and formats are documented in Export songs to disk or iCloud. Exporting the complete project includes the earlier note beginnings rather than defining a range that starts inside them. Apple also states that leading and trailing silence is trimmed, so verify alignment before placing the export alongside existing tracks.
To bring the file back, drag it from the Finder onto an audio track or the empty area below the existing tracks, following Import audio and MIDI files. Audition the rendered version by itself when comparing it with the original.
Rendering fixes the sound into audio. Keep the MIDI project for subsequent changes to pitches, note lengths, or instrument choices, and export again after those changes. The audio reference serves a different editing purpose from the original note data.
Choose the approach that matches the listening task
| What you need | Best-fitting approach | What to check |
|---|---|---|
| Hear the original uninterrupted note | Start before its onset | Include every required overlapping note |
| Repeat a passage without editing notes | Begin the cycle before the relevant onsets | Confirm the left cycle boundary |
| Hear a fresh note at a chosen boundary | Add an explicit new note onset | Listen across the new join |
| Inspect a rendered passage from later positions | Export audio and reimport it | Verify sound and timeline alignment |
| Automatically recover earlier MIDI events | No GarageBand procedure is documented by Apple | Keep Logic Pro chase instructions separate |
Begin with the earlier-start test. If it confirms that playback is skipping the long note’s beginning, choose whether to preserve the uninterrupted note, write a fresh onset, or listen to a rendered audio reference. That decision resolves the editing task without relying on an undocumented GarageBand setting.
Sources
- Import audio and MIDI files in GarageBand on Mac — Apple
- Use the Chase Events function in Logic Pro for Mac — Apple
- Intro to the Piano Roll Editor in GarageBand on Mac — Apple
- Move the playhead in GarageBand on Mac — Apple
- Change Audio/MIDI settings in GarageBand on Mac — Apple
- Use the cycle area in GarageBand on Mac — Apple
- Add notes in the Piano Roll Editor in GarageBand on Mac — Apple
- Edit notes in the Piano Roll Editor in GarageBand on Mac — Apple
- Split regions in GarageBand on Mac — Apple
- Export songs to disk or iCloud from GarageBand on Mac — Apple