• SONAR
  • Manuals for instruments/FX/whatever, F1 and general access to necessary info.
2015/08/02 11:08:58
Beepster
This gets brought up every so often but I want to sort it out once and for all.
 
F1 to open manuals for synths and stuff is dicey on my system. Sometimes it works, sometimes it doesn't. Sometimes things have a help button (which again sometimes works and sometimes not).
 
I keep a PDF copy of all documentation I can scrounge up on various things on my laptop but I also what to access things the old fashion way when needed (F1 or whatever) because I have no idea where those "additional" type manuals are stored and I don't necessarily want to scour everything and transfer them over (especially the shorter ones for things I don't use a lot).
 
So what's the trick(s) here? I do not keep my DAW online and have things set to use the Offline manual locally.
 
Essentially I'd like to hear any and all strategies for fixing F1, scouring my system for the local documention and whatever else I can do to find these friggen' manuals.
 
Example (and this is just an example): I was mucking around with the Roland Groovesynth. I wanted to find something specific about what the MIDI note reference was (on my controller I was having go down two octaves to get a C2 drum sound to play at what is C0 on my controller). Not a big deal. Just curious. There's no help button. I hit F1... nothing. I'm pretty sure there is a manual for it but damned if I can find it.
 
So yeah... this is a thread about scrounging for local docs. All ideas, experiences, methods, tricks, tips, links, locations, whatever completely welcome.
 
Also... it would be nice if Cake started a searchable online repository for EVERYTHING Cakewalk. Make it only accessible to paid customers via their store accounts if need be (but I'm of the mind allowing the world to see your manuals encourage legit sales more than help pirates).
 
Back to giving myself a synth headache.
 
Cheers.
2015/08/02 11:25:03
scook
The only help on the website is the main SONAR help which is the SONAR.chm and "Reference Guide.pdf" locally. All the other documentation is installed locally, often with the plug-ins. There are exceptions though. The fastest way to find it is scan for pdf and chm files. The only one that I recall w/ html help is TTS-1. The CW synths which were sold separately, DPro, Rapture and z3ta+ put documentation in the content folder, the default being "c:\Program Files\Cakewalk\[synthName]\Documentation." Third party plug-ins have their own way to install help (if any).
2015/08/02 12:29:31
Beepster
Okay, cool and thanks. Is there a known solution to the "F1" issue? I recall sorting this out or reading a solution to that at one point but that was ages ago.
 
It's always been hit or miss and maybe, if I did fix it at one point, it has been reset with the upgrades.
 
Awesome as always, Mr. scook. You're a treasure.
 
Cheers.
2015/08/02 12:42:19
scook
Depends on the plug-in. Even among the Cakewalk manufactured plug-ins, there is no consistent treatment of F1. Some simply require the plug-in be in focus. Some require actually clicking in the UI before F1 works properly. There is no requirement in Windows that F1 do anything and some plug-ins do just that. Plug-ins with pdf based help usually do not respond to F1. Some have a menu option to load the pdf.
2015/08/02 13:07:30
Beepster
Okay, so here is something crazy. I'm currently messing around with Cyclone. I made sure I click on an actual pad (which would normally trigger a sound if I had one loaded) THEN clicked F1.
 
There was quick flash in the upper right quadrant of the screen like a help screen was trying to load. Just a flash of the outline but nothing in it (in fact where the text/content would be was transparent and Sonar was vidible underneath so just the outline of the help window). It flashes for less that a second and it's gone.
 
I have never seen that happen before. Odd.
2015/08/02 13:59:29
scook
I do the same and the Cyclone help opens behind SONAR and takes up the full screen. The help text is readable when I bring the screen to the top.
2015/08/02 14:10:28
Beepster
scook
I do the same and the Cyclone help opens behind SONAR and takes up the full screen. The help text is readable when I bring the screen to the top.




Aha! Yeah, I had checked the taskbar and did not see anything indicating that there was a hidden window. When I hovered over the SPlat icon and the open window list popped out the Cyclone manual was available. Clicked on that and it came to the surface.
 
Welp, there's that solved I guess. I would normally expect that "paged" type graphic for the icon (like I get with multiple folders or browser windows open) but perhaps due to my screen res it isn't visible.
 
Thanks. Hopefully this woks for all the other goodies.
 
Cheers.
2015/08/02 14:17:20
Beepster
Well now... this is actually pretty cool. I'm not sure whether this has been going on forever and I was totally ignoratn of it or they changed something but now as I poke around various areas in Sonar, click on something (like the Inspector or Track View) then hit F1 I get a context appropriate help window. I am almost positive that was NOT happening before.
 
But with THOSE windows they appear over top of everything unlike the Cyclone help menu.
 
Freaky.
 
This is why I posted this. There seem to be almost Easter Egg style tricks to this context sensitive Help stuff.
 
That is brilliant scook. Thanks muchly. Any other insights about this for dum dum Beeps? You know I try ever so hard... just kind of a dum dum. lol
 
2015/08/02 14:25:04
Beepster
BTW... Cyclone is kind of annoying me. It seems very picky about what files it'll accept. I know that I can/need to convert the files I actually want to use if they don't load (so really anything can work but you gotta screw with it in loop constructor) but it is a bit of a pain. The MIDI message mapping thing is kind of a pain too. Probably why, even though in theory this thing is cool, nobody really talks about it.
 
It really doesn't handle the hard stops well either. Causes pops. Kind of figured there would be an auto fade for that (or maybe there is and I just haven't figured it out yet).
 
Still interesting to mess with.
2015/08/03 08:50:37
mudgel
Context sensitive help has been around for ages in Sonar. You know, click in the Console press F1 and get Console help etc. click on A Sonar plugin press F1 and get help for that plugin if there is any. Select Notation press F1, you get my drift. I mention it in just about every answer when I give people help about a function.

I can't remember a Sonar version where that wasn't the case. It's a pretty standard Windows operation for programs. Eg works in MSWord, Excel etc.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account