AAS Strum Session 2 and GS2 - Strum Speed Control Doesn't Work

I have enjoyed playing around with the Platinum-included Strum Acoustic 1 from AAS.  Not really convinced by the sounds but I liked the fact that I could create whole note keyboard chords and SA 1 would let me control the speed of the strum to include a slow, string-by-string flourish.  I used it mainly to just set the chord background while I built up my song.
 
With the newer Strum Session 2 (included in the latest update), the same control knob appears in the UI but I cannot get it to slow the strum down, even when I set the knob and the related "velocity" knob below it fully counterclockwise.  I've tried them both fully clockwise, as well as in every other position, and it does not seem to make a difference.  Is anyone else having this issue?
 
I then downloaded the fully functional demo version of the new strum GS2 after getting the promotional $49 offer, and I've run into the same problem.  I realize both newer versions have a more sophisticated "loop" function and wonder if this has somehow supplanted/overridden the slow strum, but the control knob is still there so I am stumped.  No matter what I do, all the strings play at once and I can't get the string-by-string slow strum.
 
Can someone please help cure my stupidity?  What am I missing?
 
Thanks,
Bill

Hi Bill,
 
I contacted AAS directly about this, and I posted about their response here,
 
http://forum.cakewalk.com/FindPost/3243094
 
cheers
 
andy

BRainbow
I contacted them too but no response yet due to the weekend/holiday. 

Ah... That's good.
 
I don't know why they couldn't provide a "switch" that could flip between two strum speed ranges. I personally don't use the loops so I would always choose the wider range...

WilliamHenley
It may not be your issue on the clock/speed of the strum. I've got both Sonar X3 & Platinum and I have the same issue with NI's Strummed Acoustics sync to Sonar. Sonar really doesn't seem to like being slaved or passing on the slaved midi clock to some vst's. You're not alone!

Perhaps a good way to test/verify is to run the standalone GS-2 app and check the strum speed range. If it's the same in SONAR and standalone, then there's no SONAR issue. If they're different, however, then there's an issue somewhere (but not over the rainbow).