mp3gain and Process Lasso

[vittau]

Hello,
I was using CDex to rip some songs (CDex.exe), and while doing that, I opened mp3gain to adjust the volume of some other songs. mp3gain has a command-line process (mp3gain.exe) and a separate GUI (mp3gainGUI.exe) that is called first, and then it calls mp3gain.exe.

CDex was using up all the CPU while ripping songs, and then I switched to mp3gain, and clicked to start normalizing volume of those other songs. At this moment, mp3gainGUI called mp3gain.exe, and Process Lasso immediately put mp3gain.exe to IDLE.
I tried setting both to be excluded, but Lasso still would change mp3gain.exe to idle all the times (the GUI was left normal, as it wasn't consuming CPU at all).
Any clues?

And while we're at it, why not put an option like "Never reduce processes to idle"?

Thanks,

Vitor Machado

[Jeremy Collake]

Hi,

Sorry for the delay, I have been in PECompact land the last couple days.

Process Lasso actually sets processes to BELOW NORMAL, not IDLE .. unless you changed the settings. Did you mean that? If not, it's possible that the program itself is lowering its priority to idle. I could see that program doing just that, so be sure to check for that. I'm not saying this is what is happening for sure, just a possibility. If Process Lasso is lowering the priority, you should see that in the log.

The exclusion should be working, but I did have one user report here in the forums that the exclusions weren't working for them.

If I understand what you mean, the option 'never reduce priorities' exists in two ways:

1. Disable ProBalance
2. Set the new option 'do not lower priority class' in the ProBalance paramters dialog (v3.43 beta)

Does this help any?

[vittau]

Ops, I was searching mp3gain GUI and found a priority option that was set to idle.
That was probably the problem, I'll test it later and if the problem still happens I'll let you know.

So you mean Process Lasso will never reduce processes to idle?
What I was talking about, was an option to never reduce to idle (while still working with all the other priorities), but apparently it already does that.

Thanks,
Vitor

[Jeremy Collake]

Yep, your feature request is already done .

I'm glad we determined the cause. I figured the application was lowering its own priority, many applications do -- particularly ones that launch non-interactive background processes.