Is this a bug or am I missing something?
(Cubase Pro 12.0.51)
When I record midi within a key editor, with Auto Quantize turned on (via the “Automatic MIDI Record Quantize” button in the transport bar), it can be reset afterwards using either “Edit>Reset Quantize” or (in the left zone) “Quantize>Reset Quantize”. Perfect.
But if I record midi directly in the Project Window “Edit>Reset Quantize” doesn’t seem to work. Yes, I have highlighted the midi part first. It’s as if the “Auto Quantize” also applies “Freeze MIDI Quantize”.
I find no comments about this, which makes me wonder if I have missed something important.
Here (0.70) it’s working as expected. With Auto Quantize on, we can then Reset Quantize and we’re back to the raw midi recording. I’m using AQ a lot, and since I many times accidentally have the quantize value set to a “wrong” one, I always use the Reset Quantize with no problem in all versions so far.
It was a good suggestion to update to the latest version. Unfortunately, it didn’t solve the problem.
However, I have now narrowed it down even further.
In the project window. It actually works if I record a new part with auto quantized midi. This is possible to reset. But if I record auto quantized midi into an already existing part, this cannot be reset.
Is there something I am missing? A setting, or something else, that can be turned on or off?
I guess as Martin most probably suspects, you’re using the merge mode.
Based on my testing here, when we record upon an existing part in merge mode, the notes of the first parts are affected by reset quantize while the new ones are not.
Same thing happens if we record in cycle mix mode a second layer after a stop.
If nothing went wrong with my testing, I think that this could be considered a bug unless of course there is an underlying logic for this behaviour. @Martin.Jirsak most probably knows a lot more on this.
Anyway, this issue is not there when we have midi mode set to new parts, after all, we can always merge these parts to one when finished with our editing. Actually this is how I work and this is why I never noticed this issue.