MIDI Export Perpetual Note
Was about halfway through a piece I was transcribing on Musescore 2.1 when the 2.2 update came out. Switched, no issues whatsoever on the Musescore front. Playback is wonderful, et cetera. One of the things I like to do with my pieces is do a MIDI export into Synthesia to determine if I have an issue regarding overlapping notes or chords that require arpeggio-ing to play. I noticed something rather concerning, though: starting at measure 17, there are a few notes that, when exported as a MIDI, seem to never end. You can see in this screenshot of the Synthesia software:
Also attached is the clipped segment of the score where the issue exists- exporting this segment to MIDI reproduces the issue- and a copy of the MIDI itself that demonstrates the issue.
| Attachment | Size |
|---|---|
| MIDI export error.mscz | 16.96 KB |
| MIDI export error.mid | 1.37 KB |
Comments
Could be a duplicate of https://musescore.org/en/node/270783 but here, I cannot reproduce the problem in the application.
In reply to Could be a duplicate of… by mirabilos
Try taking the provided score, exporting to MIDI, and then re-importing the MIDI file into Musescore. The issue appears plain as day. Just tried it myself with the MIDI file I provided above- you can see a note in the second voice that continues through the remainder of the score.
I should also probably clarify- I was exporting the score to MIDI while working on it with version 2.1 as well, and it exported fine then. This is specific to 2.2.
In reply to Could be a duplicate of… by mirabilos
Except that there it is also measure 17 where the trouble starts I don't think these have something in common
In reply to Except that there it is also… by Jojo-Schmitz
Now I see that you're doing a lot with fermatas and their time stretch property. Uploading a score here with hiding invisible stuff is not nice ;-)
And indeed on midi ex- and then import I see that long sustained note.
you could try @mirabilos' attempt to fix this be taking https://ci.appveyor.com/project/MuseScore/musescore/build/1.0.876/artif… (but careful, it'd overwrite the current 2.2 install. or even require to uninstall that first)
In reply to Could be a duplicate of… by mirabilos
I now know why I could not reproduce it: I tested with a build that had PR#3551 (which caused #270562) applied instead of PR#3560 to fix #270408, but this issue was only caused by PR#3560… anyway, we’ve got a fix now in PR#3588 (for the lifetime of the code in PR#3560).
To note, I've noticed it with the MIDI export for other files as well, for files started in 2.2. Not sure what's going on here.
Probably the same problem as https://musescore.org/en/node/270869 too
This report is indeed the same than https://musescore.org/en/node/270869 but they are different from https://musescore.org/en/node/270783
Here we are only talking about Piano and MIDI export. In this case, I believe we shouldn't try to be smart. The two staves are exported to two different midi tracks and the majority of MIDI players (and in particular, synthesia, which seems to be a major destination for MIDI files) will take care of the overlapping events.
I filed an issue: #270878: [Regression] MIDI fixup for overlapping note shouldn't kick in for different midi tracks
In reply to This report is indeed the… by [DELETED] 5
Oh, so the issue is the overlapping MIDI events? Makes complete sense; I usually handle those myself using the pianoroll editor, but it gets more difficult to identify them when dealing with multiple staves.
At the very least, now I can resolve the issue on my own end. Thanks!
In reply to Oh, so the issue is the… by LuuBluum
The issue is actually in the code intended to make the overlapping MIDI events not overlap. The proper fix is, of course, to assign separate channels to separate voices, but that’s currently not easy.
The good news is, though, we have a fix: https://musescore.org/en/node/270878#comment-827502