midi in quantization
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.
| Attachment | Size |
|---|---|
| Screen Shot 2017-06-04 at 11.15.00.png | 261.09 KB |
| IMSLP202871-WIMA.4d2b-AL99(I)Sco.mid | 49.47 KB |
Comments
What should it do with those notes? They are different pitches, so no way to combine them
In reply to What should it do with those by Jojo-Schmitz
Perhaps I misunderstand, but I'd expect that the notes would be rounded to 16ths as requested but the settings. What does 1/16 quantization mean? That means rather than a 1/64th rest followed by a dotted 1/32 note, I should simply have a 1/16th note. Right?
Here is the original score.
![Screen Shot 2017-06-04 at 11.27.31.png]( "Screen Shot 2017-06-04 at 11.27.31.png")
In reply to Perhaps I misunderstand, but 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):
![BAIAO_midiimport32ndnote.png]()
In reply to I agree. In my case, I want… 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 ?
In reply to Hi, i discovered, if you… by Pentatonus
Hi, did you test it with the midi file I provided? It doesn't work for me. The image is of the score imported with "Is human performance".
In reply to Did you test it with the… by Sambaji
Yes i did. But i'm on Musescore 3.1!
In reply to Yes i did. But i'm on… by Pentatonus
Besides the other version of MuseScore, your "is human performance" is NOT checked in the picture!?
In reply to Besides the other version of… by Pentatonus
In reply to [inline:Midiimport.png] by Pentatonus
Your are confusing me, Sambaji, with the original poster, jim.newton.562. I don't have the import midi panel even showing in my images. I am using MS 3.1 as well. Test out the BAIAO.MID and FREVO.MID file (see above and attachment) and you'll see what I am talking about.
In reply to Your are confusing me,… by Sambaji
Sorry, it was too late yesterday evening (night).