Midi File Display

• May 18, 2021 - 20:29

Why does Musescore display some Midis so badly when Anvil Studio can display the same files properly. Is there any workaround for this?

Comments

• May 19, 2021 - 16:26

Turning MIDI into music notation is AI, and there is no such thing as the "proper" display - MIDI is not notation, period. If for one particular MIDI file, Anvil's guess as to to the best way to display it happens to meet your needs, great! For other, MsueScore's guess might be better. but again, MIDI isn't notation, so it's always just guesswork. if you attach a MIDI file you'd like to see rendered differently, attach it here and someone can advise you as to what settings might help.

Reply

• May 19, 2021 - 21:52

Can you show a screenshot of what Anvil shows for the piano here?

Because looking at your midi file there's not much off with anything else at all during import. Try setting the maximal voices to 1 for example and not check split staff for the piano during import. You can then after import right-click the piano staff and choose a pitch as split point.

Reply

• May 19, 2021 - 22:49

They are both unreadable messes. Anvil indeed makes more deliberately inaccurate representations in an effort to simplify than MuseScore does by default. But your best starting point here would be to take that MIDI file and quantize it in a sequence or DAW, especially with an eye toward removing the unnecessary overlaps.

Reply

• May 19, 2021 - 23:02

Try this:

  1. During import limit the piano to 2 voices and disable split staff and clef changes. Also check "human performance"
  2. Right-click the staff and split it at C4
  3. Select each staff and for each do:
    • Select the staff
    • Press the voice 1 button
    • Select the staff
    • Implode

  4. Add brace and connect barlines

    greengrass-piano.png

Reply

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