Groove Quantize is doing strange things

I'm using SONAR Platinum v22.7.0 BUILD 41 [2016.07]  and tested on Windows 10 Pro 1511 32bit and 64bit.
 
I'm trying to copy the velocity of a MIDI Hi-Hat pattern, so I can use it as a Groove Quantize.
 
The reference clip is 2 measures and contains 16 8th note Closed Hi-Hats and each note is quantized 100% Strength and the durations are all 480.
 
The velocities are: 127 - 71 - 90 - 71 - 90 - 71 - 90 - 71 - 90 - 71 - 90 - 71 - 90 - 71 - 90 - 71
 
I have an identical clip except all the velocities are 127 and I want to apply the reference clip's velocity as a Groove Quantize.
 
I select the Reference clip and copy it. I select the 2nd clip and then go to Process menu > Groove Quantize...
Groove File: < Clipboard >
Groove Pattern: Blank
Resolution: 1/8
Sensitivity: 100%
If Outside Window: Quantize to Resolution
None of the 3 boxes are selected
Time: Off
Duration: Off
Velocity: 100
 
Click OK
 
The 2nd clip now has an extra 16th note added to the end of it and it's Velocity is all wrong: 90 - 71 - 90 - 71 - 90 - 71 - 90 - 71 - 127 - 127 - 71 - 90 - 71 - 90 - 71 - 90 - 16th note = 127
 
I tried applying the same reference clip to a similar clip but with all Kicks and the same thing happened. An extra note was added to the end and all the velocities are wrong. If I keep trying the same thing, the velocities are different every time.
 
I even tried just selecting the notes in the PRV instead of selecting the clips and had the same results.
 
Am I doing something incorrect or is there a work around?

I recently got a strange bug, not with Groove quantize, but with the velocity change feature. I wanted to reduce the velocity of all notes in a clip, with a 80 % factor.
 
SONAR did the job BUT also duplicated the first events of the following clip. For example (I don't remember), the clip I was working on was from 40:01:000 to the end of 43, and SONAR took the events which were at 44:01:000 and duplicated them! I had twice the same note and twice the same CC at 44:01:000.
 
Maybe the problem was that my MIDI clip was a suite of perfectly quantized chords, so the notes were just stopping where the events at 44:01:000 were beginning. I don't know if that's the reason why SONAR was confused.
 
SONAR is awesome but I think that its historical weakness is about "batch" operations, when you want to modify series of events at once. There are some bugs.