Realtime quantize is on.
And ‘record midi output’ option is designated.
1 Like
Hi,
Your Grid is not set to the Bars+Beats, it’s set to Second and the Tempo is not 120 BPM.
Hi thanks.
I think it’s clear the grid is set to Bars+Beats (19.1, 19.2, 19.3, 19.4…)
And how can you ascertain the tempo - and why would tempo matter anyway?
I can say, for sure, that the notes are not aligning to the grid via using input transformer Quantizer and setting it behind the midi output record dotted line.
Another example: you can clearly see the offset of the notes printed on the grid – and they are all apparently offset by the same amount.
Please test this.
If this is the case - is this a deviation from intended operation? Is it a bug?
Are you using this plugin?
This plugin does not change the notes how they get recorded onto a track. It only changes how they are being output.
When the option “Real Time Quantize” is off only the midi played back from the track is quantized, if it is on also the midi thru will get quantized. But the quantize happens only after it would be recorded onto a track.
If you want the midi input to be quantized before the midi hits the track, use AQ (auto quantize) instead, please.
It needs to be set up to be visible:
I’m aware of AQ.
Sorry to say, you are wrong about this one.
A simple test using the Quantizer midi input plugin will show you that neither the notes recorded on the track nor their output playback aligns to the grid while using this plugin.
It is also a little strange how each note is offset by what looks to be the same amount (except the very first). I tried to turn off ‘adjust for record latency’ as that’s the only option I could think of that may be relevant, but it didn’t make a difference.
I believe the midi insert plugins should be recorded as they affect the notes when the dotted bar is moved below the insert in the relevant section:
I am glad we finally managed to get you to explain exactly what you were doing. A precise description of the issue is really helpful.
Yes, when the Quantizer midi plugin is used and is on a “to be recorded” slot then I also get a delay of all notes.
@Martin.Jirsak : The delay is 6 ticks with PPQ=480 (tested with PPQ=960, the delay is 12 ticks). It is 288 samples with 48kHz saample rate.
Additionally (but another issue): When Realtime Quantize is switched off, the Quantizer does not have any effect anymore at all when it is a “to be recorded” plugin.
3 Likes
Thanks for including the supporting info.
I think the Quantizer plugin is behaving buggy.
Confirmed. Good catch.
I used a YAMAHA USB MIDI cable and set up a loopback like this;
Then I created a MIDI track with 16th note events, played it through the loopback, and recorded to a VSTi track. When the quantizer is enabled, the recorded MIDI notes are consistently offset — in this case, by 2 ticks.
Though I think it’s more of an oversight. I don’t believe this plugin was ever intended for recording — traditionally, “AQ” is used in such cases. It could be fixed, but perhaps not easily, since it would need to operate ahead of time, like PDC for buffered plugins — and I’m not sure such functionality exists for MIDI insert effects.
We all know the workaround is to just press “Q” after recording, which isn’t that difficult. 
Well spotted, though.