MIDI Quantize question

I never quantize so this is just a guess.  It looks like using the "select controllers within note duration" option prior to selecting the notes to quantize might work. It will supposedly do what you want with a temporal (horizonatal) drag, so might work with an automated drag as in quantization.

In the quantize dialog box, if you uncheck "only noes and lyrics," Sonar is supposed to quantize controllers according to the documentation:
 
Other settings
If you want, you can restrict the types of events that are affected by the Quantize commands to only notes, lyrics, and audio clips. If you choose this option, SONAR will not modify other events, like controllers.

... The quantizer shuffles them into little groups overlapping each other.

It appears to vertically stack the values in any given quantize 'window', with the highest value taking precedence.

I don't know how else to describe it but it doesn't work like "I" think it should, so I guess I'll be doing it all by hand when I need to.

I've actually tried running a high-res external controller through a sample & hold module to get the results that I 'expect'.

The highest setting is only 1/32. Maybe if it had a higher setting...

You can enter a numerical 'tick' value to get the equivalent of smaller note increments.

I see.  You are using continuous controllers that have too many events per quarter note to quantize.
 
This probably won't help you, but I actually add pitch bend and volume swells by highlighting a specific range and inserting controllers.  That way the first and last messages are in the right place and the other values are distributed evenly.
 
The only problem is that Sonar puts in too many messages—like 8 per tick, which is ridiculous.  So, I highlight all the controller messages EXCEPT the first one and last one and then use then Thin Controller or Thin Pitch Wheel CAL.  I usually have to set the CAL program to remove every second event and, even then, I may run it 2 or 3 times.
 
You don't have to thin them out, but too many pitch bend messages can really bog down your CPU and I don't think anyone can hear the difference.
 
This is tedious but I have done it so many years that I have gotten pretty fast.  I already have ideas about how far ahead of the beat a pitch bend should start and how long after it should continue.  Few players end up on the final pitch exactly on the beat.  A lot of keyboard players using wheels tend to bend faster than a guitarist would.
 
 

soens, I agree completely with your point—I waish it worked like you say.  That is why I add controllers after the fact; but, of course, the disadvantage to my method is that it is programming and not playing which doesn't work for some people, especially in inspired moments.
 
Even though I grew up as a player and have many years of training, I have been using sequencers so long that I am just used to creating parts in event lists and on staves.