f.lux beta (another thread)


  • f.lux team

    @SomeGuyNamedDavid Not while it's launched, while it's active. Thanks @TwoCables for making that more clear.



  • @lorna said in f.lux beta (another thread for 4.21):

    @SomeGuyNamedDavid Not while it's launched, while it's active. Thanks @TwoCables for making that more clear.

    You're welcome, Lorna.



  • 4.21 on my Laptop (Windows 10) the location is incorrectly showing Europe Asia even though the LAT/LON it's showing is actually the North of England.

    I know we're going through Brexit and everything but I don't recall England becoming part of Asia ;-)


  • f.lux team

    @dragon2611 Wow, ok (also thanks for the giggle). Can you message me your coordinates or send a screenshot? Does Google maps locate you correctly?



  • Since this new update and turning the "Use Monitor Data for Calibration" ON in whatever setting i use (2700k 3400k etc) its more yellowish, it will take time to get used to it. So I assume that it due to my laptop screen calbration....


  • f.lux team

    @sitayi2308 maybe we should make a visualizer for it :) which laptop do you have?





  • @herf A humble ASUS X555L


  • f.lux team

    Fixed another color bug, sorry!
    https://justgetflux.com/flux-setup4-23.exe



  • @lorna Right, it's just difficult to reach f.lux while the window is still active if it's fullscreened, because bringing up the taskbar to get to f.lux deactivates the window in question.

    A totally separate thing to note is that f.lux also seems to be creating multiple entries in the "hide/show taskbar icons" settings, depending on what time it is. So my list contains items like:

    • f.lux
      Sunset: 4 hours ago, Wake in 9 hours
    • f.lux
      Sunset in 43 minutes, Wake: 11 hours ago
    • f.lux
      Sunset in 13 minutes, Wake: 11 hours ago
    • f.lux
      Sunrise in 5 hours, Wake in 7 hours

    which are continuously appearing, and must all be turned on/off in order to consistently show/hide f.lux in the taskbar, else it will appear and disappear as time passes.



  • I'd like to see the ability to use the color-changing keyboard shortcut to go back to 6500K from 800K. Right now, I can get close but it's either 6300K or 6550K.

    Transitions while the f.lux window is closed are very choppy for me. When the window is open, they're fairly smooth.

    I think that radio buttons should be used on menu items that can't be deselected when clicking them again. Check marks make it feel like I can just click the currently-selected item to deselect it.

    When I have f.lux disabled for a specific program, or for an hour, or until sunrise, I think it would be nice if it would say so in the window instead of just "Disabled".

    If I'm using custom colors and I go and select a different preset like "Recommended Colors" or something, I would love the ability to instantly go back to my Custom Colors by having a menu item by that name to choose from in the drop-down menu.

    I'm not sure if it's supposed to be automatically updating, but it's not.

    The download link in the beta thread (https://forum.justgetflux.com/topic/3675/f-lux-beta-for-windows) isn't for 4.23 either.

    I found a weird bug. Here's how to reproduce it:

    1. Put f.lux in Bedtime mode
    2. Choose a color that's warmer than 6500K for either Daytime or Nighttime, depending on the underlying mode that f.lux is in.
    3. Hold down CTRL and try to get Bedtime mode to be in 6500K.

    What you should find is, you can only go as high as 6450K. As soon as you put the slider in the 6500K position, the set color temperature drops down to the warmer color for Daytime or Nighttime that you chose, but the slider stays in the 6500K position. It only does this for Bedtime mode. If you release the slider button by releasing your mouse button, the color temperature will drop down as depicted.

    I think it would be nice to choose how long the f.lux window stays open for when it's not in focus.

    I think Movie Mode should be forced on if you choose it while your current color temperature is higher than 4400K.

    I might have more to post later.


  • f.lux team

    Posting 4.24 which avoids interrupting fullscreen apps with notifiers and popups, so at least we can use hotkeys to debug these cases.

    https://justgetflux.com/flux-setup4-24.exe



  • I found that having the monitor data for color calibration ON, (im using 2700k) the screen is yellowish....i dont like very much, so if i disable it it goes to f.lux default color right?



  • 2700K is supposed to be yellowish.


  • f.lux team

    @sitayi2308 yes it goes back to the old code instead



  • @TwoCables Actually it was more red...but i will get used to it. BTW, nice job Herf and Lorna.



  • 4.24 still thinks I'm in Europe, Asia same as screenshot posted earlier for 4.21


  • f.lux team

    @dragon2611 We are using the windows location service. Can you run the "Maps" app from Windows and see if it is doing the same thing?



  • @herf it's correct in there as far as I can tell (it only shows the Lat/Lon when I enter that) it's also correct on the Map in Flux it's just the text under the location box that's wrong.

    55.00N, 1.60W is an area near Newcastle Upon Tyne not really sure why that gets set when I did give it my actual postcode, but anyway it's close enough for the purposes of calculating the sunrise/sunset.

    Where Flux is picking up the (Europe, Asia) text from though I'm not sure


  • f.lux team

    Sorry, I understand the issue now. We are trying to show your continent to avoid people pasting in "E" when they mean "W" and so on. Back before we had the map this was a common problem. Of course with the map there, it is sort of redundant.

    I can imagine that someone in the UK would not think of "nearest continent: Europe" when they see "Europe".



  • @herf Ah it's unclear that it means that,

    Edit:
    Ah Now I understand, I think perhaps the UI could be a bit clearer in alerting a user it won't necessarily store their precise location so they don't get confused when they go back in next time and see something different to what they entered.



  • Please add brightness to the color settings.

    Could use a disable/set color/brightness per app. (this would be amazing!)



  • Bug: The task tray icon forces itself back to being "shown" after each PC reboot. I like to keep my taskbar minimal and clean, so this is making me have to drag it back up to the hidden tray every time I start Windows. (Windows 10)



  • Bug report: "The sun is up. Light is making your body later". I also suggest to rephrase this to similar: "light is making you wake later". Also, the slider is showing the position of the daytime color selection, so not sure what it should show there--maybe the current color, updating every 20 minutes?

    alt text


  • f.lux team

    @phrontisteries yes we have brightness schedules in our internal build, but it is complex enough that we have not shipped it yet.

    Actually, a couple years ago, I had my screen on a "forced" schedule, so f.lux was controlling the dimmer exactly. This was pretty good, but occasionally very frustrating, because when it was wrong, it was awful.

    Since then, we've tried to listen to the keyboard keys that adjust brightness, so you can override our "forced" schedule. This almost works, but there is enough 'noise' in the system (power changes, ambient light sensors, etc.) that it wasn't ready for prime time yet.

    That said, I really wanted to get it done for this version, so it is still on my list for the next one.


  • f.lux team

    @Tungsten_smooth yes we have more to do here. Wake time corresponds somewhat to circadian time, but not exactly - it is also related to sleep debt and the ability of the body to stay asleep (which varies by age). So if you talk to elderly people who have trouble sleeping through the night, they often need a stronger "amplitude" signal (more light during the day) and not always a "phase shift" in schedule (as do 20 year old students who have to get up early for class).

    For f.lux right now, it is a very important time to show "how your body is reacting". This next chapter is "how to help your body do what you want it to" and I hope that can be simple too.

    In the UI, the big slider should usually reflect the current-nearest preset, which is not the best way to do it, but better than having an infinite number of control points that are hard to delete! We could do this better but it makes sense at most times of day.



  • I'm on 4.21 and it doesn't play nice with Windows 10 (toast) notifications. As there is no option in the program's menus, I switch off the sound or even the notification altogether in WIndows Settings (screenshot attached), but after a system restart, f.lux resets the notifications, creating a new entry in the notifications app list.
    Screenshot of windows notification options
    As if f.lux is registering a new instance with the notification system each time. Kind of annoying. I'd love in-program options or a fix for playing nice with Windows system.

    Otherwise I love what you did with per-app options. Been waiting for it for ages.



  • I have both f.lux 4.21 on my Windows PC and f.lux 39.94 on my MacBook Air next to each other.
    The location is the same and on Windows I have set the transition time to "slow" and on the Mac I have disabled the "fast transitions" option.

    Unfortunately their timing is not the same. :cry:
    f.lux 4.21 on Windows is already at 1900K while Mac with 39.94 is still at 27xxK and still going down.

    Can you please align the transition times across these platforms? Bonus points if the Android app also does exactly the same. :)


  • f.lux team

    @hsiktas well they are using the same code, finally. Things to check:

    1. same wake time
    2. same location
    3. same presets
    4. https://justgetflux.com/timesync.html looks similar?

    It turns out my Mac and PC are about 8 kelvin apart (testing during the fastest portion of the bedtime transition), but they are also about 7 seconds apart too.

    The next update may shift the wake timing a bit, so there might be some skew until we update the Mac. But right at this minute for you, they should be the same.



  • @herf
    I had indeed different wake times on both machines and I just adjusted them. This seems to solve my problem. :)


  • f.lux team

    Pushing 4.25 via auto-update, to get everyone testing the newer code. I definitely have bugs filed for all the things in this thread too!

    Thanks everyone.


  • f.lux team

    @hsiktas and I just shifted the wake transition earlier so "fast transition" people should not wake up to an orange screen. However, at night the Mac and PC should still be the same. Glad to hear you got it. :)



  • I'm not sure if I'm too early, but it's not automatically updating for me. I have 4.24.



  • @herf Hey I just installed 4.25, thanks for support DisplayLink Monitors! That was a deal breaker for me! (I still used Flux but the DL monitor had a custom color setting to match my primary monitor at 2900K)

    Bugs
    Only one I found so far: when prompted for UAC in Windows 10 v1607 build 14393.1066) ,flux will instantly show the blue colors on both displays as long as the UAC prompt is up.

    This also happens at the lockscreen. So there is a little bit of inconsistency when working at night as my lockscreen is at 6500K and when I am prompted for UAC for opening programs or scripts that require Admin rights



  • @herf With the new release I just had installed, I very clearly see the future for this program and your other projects: You and Lorna (and probably other people working with color controlled lights) want to make it abundantly clear to avoid or reduce light after / near sunset as much as possible. The "vignette" mode really makes this obvious!

    I do appreciate your specific example, and I'm still in school, but I don't have to get up early for that, it's for other reasons and it's not mandatory. I remember you talked about a phase shift versus a stronger light / dark cycle and I'd a bit of education about what you're describing. My understanding of this topic only involves regulating light / dark timing, so bright light during the day, etc. So, what is a phase shift?

    Thank you, it's great to see you both on the forums, it does seem you've got a bit more free time not working as much on the beta now that you've got it working. You and Lorna are very helpful and it's just incredible how much you all can help explain some of information about light and sleep, and we keep learning more (and I'm sure your research is non-stop so far). I am just in awe of how much there is to learn about all this, I never thought I'd learn so much about what seemed a very simple topic.



  • I did a Performance Test (just noticed the button there) and I got 64 - 70% dropped frames at 60FPS. Is that normal? Feels like a lot. Would you recommend disabling f.lux during gaming then?



  • How are you guys getting 4.25? It's not automatically updating for me.



  • @Tungsten_smooth said in f.lux beta (another thread for 4.21):

    @herf With the new release I just had installed, I very clearly see the future for this program and your other projects: You and Lorna (and probably other people working with color controlled lights) want to make it abundantly clear to avoid or reduce light after / near sunset as much as possible. The "vignette" mode really makes this obvious!

    I do appreciate your specific example, and I'm still in school, but I don't have to get up early for that, it's for other reasons and it's not mandatory. I remember you talked about a phase shift versus a stronger light / dark cycle and I'd a bit of education about what you're describing. My understanding of this topic only involves regulating light / dark timing, so bright light during the day, etc. So, what is a phase shift?

    Thank you, it's great to see you both on the forums, it does seem you've got a bit more free time not working as much on the beta now that you've got it working. You and Lorna are very helpful and it's just incredible how much you all can help explain some of information about light and sleep, and we keep learning more (and I'm sure your research is non-stop so far). I am just in awe of how much there is to learn about all this, I never thought I'd learn so much about what seemed a very simple topic.

    Same here. This beta has opened my eyes to one simple fact: this is an extremely deep rabbit hole.



  • @TwoCables said in f.lux beta (another thread for 4.21):

    How are you guys getting 4.25? It's not automatically updating for me.

    It auto updated here without any problem. I just quitted f.lux and launched it again.

    Btw, one bug, that was already present in build 4.24 at least, can't tell about the previous ones. When the screen goes to "sleep mode" aka AFK, when i return to PC and the monitor powers back on, f.lux has daytime temperature. I am forced to click on f.lux icon in the taskbar to bring it to foreground in order to get back the right temperature.


  • f.lux team

    @caydenly this is a common result now, since GPUs are synchronizing with the backlight. In this version, we have done a lot of optimization to send as few commands as possible, because dropped frames at 60hz are hard to avoid now. (Before the power saving efforts of the past couple years, this stuff was totally free and never dropped frames ever.)

    Also, for gaming, you can use our "very fast" transition setting, so the number of times we will touch the GPU is low.



  • @disqQ said in f.lux beta (another thread for 4.21):

    @TwoCables said in f.lux beta (another thread for 4.21):

    How are you guys getting 4.25? It's not automatically updating for me.

    It auto updated here without any problem. I just quitted f.lux and launched it again.

    Btw, one bug, that was already present in build 4.24 at least, can't tell about the previous ones. When the screen goes to "sleep mode" aka AFK, when i return to PC and the monitor powers back on, f.lux has daytime temperature. I am forced to click on f.lux icon in the taskbar to bring it to foreground in order to get back the right temperature.

    Yeah, I exited f.lux 4.24 several times. I right-click the icon and choose "Exit f.lux".


  • f.lux team

    @Tungsten_smooth Well, we don't know the answers yet -- in particular a lot of people need better ("more") light exposure during the day (which involves screens too, because we work in offices that are too dark to accommodate them). The first part of our job with f.lux is to think up hypotheses and motivate people to test them. The vignette feature is based on some recent research, and I'll write down the idea sometime soon.

    But the main work we're doing is to make models and test them in the real world (not just have people believe they're all true).

    Regarding your question about phase vs amplitude:

    Phase

    Most people think of the circadian system ONLY in terms of phase - e.g., we would call a night owl "phase delayed" and an early bird "phase advanced". This means that their internal clock is offset from the solar time by a certain amount.

    So when you are a night owl who wants to wake up earlier, you want to "advance" your system by seeing more light in the morning and less at night. And the reverse for an early bird who wants to sleep in. As such, a lot of our users tend to be night owls. But you might think this is the end of the road for circadian topics - is your phase aligned with how you want it to be?

    Amplitude

    What is clear from experiments on shift workers and the elderly (and many rodent models) is that the overall circadian rhythm in the body can be suppressed. In some cases, it's operating at a lower "amplitude" because light and dark are not clearly defined or not happening at the right times. For instance, people who spend time in natural lighting during the winter have an enormous melatonin amplitude thorughout the night (you can see melatonin in the blood lasting 14 hours), whereas most of us in the modern world are living in a "perpetual summer" and we have a relatively small melatonin duration in comparison to natural conditions.

    We think some sleep problems (and some immunity and seasonal effects) depend to some degree on the "strength" of the circadian rhythm, not just whether it's phase aligned. (Of course, a misaligned rhythm, e.g., in shift work, will almost always have a reduced amplitude, so they are somewhat related.)

    Also, not all sleep trouble is circadian, so when we can, we look for ways to help people get to bed on time. It is probably true that we could do a lot of good here that's completely unrelated to magic science and more to human behavior.



  • @TwoCables You can also get it via link, as usual, at: https://justgetflux.com/flux-setup4-25.exe



  • @disqQ said in f.lux beta (another thread for 4.21):

    @TwoCables You can also get it via link, as usual, at: https://justgetflux.com/flux-setup4-25.exe

    It was still just v4 before.

    Mike got the automatic update working for me just now though!


  • f.lux team

    @TwoCables Rabbit hole is exactly the way we talk about this - once you fall in, you realize there isn't a bottom. But first you have to fall in....



  • @herf
    Hi ,
    just installed the new "beta" version ..initially it's a bit confusing.. but I think I have my "old" settings back. My Anti-virus did not like the installer ? I agreed /approved that the file was legit but that is something you might need to work on, overall I tend not use the settings at all once the program is installed .. "set and forget " is my motto.

    suggestions ,

    • see if you can get back to the old UI .. the waves on the screen make it very confusing , something compact and neat ?
    • I dunno what they are , the line " light is making your body earlier. means a big huh to me ?
    • change waking time to working time .. ( unless we have people that roll out of bed while working)
    • no help ? not even a link or a help file ? ( maybe could explain how it works and the settings )

    aside from that its good, I have pointed several people to this who work late in the night and most of them give raving reviews ..



  • Wow. Great job with the new software mouse cursor! No reboot required! Now we no longer need to use any tricks.



  • I don't know if this was just a one-off glitch, but I was taking the color temperature down and up with the hotkeys and somehow got it into a situation where it just wouldn't stop going up. It was at somewhere like 70,000K before I ended the f.lux process and restarted it (when I restarted, it was at something like 18,000, which was more manageable to get back down to where it was, especially since it wasn't going up anymore). I've noticed there's an 800 lower bound, but is there an upper bound when using the hotkeys?


  • f.lux team

    @citrusella It goes up to 100,000K, which isn't so enormous - a blue sky can be 50,000K. What we mainly need is a more non-linear adjustment up there, because nobody needs tiny increments all the way up to 100,000K.



  • 4.21 worked flawlessly (notebook, external monitor via vga, win10, integrated graphics).
    4.25 now has the following bugs:
    -Checked “Use Monitor Data for Calibration” makes external monitor greenish. Unchecked returns colors to normal.
    -f.lux colors don't appear after the monitor comes back from power saving standby. Have to click the f.lux icon in order that they come back.