When conveyed by a MIDI file: MS 3.6 / 3.7 / 4.4.2 unisons of equal durations have unequal durations in my DAW
MIDI files exported from MuseScore 3.6, 3.7 or MSS4.4.2 are sometimes peppered with very short notes that interfere with playback in my DAW.
When a single staff in museScore file contains unison notes, and I export to MIDI, and then import the MIDI file to my DAW (Logic Pro X) I find that one unison is the expected length but the other is a very short blip ... with the correct aligned onset time.
Unknown matters include:
• if MuseScore 3 is exporting MIDI incorrectly
• if my DAW is generating the issue when I import the MIDI file
Here's my test score:
Exporting unision notes to a MIDI file SUTB.mscz
And this is the MIDI file it exports
Exporting unision notes to a 3-7 MIDI file SUTB.mid
Bringing the issue to the light of day
I can reveal the blips in my DAW's piano roll editor by selecting the notes of proper duration and dragging them up one semitone, as shown:
NOTE: I haven't tested the behavior when unisons are on different staves.
scorster
Comments
After exporting to MIDI from MSS4.4 I encounter the same result when opening the MIDI file in Logic Pro X:
• one normal length unison
• one short blip unison note—exactly as reported above.
This odd unison pairing occurs in Logic Pro X ... at the location of each unison in the MuseScore source score (i.e. at beat 1 of measures 1, 2, 3 & 4.)
The source score is the same as the one originally posted above. I simply opened it in MSS 4.4.2 and exported via File>Export>MIDI:
Exporting unision notes to a MIDI file SUTB.mscz
scorster
Would someone please open the MIDI file in a DAW—other than Logic Pro—and check to see if the unisons import as I've described?
scorster
In reply to Would someone please open… by scorster
MIDI in your post on https://tonejs.github.io/Midi/
![Capture.PNG]( "Capture.PNG")