Recent Posts

Pages: 1 2 [3] 4 5 ... 10
When an application changes its own settings, or the power profile in this case, Process Lasso doesn't try to fight with it. Instead, Process Lasso makes a one-time change.

'Options / Forced mode' (near the bottom) can relieve the conflict with many settings, but not in the case of power plans. The code needs adjusted to allow for forced mode with regard to power plans. This is something I'll consider going forward.

For the time being, it is simplest to disable CuBase's set of its custom power profile.
I installed Prozess Lasso today as service.
I added also Steinbergs Cubase to the list of applications for which Performance Mode shall be enabled.
Cubase also has an internal option to set its own energy profile "Steinberg Audio Power".

I would have expected now that Process Lasso has precedence over the applications power profile setting and finally activates "Performance Mode" for the system. But this doesn't happen. In Process Lasso Window I see still "Steinberg Audio Power" enabled. And it stays even when I rightclick the Application and assign manually "Application Power Profile -> Bitsum Highest Performance".

As normal user I can change the Power profile with my Win7 Gadget that you already know and then balanced mode or energy saving mode is being displayed in the Process Lasso GUI as current power profile.

So by this I validated that Cubase does not instantly change back to its own power profile.

Question, why does Process Lasso Pro not properly set the Power Profile
a) automatically, because I added the path to the Cubase executeble properly to the list of designated high performance processes
b) after manually assigning the process Cubase9.5.exe "Bitsum Highest Performance" as Application Power Profile (rightclick with mouse to process)

Other check when disabling Cubase own power Profile: Bitsum highest Performance properly kicks in, if I configure Cubase not to use its own power profile which does different things including deactivation of CPU core parking. I wonder, why this deactication in Cubase is necessary. For my understanding Cubase only sets it one time on startup (otherwise I could not change it as user successfully with the power gadget) and then everything should be under the control of Process Lasso Pro.

Would be very nice if you could have a view on this, many thanks.
Process Lasso / Re: 9.1. performance mode settings do not work 100% anymore
« Last post by ranko on June 08, 2019, 04:22:15 PM »
Ok, many thanks.
Process Lasso / Re: Stock settings
« Last post by Jeremy Collake on June 07, 2019, 05:13:01 PM »
Simply uninstall Process lasso and reboot your computer.

Alternatively, use 'Options / Restore settings to defaults' and reboot your computer.
Thanks for the work and info diagnosing this! It is good that it doesn't happen on your Windows 10 install.

We'll get to running those tests in Windows 7 and see if we can reproduce.
Process Lasso / Stock settings
« Last post by cherylbusby on June 06, 2019, 11:30:12 PM »
is there a way to put everything back before I dabbled into it .
Process Lasso / Re: 9.1. performance mode settings do not work 100% anymore
« Last post by ranko on June 06, 2019, 01:53:41 PM »
Good news, I could validate under Windows 7, that my Power Gadget from orbmu2k works fine. It seems to have a fix compiled in update interval of 1 (or maybe 2) seconds.
During these 3-4 set of tests the error didn't show up. I had this already a couple of times where I thought I couldn't reproduce but then of all sudding it was still there.

For my testing I moved the gadget over the HW Monitor Pro screen close to the actual clock values to be able to validate, that a state change happens in both tools.

This means to me that I can rely on the power gadget and that my issues here are not based on a wrong status display of the gadget.
And in the past I never saw a deviation that moving the mouse for a long time didn't change the status.
So I think there could be an issue under Win7.
Process Lasso / Re: 9.1. performance mode settings do not work 100% anymore
« Last post by ranko on June 06, 2019, 01:32:32 PM »
Under Win10 I could not reproduce the issue.

I am using btw this power monitoring gadget under both systems:

Under Win10 I got the idea and added a 2nd gadget tool - Systemmonitor II from the 8Gadget suite - which also monitors the energy power state
and found out that there is sometimes a deviation in status updates of up to 8 seconds with Systemmonitor II. But not always.

This puts up the question, whether my sidebar gadget from orbmu2k (which up to now worked flawlessly under Win7) MAYBE also has deviations.

I am thinking now how I can double check with a 2nd status tool whether my gadget works under Win7 well or whether it brought up the whole thing.

At the moment I think about this for doubleshecking:

As my energy profiles are tweaked well and set a very significant clock on my CPU I could use another status monitoring tool called HWMonitor
( and watch the change of CPU clock and doublecheck with it whether a energy profile
change happened based on the clock I see
and whether my Power Gadget from Orbmu2k is exactly in sync with it or how much the max deviation is. A few seconds won't mind.
Remeber, last time I had to move the mouse for more than 1 or 2 minutes and no power status change happened.
Process Lasso / Re: 9.1. performance mode settings do not work 100% anymore
« Last post by ranko on June 06, 2019, 12:48:27 PM »
1. No parkcontrol running
2.  All tests on an idle system.
OS: Win7 Professional SP1, latest Patchlevel.
System: CPU Xeon E5-1650v3, Supermicro X10SRi-F, 32 GB ECC RAM.

Parkcontrol is a great tool. I used it only once to tweak my energy profiles, its not running anymore in parallel.
With it I could achieve that only the 6 main cores (not the hyperthreaded cores) are running and that the clock runs at 2.5 GHz.

What I could do .. I have a 2nd SSD with a Win10 parallel installation running for testing/evaluating Win10.
It is an upgrade installation based on my Win7 system, so more or less the same drivers/applications plus eventually some new drivers with Win10.
The only modifications which I did there is:
- O&O Shutup 10 for Administrator and my account (use per account):
- deactivate Live Apps in Win10 Startmenu
- installation of 8Gadgets and the gadgets which I typically use:
- installation of "Open Shell Menu" (old classic shell, further developed):

See here:

Lets see whether it behaves same or different on Win10.
Coreprio / Re: CorePrio - Bitsum's 'Dynamic Local Mode'
« Last post by Jeremy Collake on June 06, 2019, 12:38:29 PM »
+ Minor code maintenance
Pages: 1 2 [3] 4 5 ... 10