f.lux

    f.lux forum

    • Register
    • Login
    • Search
    • Recent
    • Popular

    Progessly reduce color overtime

    Windows v3
    6
    7
    5376
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tj3n123 last edited by

      I like this program a lot, but i cant figure out if there's or somehow the dev never thinks about this before...It should be reduce the blue color overtime from 6 -> 12 since not bam! orange color, its pretty annoying since i have my light on and my eyes not yet adaptation to the orange color yet, reduce blue light progessive to the choosen level over time is really needed.

      Thanks for the great app, hope u guys can implements this!

      1 Reply Last reply Reply Quote 0
      • lorna
        lorna last edited by

        Maybe try the slower 1 hour transition? There's not really a good reason to hit your CPU from 6-12, so we don't.

        @lorna

        Tungsten_smooth S 2 Replies Last reply Reply Quote 0
        • TwoCables
          TwoCables last edited by

          Yeah, the 1-hour transition is much better than the 20-second transition. However, if the 1-hour transition is still not slow enough, then just remember that a 6-hour transition could potentially slow down your computer in a noticeable way.

          1 Reply Last reply Reply Quote 0
          • Tungsten_smooth
            Tungsten_smooth @lorna last edited by

            @lorna said:

            Maybe try the slower 1 hour transition? There's not really a good reason to hit your CPU from 6-12, so we don't.

            What about the Mac version, that does from sunset (can be 6 in the winter) to bedtime, which can get around 11-12? That seems close, but is there a different more efficient way that f.lux works there? Does it make slightly bigger changes, or only every 5-10 seconds instead of every one or two seconds?

            1 Reply Last reply Reply Quote 1
            • S
              stevemidgley @lorna last edited by

              @lorna I would also like to see a slower transition time than 1 hour. Just a +1 vote for a feature that progressively goes from normal to redshifted over a long period. Thanks.

              1 Reply Last reply Reply Quote 0
              • herf
                herf last edited by

                It's a lot harder to figure out circadian timing for 6 hour fades because we just don't have an intuition (or evidence) of how people react to them. They might be incredibly awesome, but we just don't have a good way to do the timing -- e.g., if you want to feel sleepy at 11PM, when exactly in the 6 hour fade will you start feeling more tired and how should the fade be shaped? Getting this wrong seems a lot worse than getting a 1-hour fade wrong.

                We do two slow fades in the Mac build and that will be coming to Windows soon.

                I guess we could open up some more parameters and let people try it out.

                Most circadian research is done with on/off signals (no fade at all) but recent work has started to consider fading too. At least the sunset is reasonably "about an hour" so that is why we do fades in that time scale.

                The Mac "late mode" is actually using a 90-minute fade now, but this is actually because it fit our morning model better.

                1 Reply Last reply Reply Quote 0
                • T
                  tj3n123 last edited by

                  thankyou for the reply, im using the 1hr transistion but it still seem fast, maybe give the user option to choose the fade time? that might be best?

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright © 2014 NodeBB Forums | Contributors