Understand the columns
MIDI middle C is note 60. Start and duration are seconds from the beginning of the clip. Velocity is an integer from 1 to 127; it changes playback strength, not the measured loudness of an original instrument.
Round-trip corrections
Copy the note rows, change a pitch or start time, and generate a new MIDI. The exporter writes a fixed 120 BPM map so seconds remain consistent. Changing a DAW tempo afterward can stretch those events unless you preserve absolute time.
Separate repeated notes if the tracker merged them. Keep positive durations and check that note overlaps are intentional. The CSV workflow accepts up to 2,000 events and ten minutes of timing.
A concrete correction example
Suppose the table contains 64,1.20,0.35,90 but the intended note is F4 held for half a second. Change that row to 65,1.20,0.50,90. Choose Create MIDI from corrected note rows, paste the complete table, and run again. The MIDI pitch changes by one semitone while the note still begins 1.20 seconds after the clip starts.
A repeated note needs two rows, even when the pitch is identical. For two C4 notes, use 60,0,0.40,90 and 60,0.50,0.40,90. The 0.10-second gap separates the attacks. An accidental overlap can instead make a synthesizer sustain a voice longer than expected. Listen after editing; a visually tidy table can still produce an unintended articulation.
Keep an editable source
Save the corrected CSV beside the MIDI. The standard file contains note-on and note-off events plus a fixed tempo map, but it does not retain your original audio or editing notes. This exporter uses 480 ticks per quarter note at 120 BPM, giving 960 ticks per second. Times are rounded to that grid, so sub-millisecond changes may round to the same event position.