Midi file imports as non monophonic, when part is monophonic, how to repair?

• Jan 22, 2025 - 03:41

I've recently discovered the utility of importing midi files as a time saver for note entering. But my most recent example is importing as if there are parallel parts, even though the midi file clearly has no notes that overlap in time. Why might this be? In any case, I can't figure out how to get rid of the "parallel rests" in bars 3 and 4 without getting rid of the notes. How do I do this?

I'm including a screenshot as PDF, plus the midi file

Attachment Size
example clip.pdf 110.01 KB
Jump Transition.mid 649 bytes

Comments

In reply to by jandymanvoelk

Actually, this triggered me to try restarting Musescore 4, rather than just closing the file and re-opening the MIDI file (which I had fixed to make sure there were no overlapping notes). The problem went away! This seem to indicate that Musescore 4 was somehow "caching" the original midi file even after I fixed it.

In reply to by bobjp

I am running into this problem again. I've included what I see when I open the midi file, and the midi file itself. I checked very carefully for any overlapping notes, even used a feature in Logic Pro which ensure overlapping notes. It's a monophonic part. Yet it gets split into two separate parts on import.

How can I figure out what is going on here?

Also, when I use "Implode" to try to merge the content, I get these funny markers I can't remove. What is that, and is there another way to easily merge the parts onto one staff?

Attachment Size
Imported Midi Image.png 119.37 KB
Revelation.mid 1005 bytes
Funny Top Markings.png 55.78 KB

Do you still have an unanswered question? Please log in first to post your question.