[4.61] Multi-MIDI Editor quantize bugs (FIXED)

[Reaktor:[Dave]]

With this project file, you can start at step 4.

1. New project. Create two tracks with a midi item for each one.
2. Open the first item in the midi editor, set the grid to 1/16 and draw in some notes.
3. Open the second item in the midi editor, set the grid to 1/2 and draw in some notes.
4. Open both items in the midi editor, (check that both are editable) select all notes, change the grid to 1/32.
5. Select all notes and do "Edit->Quantize Events (Q)".
6. In the dialogue, select "Settings: Use Grid" and "Quantize: Position and note length".
7. Look at the quantized notes: only the active (green arrow) track has the correct note length of 1/32. The other notes are 1/16 long (bug).

Note: this bug is not only about quantizing note length, but also about other parameters like note start. Quantizing multiple midi items only works, if the grid has been set to the same size for all tracks you want to quantize.

There is another bug related to this:

1. Continue at step 7 in the list above. Make sure you didn't commit quantization.
2. Close the editor and open again all items.
3. quantization has been silently applied!

[Reaktor:[Dave]]

Bug Report #1: http://forum.cockos.com/project.php?issueid=5221
Bug Report #2: http://forum.cockos.com/project.php?issueid=5222

[Ollie]

I set the second part to confirmed, but I can't reproduce the first part. All selected events on all items are being quantized as set in the quantize dialog.

[Reaktor:[Dave]]

Can you try the supplied project file?
Did you set quantization to 1/32 and "Position and note length"?

[Tod]

Originally Posted by Reaktor:[Dave]

Can you try the supplied project file?
Did you set quantization to 1/32 and "Position and note length"?

It took some fiddling but I finally got around to some conclusions.

First of all you have 3 midi tracks not just two so I simply ignored the third track. Also the tracks were duplicates of each other and the notes were already quantized to 1/32nds. So I set the notes on the first track a whole step higher and then slightly shifted the notes off from the grid on both tracks.

I got varying results but in essence they would not quantize correctly unless they were set to the same grid size in the first place.

For the 2nd part of the test you're right, however it only quanized the 2nd track and not the first when I reopened the ME.

[Reaktor:[Dave]]

Originally Posted by Tod

Also the tracks were duplicates of each other and the notes were already quantized to 1/32nds. So I set the notes on the first track a whole step higher and then slightly shifted the notes off from the grid on both tracks.

Something is wrong. The notes should be different on each track (I just checked the linked project file). The beginning of all notes is quantized to 1/16. So to demonstrate the bug, the user has to change the grid to 1/32 (which changes the grid only for the active item) and to quantize "Position and note length", resulting in different lengths (but the lengths are supposed to be the same).

You could demonstrate this bug using off-grid notes, too.

I updated the steps reproducing this bug. In my first post.

[Reaktor:[Dave]]

Still unfixed in v5.20. Olli, would you mind checking my description on the first part again? This bug is simply annoying and slows me down when editing multiple midi items as I cannot batch quantize them but have to quantize them item by item.

[Dstruct]

Can't reproduce or confirm any of the posted issues here (5.201 x64).

[Reaktor:[Dave]]

It looks like bug #2 has been fixed.

And bug #1 is really just a misdescription. I was expecting the "quantize note length" to quantize the length to the grid instead of a multiple of the grid. Sorry for the confusion.

[Dstruct]

Ok, thanks!

[juliansader]

I can confirm #1:

It seems that when you quantize multiple tracks to "Grid", each track may be quantized differently: The events in each track are quantized to whatever grid value was applied when events were *last* drawn in that track, not to the MIDI editor's current grid setting.

(v5.22pre4)

[juliansader]

It seems that REAPER does indeed remember grid as a per-take setting, not a per-editor setting, since the relevant ReaScript function uses a take as argument, not an editor:

Lua: number retval, optional number swingOutOptional, optional number noteLenOutOptional reaper.MIDI_GetGrid(MediaItem_Take take)

Returns the most recent MIDI editor grid size for this MIDI take, in QN. Swing is between 0 and 1. Note length is 0 if it follows the grid size.

I guess it may sometimes be useful apply quantization on a per-take basis, but there should at least be an option in the Quantize dialog box to override the take's grid with the editor's current grid instead.

Perhaps the Settings dropdowns list should split "Use grid" into "Use editor grid" and "Use take grid"?

[juliansader]

Four years onward, and REAPER's Quantize -- one of the most basic, easiest MIDI functions -- still don't work properly.

Here is a GIF to demonstrate (each note is from a different track):



As I wrote above: "when you quantize multiple tracks to "Grid", each track may be quantized differently: The events in each track are quantized to whatever grid value was applied when events were *last* drawn in that track, not to the MIDI editor's current grid setting."

[Justin]

Fix coming soon!

[_Stevie_]

woop, thanks guys!!!

[Reaktor:[Dave]]

Great! :-)

This was driving me nuts.