So - I think there is some confusion on this from folks who think that W or RTZ is the same thing as Rewind. If it were, there wouldn't have been such a "call for" or a "big deal made of" the Rewind and FF buttons in the Transport as a very granular, cassette tape-like function.
To my knowledge, there is no key binding for this. Why? Who knows? Seems like it would have been a natural thing to add in, even for the people who want to use FF and RW from a Control surface.
The closest things I have to offer are ctrl-pageUp and ctrl-pageDown, which go forward and back by measure or the CAL script mentioned below for forward and back by beat (assuming 1/4 notes), which looks like this for Rewind (based on 960ppq) - both of which can be saved as .cal files in the CAL folder and then attached as key bindings:
(if (>= Now 960)
(-= Now 960)
(= Now 0)
)
and this for FF:
(do
(+= Now 960)
)
So now the somewhat, but not completely off-topic rant...
I have a Contour Shuttle Pro (v1) that used to work for at least a beat forward and back function when it was released, which was before there was a FF and RW button in the transport. I have a Tranzport (Frontier Design - now defunct), an Edirol PCR-800 and a Behringer BF-2000. Those three devices allow for forward and back by beat or measure depending on the settings, and even work for this when Focus is outside of the Sonar window. I suppose this is because those devices are using an API of some sort.The Contour does not. The Tranzport doesn't do Pause because it has hard-coded button functions and as far as I can tell, they can't be changed.
I have a CAL script that mostly works for forward and back by beat for a key binding, which I can then attach to the Contour, but it is a little fiddly because sometimes it just doesn't work and even when it does, it goes forward and back by a number of tics, so if you are between beats, it is pretty literal, and goes from 100tics before one beat to 100tics before the next, etc.
The whole thing seems poor to me. Two of these devices (the Contour and the Edirol) are items I bought because of their inherent Cakewalk/Sonar support, one purchased directly from Cakewalk in their Store and the other purchased because it was made by the parent company. It has since been replaced with the Roland A-xxx line, but no matter, since Cakewalk is no longer Roland's. So, the Edirol doesn't technically support Windows 10 (though I've made it work) and the Contour lost its "plugin" when the X series of Sonar came along.
For the PCR-800, which is really a pretty nice KB, the ACT functions aren't great for me and the few places where I do want such things, like for midi remote control of Sonar-native knobs and switches, they don't work because of bugs. ACT itself is fiddly and feels abandoned and should be REALLY easy with a device such as this one, but it's even weird to figure out even with it's dedicated Dynamic Mapping button that apparently does nothing with any software except Sonar, specifically designed to engage with ACT. Since there is a PCR-300 choice in the control surfaces, you might expect there would be a nicely laid out graphic UI or something for this line, but no - it uses the generic ACT stuff, which is odd and awkward to use.
Have I gone a bit off-track from rewind - certainly. But this is what happens when I get in front of Sonar lately - I find reasons to rant - often because the features like this one have been strangely neglected for SO many versions. But hey, there's Lenses! :)
Anyone have more input on any of THESE related items? Hope this at least helps in some way!