Are there any shortcut keys you can set up to control the position of Sonar's playhead?
I can't seem to find out where these are.  I just use the mouse all the time.

eg:  move the play head two measures back...  etc

Ctrl+Page Up and Ctrl+Page Down will move now time forward or back one measure (works in playback mode too).

Ctrl+Page Up and Ctrl+Page Down will move now time forward or back one measure (works in playback mode too).

 
Those are probably the two I use the most.
 
You can also set the "nudge" values in Preferences.

I use a Mackie Control to scroll the now time. 

since it is CAL week for me. I have a couple of keys bound to simple CAL scripts to slide Now forward and backward.

;; Name: Now Forward.CAL
(do
 (+= Now 30)
)
 
and

;; Name: Now Backward.CAL
(do
 (int offset 30)
 (if (< Now offset)
  (= Now 0)
     (-= Now offset)
 )
)

scook


since it is CAL week for me. I have a couple of keys bound to simple CAL scripts to slide Now forward and backward.

;; Name: Now Forward.CAL
(do
 (+= Now 30)
)
 
and

;; Name: Now Backward.CAL
(do
 (int offset 30)
 (if (< Now offset)
  (= Now 0)
     (-= Now offset)
 )
)

Is it also possible to move the now time to a marker using CAL and create a keyboard shortcut like if you press Num1 it jumps to the first marker?
I hope your CAL week continues... :) 

Hey @scook - I know that this is OLD post, but a while back I adapted this script for forward and backward by beat (960 instead of 30) and then assigned that to the Ring on my Contour Shuttle Pro.  It works ok, though it can be a little bit fiddly.
 
So now I got the new CbB version and I'm trying to use the very same CAL to do it there and while it works, there is an oddity that I don't understand.  I verified that it is a problem when bound to a key command as well (which is basically all the Contour Shuttle is firing at this point anyway since the Cakewalk plugin stopped working for this ages ago).
 
Can you try to bind this command to a key and then hold down that key and see what you get?  I used to get a Now time that moved across the screen and worked like the FF or RW keys, except at "beat" resolution.  Same with what would usually be ctrl+PageUp and ctrl+PageDown (for by measure).  The by measure works smoothly.  The CAL script doesn't.
 
Instead of seeing the data fly by, you just see it doing nothing until the key is released and then you are magically transported to the point in time that aligns with how long you help the key.
 
Another oddity that I've found: If I start a brand new song (from a template I have with the same track and plugin layout I typically use), it works fine, no matter how fast I ask it to go.  If I open an older song (made with SPLAT), I get varying degrees of success from - works as long as I don't hit the keys too fast (ala Contour Ring held all the way to one side = hit key "as fast as possible") but as soon as I get to too fast, it goes to the "I can't process the video for your request" and stops working.
 
If I close CbB and open SPLAT and open the exact same "old" song, the Contour and CAL work exactly as expected.
 
I doesn't seem that anything in CbB would have changed to affect this, yet here I am with this strange issue.
 
Not sure why this would behave this way.

Hmmm.  Update: maybe it's not as exclusive as shown above.  I can't nail down exactly where the differences are.  It's definitely after a certain "key presses per second" that is fails to show the progress.

I found what the distinguishing characteristic seems to be: Is the Console view open.  If that is not open, it works perfectly.  If it is open, whether it is the focus or not, the CAL script doesn't update the screen right.
 
In SPLAT - it doesn't make any difference, whereas in CbB it makes ALL the difference.  I have settings from Shuttle In Left 7 - 7 then Right 7-1 - so there are 14 positions.  Each one allows for a different speed that the key is pressed.  In Patinum, I have the max at 60 times per second that the key is pressed.  In CbB if I have it about about 30, whether the console is open or not, it's a problem.
 
Strange.  Not workable since I have the console open a LOT.
 
And as a matter of pricinpal - I thought nothing like this would have changed with this release of CbB.  I'm on the SPLAT 2017.10 release or the new CbB one.
 
 

I doubt I would have noticed any of this. I do not use the console view or special input device.