Is it just me(very likely, it is, but I'm asking the board anyways), or are Sonar's options kind of a mess. I am learning to enjoy the software more and more, but the deeper I get, the more confused I get about the overlying -err, I dunno, philosophy?- philosophy of the layout. Like why this option is global, but that one is per project, or, like why this option has a button in the track options, but that button you have to go digging it out of Preferences, then you still gotta dig around to figure out whether it is global or per project and if it is per project then you gotta go and mess around with your Normal Template if you want it to stick.
 Before anyone feels compelled to tell me, I know that I can save at least a couple of those steps by making one of them opening the manual or help documents. My experience with computer programmes is not huge. My day job has me using off-the-shelf and turn-key windows software( email, a little bit of sign-making, SAP, MASS, ect ). My music hobby has me messing around with Ableton Live, Reaper, And Sonar. 
 I guess I should start trying to make my point here. Okay: Generally, dealing with computer programmes, when I need to change an option or preference, and I am not sure where it is, a lot of times I can find it simply by guessing " it's probably in with...(some other option or preference whose location I do know)". This is much more difficult with Sonar (worse now with X3, but still kinda wonky when I picked it up with 8.5).
 I am truly seeking guidance here. This is not a troll.
 
respek

I agree. Not to mention there are like three different screens where you make your basic audio driver settings. I always forget what's where.

Yeah they could probably do with some reorganization. The problem is that if they changed the options layout then they'd get the inevitable barrage of complaints along the lines of "I have used Sonar since the days of Cakewalk on DOS and now I can't even figure out how to reset my VST's" etc. 

 Thank you for your comment, Member Sanderxpander. While it is always nice to have people agreeing with me, what I am really trying to dig up here is: why?
 It seems like millions of computer programmes follow fairly closely a certain - err again, I dunno...windows logic?- windows logic, but Sonar works considerably differently. Maybe if I had worked with the programme through it's evolution from inception, to now, it would seem clearer.

Member Sharke touched on some of my last post while I was typing it.
 
 
 
minor grammar error corrected

Legacy support and bad decisions? I think it's really as simple as that, no offense to the bakers. Probably not the highest priority to "fix" either. But yeah some reorganizing would be nice.

I would love to see some way to save preferences as presets. You could save a lot of time.

Sanderxpander
Legacy support and bad decisions? I think it's really as simple as that, no offense to the bakers. Probably not the highest priority to "fix" either. But yeah some reorganizing would be nice.

 Yes, Legacy support. I am mildly curious to know more about this legacy that I sometimes feel put-upon to support. But to be as fair as I can to Cakewalk, I doubt a product of such high quality is the result of bad decision. I believe all decisions made are the best ones possible with the amount of information given, at the time the decision was forced. Or something.
 
@Member ampfixer: I'm with you. Is a "feature request" to Cakewalk for some kind of "Options Manager"(sounds kinda silly, I'll work on the name) likely to bear fruit?

I just mean something like putting the most common audio driver settings across three different menus. What may be a good decision from the developer's POV can still be a bad decision from the user's POV. But whatever, I think we all agree some reorganization would be useful :)

Hello,
 
Panu's duckbar may offer some assistance with menu layout.  I would suggest checking it out to see if it can help...IHTH