Problem with quantizing -> Notes & CC (FIXED)

[TheWhistler]

I have made some animated gifs to point attention to a problem with quantization AND its handling of CCs.

In this first animation everything as it should be.
I grab the note and it moves. The CC data moves along to the note, fine.


Now it s getting complicated.
I wanted to quantize the note to half notes.
The note moves, but the CC data does not....hm.
It is kind of ok, because I did only "selected notes" in the quantize dialogue. So seems to be normal.



But I want to move my CCs along to my note, of course (think of some filter modulation)
So I used selected events, because I want to move the controller data to move along with my note.

BUT !!! The controller data is quantized not moved (of course this is what I have selected)



Is there a way to overcome this?
Can a note be quantized and not only moved by hand with REAPER respecting the relative positons of notes and e.g. CC-data that is in the range of the corresponding note?

Maybe this is of interest to a lot of Midi-users. If not possible atm, this is really worth a feature request, isn´t it?

[MikComposer]

It would be tricky. There is planty wrong with the editor, but in this case Mod wheel data isn't really tide in any way to notes. How one would go about it when there would be a lot of notes to quantize? For each note it would have to select corresponding cc data within the length of the note itself, and move. Then, if one would select changing the notes length too, it would have to remember starting position of the notes, then quantize and move the note, then from recorded position select the cc data of original note's length, then squeeze it or expand it trough an algorithm, and then move it to the new starting position of the note. So yes, absolutely doable and it would be nice to have. Just needs to remember to put a toggle button in the quantize pop up so there would be some control over this.

[TheWhistler]

Originally Posted by MikComposer

It would be tricky. There is planty wrong with the editor, but in this case Mod wheel data isn't really tide in any way to notes. How one would go about it when there would be a lot of notes to quantize? For each note it would have to select corresponding cc data within the length of the note itself, and move. Then, if one would select changing the notes length too, it would have to remember starting position of the notes, then quantize and move the note, then from recorded position select the cc data of original note's length, then squeeze it or expand it trough an algorithm, and then move it to the new starting position of the note. So yes, absolutely doable and it would be nice to have. Just needs to remember to put a toggle button in the quantize pop up so there would be some control over this.

I understand what you mean. How shall REAPER know which cc-data belongs to which note...hm.

I would insist on a toggle for "move cc-data with note while quantizing".
So it is switchable if wanted.

Or one could grab a couple of cc-data an the whole bunch of data gets processed.
So the realtive positions to each of the single cc-events would be kept.
With the first selected event to be the reference point.

[clynos]

This would be great.

[fundorin]

Originally Posted by TheWhistler

I understand what you mean. How shall REAPER know which cc-data belongs to which note...hm.

It already knows. As can be seen in the first GIF, related CC data is also being moved when the note is moved with mouse.
I've tried to find a usable workaround for years. No progress, though.

[d. gauss]

Same problem here. VERY frustrating. no way to do this? i uses superior drummer with an electronic drum kit and cc4 is the hi hat pedal openess control. like OP's GIF above, i can manually move the hi hat midi note and all associated cc4 data follows it, but using quantize either mushes all the cc onto a beat (useless) or doesn't move at all (terrible) depending upon the chosen quantize settings.

[d. gauss]

bump. anybody?

[d. gauss]

bump. really? no one uses v-drums with reaper and dealt with the mess that is cc hi hat data and note quantize?

[juliansader]

This would be very helpful for anyone that needs to quantize notes after CC curves have already been drawn.

There is also an older FR thread at Quantize and CC follows.

[d. gauss]

so frustrating. when you manually move a note, all the cc data follows along with it. i don't get why CC won't follow note (maintaining the same relationships) when using quantize.

[d. gauss]

bump. devs? anybody?

[juliansader]

Notation issues get fixed much faster than piano roll bugs, so if you can report this issue as a notation bug in the Bug Reports subforum, you may get the devs' attention.

Come to think of it, this may genuinely be more of a problem for composers that prefer to only work in notation, since they may not notice that the notes and CCs become misaligned after quantizing.

[d. gauss]

bumping this

[d. gauss]

bump. anyone?

[LugNut]

Hi,
The new version of Motu Digital Performer has this feature.

[d. gauss]

reaper should, too.

[mccrabney]

+1, yet another reason i don't use recorded ccs much in REAPER

[Dex]

Originally Posted by TheWhistler

I understand what you mean. How shall REAPER know which cc-data belongs to which note...hm.

It’s not too hard to come up with a working solution. CC data goes with any selected note that it overlaps with, and gets moved the same distance as the note does. If there are multiple overlapping notes for a CC event then that event gets moved the overall average amount the notes get moved.

That’s where I’d start. Maybe someone can code it up?

[_Stevie_]

Solved in reaper5971+dev0225

[d. gauss]

Originally Posted by _Stevie_

Solved in reaper5971+dev0225

did it make it into 5972? didn't see it in RC relase notes (though i may have missed)

[_Stevie_]

Good question! Most of the dev stuff doesn't make it in the pre. I think stuff will get merged later on. That's why I'm always using devs. Drives me crazy to use Reaper without global hotkey override.

[d. gauss]

anyone know for sure?

[schwa]

This fix is not in 5.972, but will be back in the next prerelease and should be in the next official release after 5.972.

[TheWhistler]

Originally Posted by schwa

This fix is not in 5.972, but will be back in the next prerelease and should be in the next official release after 5.972.

Yes please, ultemately. So important. Kissing your feet.....

[d. gauss]

Originally Posted by schwa

This fix is not in 5.972, but will be back in the next prerelease and should be in the next official release after 5.972.

didn't see it listed in the 5.973rc pre-release changelog...perhaps i missed it?

[schwa]

It was in the development (+dev) builds that were posted over the past week, but we wanted to get 5.973 out sooner for a bugfix. The feature will be back in the next +dev build.

[d. gauss]

Originally Posted by schwa

It was in the development (+dev) builds that were posted over the past week, but we wanted to get 5.973 out sooner for a bugfix. The feature will be back in the next +dev build.

so v5.974 has it? wasn't sure by the changelog description.

[schwa]

Originally Posted by d. gauss

so v5.974 has it? wasn't sure by the changelog description.

Yes, it's this:

+ MIDI: obey editor toolbar preference for CC following notes when quantizing notes only [t=172470]

[Klangfarben]

Silly question. In the dev version, where is the pref for this?

Also, is there a pref for moving/scaling CC when trimming note lengths?

Currently using dev0329a

[_Stevie_]

Originally Posted by Klangfarben

Also, is there a pref for moving/scaling CC when trimming note lengths?

don't think so, but this would be wonderful!