Midi File import creating multiple parts from monophonic input - again

• Feb 12, 2025 - 03:17

I tried updating a previous post about this, but that seems to result in no replies, so I'm creating a new topic repeating an old problem...

Original thread: https://musescore.org/en/node/374262

Basically, Musescore is splitting what I think is a monophonic midi file into two parts. 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

Comments

Here is s the chapter on implode: https://musescore.org/en/handbook/4/implode-and-explode

When you implode two staffs they will be merged into different voices in the same (upper) staff. But if you then implode it again, the two voices will be, wherever possible, merged into one voice.

What version of MuseScore did you use for importing the midi file? The behavior in MuseScore 3.6 is different from MuseScore 4.x . the 3.6 version gives you much more control over the import and you can then save the file and open it in MuseScore 4. Both versions can be installed at the same time in your computer.

There are several ways.
In this score, cut and paste is the easiest method - but you have to edit the measures individually.

And those funny marks are rests in voice 1 that can't be deleted. Select all the notes and press the key for voice 1. Now these rests have disappeared, but a lot of eighth-note rests and quarter-note rests in voice 2 have appeared. You can delete these rests by clicking on one with the left mouse button and selecting “Similar” and pressing 'Del'.

By the way: MIDI is not the optimal format for file input. It almost always requires reworking...

In reply to by HildeK

Actually, other than this issue of splitting onto staves, I find this is a great and musical way to get notation going. Musescore interprets the input surprisingly well. I can play the phrases in realtime, quantize and make some edits in Logic, and then import it. I feels much more musical than popping back and forth from "eighth note mode" to "quarter note mode" in Musescore. I find the normal modes of input in Musescore pretty awkward. I've tried various things and some are better, but none are good IMO. I've made suggestions about a better note entry mode. I would explore the semi realtime input modes more, but in version 4 the keyboard latency is absolutely horrible on my Mac (200 mSec!!), which makes it pointless. It's all a shame, because it's clear to me from how well Musescore does at interpreting midi input that there is no reason for Musescore not to support realtime input, since it is basically the same thing. I tried a cheaper version of Dorico, and its interpretation of realtime input wasn't as good as Musescore's interpretation of midi files.

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