I love this thread. Really? "Very disturbing" that an indicator tick isn't present? Is it really breaking your tranquility and causing anxiety? The way I'm looking at it, it adds one-click to your workflow. 
 

...wicked
I love this thread. Really? "Very disturbing" that an indicator tick isn't present? Is it really breaking your tranquility and causing anxiety? The way I'm looking at it, it adds one-click to your workflow.

 
We're all entitled to our opinions and wishes. It may add one click more, but the checkmarks are utilized in other areas without problems. It's the principle of the matter. And like others, we all wish longtime bugs are finally squashed on current releases and patches.

But your hyperbole is laughably out of proportion. Srsly, "very disturbing"? Are you really "very disturbed"? Like the same level of anxiety when you find out a serial killer is loose in your neighborhood? Your points are fine, your rhetoric is the kind that makes people not take any of this crap srsly.

2:43AM
#2.  If Sonar is running on a dual-monitor setup, where the Track View and Multi-Dock/Console View are displayed separately, and Sonar is minimized, then upon reclick to foreground (i.e. re-maximize), the second monitor's display (in this example, the Multi-Dock) reappears not in fullscreen; it merely reopens in a small window, specifically a window 280x1279 pixels. So did Cakewalk fix this issue? NOTE: this may be a Windows vs. floating-window issue, inherent to a program running in the Windows environment, and therefore no fix or workaround is possible.
[Problem report submitted on 6/18/13; submitted to development -- CWBRN-17792].

I can't say if this is a Windows issue or peculiar to Sonar (although experiences in other software seem to say it's Windows) however...
 
There is a workaround. Don't maximize the window on screen #2, use the resize gadget to make it full screen. Minimize/maximize will now open both windows to their original sizes. This should work in X2 as well, BTW.

2:43AM#3.  For some reason, Sonar seems to forget VST and VSTi layouts in the Browser upon opening projects or starting new templates. Sometimes I need to select "Default All Plug-ins," then reselect my own Layout from time to time. It seems rather inconsistent and intermittent, but I don't think it's just me. So is this still an issue?

 
I'm assuming you're talking about the FX bin for this on...
This hasn't happened to me in X3. And with the VST/plugin manager, you can get very fine control apparently. I haven't tried it yet, so can't say if it works as advertised.
 

2:43AM#4.  Perhaps I am missing something easy, but I always thought if I right-clicked an audio clip, I could select an effect to apply to it. For example, if I wanted to normalize a clip, I could right-click on it and select "Normalize" from a "Process" menu. However, the only way to do it, as far as I know, is to go to the top of the screen's Process Menu and select Apply Effect. I think it's been this way since the beginning of Sonar, but that doesn't mean it couldn't be improved. So has this optimized trick/feature been added??

 
In X3, the clip-based context menu does have a Process Effect submenu, but the items in that submenu are the same as the FX bin, not the main window's Process menu.
 

2:43AM#6.  Oh, BTW, can the EQ be removed from the ProChannel strip?  In X2, it could never be removed.?

 
I don't see any way to do this, but you can disable and collapse it.

2:43AM#7.  Also, can values for knob parameters be manually entered in any ProChannel module other than the EQ??

 
No.
 
Hope this helps at least a little.
 

I don't know that I agree that just because there happens to be a vertical bar down the left side of the window that it was intentionally put there to hold some sort of selection indicator. 
 
That said, it WOULD be a great place to put a check mark, little dot, or whatever to indicate that an option was selected.  If not that, maybe a bold face of the selected item or maybe even a little popup with a "less cryptic" version in a little popup window.
 
I haven't looked at any of these issues, just wanted to drop my opinion on this, same way I wish someone would have added input to my issues with midi remote control not quite working! Not bitter or anything :)

Blades
I don't know that I agree that just because there happens to be a vertical bar down the left side of the window that it was intentionally put there to hold some sort of selection indicator.

 
Yes, it's a guess on my part, but if you compare the Sends drop-down menu to all other menus utilizing the check mark (e.g. MIDI ch. #, MIDI patch, MIDI I/O, audio I/O, etc.), they are all the same menu type and style. Therefore, one could only surmise that the Sends menu would (or should have) followed suit.
 

Blades
Not bitter or anything :)

 
You mean you're not "very disturbed?" "Srsly?"

2:43AM

Bristol_Jonesey
8 - Never seen this in any version of Sonar. Envelopes have always worked fine for me.

 
I am currently working on a project and the volume envelope basically died on the vine. It became unresponsive and did not send any volume increases/decreases to the track's respective fader; only moving the nodes manually with the mouse caused a change on the fader. Automation READ was on. I don't know what causes it exactly, and it usually occurs after working a project for a long time. Whatever it is, it happens. In X3, it would be nice to know that envelopes can be beaten to near-death but still remain intact and 100% functional.

You didn't activate Envelope Offset mode by accident and this is the reason why the faders doesn't react to envelopes? You activate/deactivate offset mode by pressing "o".
 
It's a great feature if you for example have created an advanced automation and later want to increase or decrease the overall volume of a track without having to redo the automation. It woks for pan as well.

Regarding check's for used sends, they are not used because multiple tracks or buses can use the same send. Normally checks are used in menus when the item is a "radio choice" which doesnt really apply in this case. 
Re #3 I know there were several fixes made in X3 and the updates for plugin layouts so pretty sure it should be addressed.
#5 - manual text entry applies to only built in modules like the compressor eq and tube saturation where the UI is drawn by SONAR.

Noel Borthwick [Cakewalk]
Regarding check's for used sends, they are not used because multiple tracks or buses can use the same send. Normally checks are used in menus when the item is a "radio choice" which doesnt really apply in this case. 
 

 
Hmm......this isn't very user-friendly, is it?