midi in quantization

• Jun 4, 2017 - 10:19

I'm experimenting with the newly released 2.1.

I tried the midi-in feature, and I get results I don't understand. Can someone tell me if I'm doing something wrong, or whether this is a bug.

The maximum quantization is set to 1/16, yet the midi-in creates nodes 1/64 rests.
Even when I press the apply button again with the 1/16 settings, I don't see any difference
in the results.
I'm attaching a screen shot of what I see, and also the midi file i'm using as input.

Screen Shot 2017-06-04 at 11.15.00.png


In reply to by jim.newton.562

I agree. In my case, I want the quantization to have a minimum of 32nd notes. However, in MS 3.1, the greatest quantization of an imported live midi file still leaves 128th notes and rests? In order to make the imported midi readable by humans I have to use another midi program to quantize. There needs to be greater control of midi quantization in MS.

The below image shows quantization in MS set at 32nd note with "is human performance" checked. (it doesn't look very quantized):

Attachment Size

In reply to by Sambaji

I've made a feature request in the tracker: #290687: Provide option to set "quantization fraction" in midi import.

For those who want "readable" notation from live non-quantized midi files, I suggest using a program like MidiEditor first (https://www.midieditor.org/), which is free. In MidiEditor, under tools, set the quantization fraction to 32nd or 16th, select all, quantify selection, and then save us. Now the file is ready for import to Musescore. To compare the results check out the tracker issue submission above.

Hi, i discovered, if you import the midi-file and tick "is human performance" (in midi-import-dialog), the notes are displayed correctly as you desired.
So, no need for the feature request ?

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