A request to the bakers who deal with documentation -- this could have been *a lot* easier to figure out.
I searched the online help for "auto scroll" and read through all nine hits. The only relevant only advice was to use the Left Click Locks Scroll option; there was no mention of the Scroll Lock key. So I searched the Hopkinton PDF manual for "auto scroll." The only occurrences were on page 448 :
"To enable/disable auto scroll lock: Click the Track view Options menu, point to Click Behavior and choose Left Click Locks Scroll on the submenu."
and something echoing this on page 1739. Again, no mention of the scroll lock button option.
Now, if I'd already known the answer, and searched the PDF for "scroll lock", you'd have to go to page 1325, which mentions it in a Staff View context, and then finally, if you want to know about non-Staff View, you have to go on to page p. 1539 of the manual:
"The SCROLL LOCK key toggles whether or not SONAR scrolls during playback."
Eureka ... well, we got there in the end...
But sorry, but page 1539 is just buried. While in retrospect, scroll lock is an obvious answer, well
a) ymmv; as the years go by, fewer and fewer apps I use make much important use of old IBM keys like ScrLock and PrintScr, so they're quite on my periphery; and
b) if it's so obvious, perhaps it should have been stated -- like many other "obvious" things -- somewhere higher up in the manual / help file. I personally would suggest mentioning the Scroll Lock key method in the same places that you mention the Left Click Locks Scroll method. Keeps things organised by topic, from a user's point of view.
I know this sounds petty, but as someone who really tries to consult the online help, the manual (both of which are usually pretty great), google, videos etc
before posting a query, I get really annoyed when something so basic is made so obscure. It leads to an unneccessary downtime and forays on the stop-start-headscratch-wtf-doh! cycle. If I'd had no internet access today, I might still be facing downtime, or postponing what I wanted to do until I could ask here. Shouldn't have to be this way -- the bundled documentation should do the trick.