Rem0o
Feature Request: Mix curve: add multiplier
New entry in the "function" drop down in the Mix curve.
All listed inputs are multiplied by each other.
eg: if input 1 says fan is at 42% and input 2 says fan is at 120%, then that's 42% * 120% = 50.4%.
This would be useful for eg adding an extra bias for when it's very hot in the room, or when you want to have the system be very quiet for watching movies.
But none of the inputs (curves) can go outside the 0-100 range, so your use case doesn't work or make sense.
It was just an example, being able to multiply things would be good even if things don't go above 100%
On Mon, May 19, 2025, 18:52 Rémi Mercier @.***> wrote:
Rem0o left a comment (Rem0o/FanControl.Releases#3193) https://github.com/Rem0o/FanControl.Releases/issues/3193#issuecomment-2891679285
But none of the inputs (curves) can go outside the 0-100 range, so your use case doesn't work or make sense.
— Reply to this email directly, view it on GitHub https://github.com/Rem0o/FanControl.Releases/issues/3193#issuecomment-2891679285, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABPWPTA7NOI5QX45HMUXXL27ID37AVCNFSM6AAAAAB5MSF63SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJRGY3TSMRYGU . You are receiving this because you authored the thread.Message ID: @.***>
But multiply by what? For what? How is it automated? If it's hotter in the room for example, the curves will naturally run faster due to the temp.
having multiplication there just makes sense. try and see. people use software in ways you can't anticipate when making it.
On Tue, May 20, 2025, 01:50 Rémi Mercier @.***> wrote:
Rem0o left a comment (Rem0o/FanControl.Releases#3193) https://github.com/Rem0o/FanControl.Releases/issues/3193#issuecomment-2892528547
But multiply by what? For what? How is it automated? If it's hotter in the room for example, the curves will naturally run faster due to the temp.
— Reply to this email directly, view it on GitHub https://github.com/Rem0o/FanControl.Releases/issues/3193#issuecomment-2892528547, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABPWPVGP3H4IMXY7U2L5K327JU6HAVCNFSM6AAAAAB5MSF63SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJSGUZDQNJUG4 . You are receiving this because you authored the thread.Message ID: @.***>
Well, I can't design a good feature if I don't truly understand the purpose. I never implement a feature "blind".
In your use case, you talk about having a way to "offset" a mix. Wouldn't this work? Using the flat as the offset, + or - depending on the function on the mix.
Otherwise, there is already an "offset" feature on the control. However it is "linear" and not "proportional". Would a "proportional" offset on a control satisfy this request?
For eg: You set a fan curve on a control, it ask for 50%. You have a 20% "offset", you get 50 * 1.2 = 60% output.
the problem is that I can't use the same curve for multiple controls with different offsets. so once again i would have to keep multiple curves in sync.
the problem is that I can't use the same curve for multiple controls with different offsets
So you want 1 curve, and 1 multiplier offset PER fan/control? Is that it? The offset in the control card does exactly that. Assign the same curve to multiple controls, then assign a different offset on each control.
for example, if you had a game sensor, or a manual toggle sensor, then i could set things like this:
gpu_fan = normal_gpu_curve + game_sensor * extra_game_curve
or
aio_fan = normal_aio_fan * (100% - quiet_mode) + quiet_aio_fan * quiet_mode