Midi import splits single melody to separate voices

• Oct 28, 2024 - 20:25

Hi! I'm a producer, I use Logic or ableton to work, and then I used to work with finale to transform the midi files to scores. I'm new to MuseScore and I'm trying to do the same, but when I import the singe melody midi file, it gets split into two voices. How can I disable this setting please? Here's the file

Attachment Size
chuzalongo.mid 3.04 KB

Comments

• Oct 28, 2024 - 22:01

It even gets split into three voices (1.blue, 2.green, 3.orange) This is possible with version 3 (e.g. 3.6.2, the last one), see GIF below.

  1. In the MIDI Import panel, in the "Max.Voices" tab, set to 1 voice
  2. Click on "Apply". And you're done.

This is not currently possible with version 4, simply because the MIDI import panel has not been retained (at this stage of V4 development anyway)

Video_ voices.gif

  • Another possibility: a plugin, "Merge Voices, is currently being finalized that does a similar job. The most advanced version (1.1) is here (https://musescore.org/en/node/370074#comment-1265129) But in a few days, I suppose, the final version will be available.
    Also only works for version 3, for other reasons.

Reply

• Oct 29, 2024 - 05:06

Thanks @Cadiz1

All true. When importing MIDI MS3 is better capable and more flexible than MS4. On the path to MS4 the number of features stripped from v3 is staggering; most supposed lost for only a temporary period of time, but it's getting close to two years now.

I checked the OP's MIDI file in Logic's Event List Editor and indeed all notes are in Channel 1.

Indeed I find it peculiar that MS4 thinks it needs to splay MIDI data into separate voices ... the only justification is that some notes have a slight overlap. But that would not be an issue if MS4 acknowledged the LEN property.

If I were MuseScore 4 I'd beg developers to reinstate the LEN property!

With the LEN property restored in MS4 MIDI import could be straightforward:

    • MS4 could determine note face values evaluating the onset point of a NoteON and and the point of the next note in the MIDI file
    • all notes in the score could remain on their native channel
    • all MuseScore play durations could precisely match their DAW origins

Net result:

    • intelligent, readable notation that needs no revision
    • playback quality that matches the detail and fidelity found in the app that generated the MIDI file

Reply

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