I have problems with CPU Conservation Mode. I use other software that uses Break button as global Windows shortcut. It is maybe only one button that could be used such way. And sometimes when I start Sonar it is already in CPU Conservation Mode, I don't know why. The third-party application is set to exclude Sonar, but it works such way that Break doesn't work in Sonar. So I find myself in CPU Conservation Mode, and can't switch it off. So I go to third-party application, exit it, disable CPU Conservation Mode, and have to remember to start third-party application later.
I did some research, made heavily loaded project and tried to figure out if CPU Conservation Mode does something useful. And what? Nothing! It really does nothing with CPU power (at least on my PC). The project's sound starts glitching and dropout occurs exactly the same with or without CPU Conservation Mode. So why is it exist at all? This completely harmful function could be easily eliminated.
If I'm wrong, and on some setups it could be really useful, and there is at least few people who use it, it should remain, but there is absolutely must be an option to completely disable this function, and this option should be enabled by default.

While waiting for Cakewalk to implement this idea, consider using autohotkey or similar product to trap the BREAK key when SONAR has focus. Like this:
#If WinActive("ahk_exe SONARPLT.exe")
Break:: Return
#If

Thank you, I'll try it. But as I've said, third-party application already block break, but somehow Sonar sometimes starts already in CPU Conservation Mode. I don't know how and why it happens, maybe when I press break during Sonar loading or before it, but I can't reproduce it.
My point is that this function is useless and harmful, so it should be eliminated or hidden.

If SONAR is starting in CPU Conservation Mode, it is because the break key state is already set. IOW, the other software while using the BREAK key as a shortcut is still setting the state in the OS. You can confirm this with a simple autohotkey script, in this example I bound the script to Windows-B:
#b::
  GetKeyState, s, Break, T
  MsgBox, %s%
  Return

Have NO idea what ur talking about and the suggested fixes... if this is an issue, especially with us power users who've invested in decent CPUs...would be nice to fix it so dummies like me aren't left with less than optimal systems... but still have no idea what ur going on about... but as the mighty scook has chimed in, I'll assume it's an issue worth fixing.
 

Vastman
Have NO idea what ur talking about and the suggested fixes... if this is an issue, especially with us power users who've invested in decent CPUs...would be nice to fix it so dummies like me aren't left with less than optimal systems... but still have no idea what ur going on about... but as the mighty scook has chimed in, I'll assume it's an issue worth fixing.

That can sound dangerous, but it is not. It is Sonar (not hardware, not windows) mode which reduce the number of graphic updates in Sonar in attempt to free a bit more resources for music:
https://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=AudioPerformance.21.html
 
Also in case you do not use Pause key with some other program (for example, I have never used such programs), this discussion is not relevant for your setup

azslow3, formally you are right, but...
1. There is no confirmation that this mode can really improve CPU performance. When I tried to use it, it didn't help at all.
2. Break could be accidentally clicked, and if somebody is not aware of this feature, it could make some trouble. So it makes Sonar less friendly to novice users.

Adq
azslow3, formally you are right, but...
1. There is no confirmation that this mode can really improve CPU performance. When I tried to use it, it didn't help at all.

That is (hardware) system dependent, especially graphics. On top system it is impossible to notices.
 

2. Break could be accidentally clicked, and if somebody is not aware of this feature, it could make some trouble. So it makes Sonar less friendly to novice users.

Most keyboard keys are mapped to some function in Sonar. The effect from some of them is not easy to spot. So "Accidentally" pressing random keys is a bad idea when using Sonar, this particular "break" key is harmless for the workflow (no changes in sound, no changes in project).
 
As a request, I only support a possibility to change/remove any mapping. There are (too) many hardcoded combinations, which are not even listed in the key mapping. And that in general can confuse novice users.

Well I had no idea about this until today so thanks for bring it up.

http://www.cakewalk.com/D...dioPerformance.21.html

If you have issues with glitches and dropouts etc I would hope more into the root cause rather than rely on this functionality.

Updating audio interface drivers and firmware for audio interface and display, doing a motherboard bios and chipset update, Running windows update. Doing a defrag. Seeing what happens with your virus scanner on and off. Disabling your network adapter, running latencymon, upping your buffers etc. Making sure min/Max for CPU is set for 100% in the control panel power management. Updating your plugins (getting rid of 32 bit), optimizing your project for load..

azslow3
That is (hardware) system dependent, especially graphics. On top system it is impossible to notices.

My system is far from top, q6600 CPU, HD5450 video. So it is doubtable. I'm still not sure if there is real system where it matters, or if someone really uses it.

azslow3
As a request, I only support a possibility to change/remove any mapping. There are (too) many hardcoded combinations, which are not even listed in the key mapping. And that in general can confuse novice users.

Not listed? Here is what in the list:
Space
Scroll Lock
Pause
Ctrl, Alt and Shift combinations with Pause, I have no idea what they do.
Do you mean something else?
Scroll Lock can be problem for novice users too.