f.lux beta (another thread)

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

    @TwoCables Man...you are amazing! Many thanks, im learning a lot with you!
    Ive been using F.lux since 2010 and can´t live without it anymore.

    You're quite welcome!

    Yeah, I think I've been using f.lux since maybe 2011. It's absolutely wonderful that I can still use my computer when I have successfully reduced or eliminated blue light and alerting light everywhere else in my little living space!

    Of course, I don't think it ends with light (or the brightness of light). I think it's also good to avoid loud noises and sounds, fast rhythms from anything, video games, movies, pretty much anything on T.V. these days including the news (heh), physical activity that raises your heart rate and gets you going, etc. Anything that is stimulating and energizing can be bad and make it harder to go to sleep. I mean, I think we should all take a cue from the animals outside because when the sunset draws near, they begin winding down and their activity levels decrease and they make less noise, etc. They calm themselves down and avoid things that interrupt that calm serenity they are trying to achieve.

    I even found in my research that it's best to wait a minimum of about 3 hours after eating before going to sleep because that's about the minimum amount of time for your stomach to become empty so that your body isn't being forced to digest while you are trying to sleep. Have you ever gone to sleep like say 30 minutes or an hour or an hour and a half after a decent-sized meal only to wake up hot or to have bad dreams - or both? Or you think you sleep fine but you feel kinda crappy the next day?

    Then, of course, there's caffeine and alcohol and other things. lol

    Of course, at 800K, there isn't much I can do on my computer and still enjoy it except for maybe reading things. That's fine though because I really shouldn't be doing anything other than super calm and peaceful things at that time anyway. Still, it's hard. I want to play video games or something so that the time goes by faster so that before I know it, I'm laying down to go to sleep. lol

    It's tough being a human being on this planet. LOL :)

  • On Windows, where is the disabled-program data stored? Since, currently there is no option to un-disable the use of f.lux with a certain program once it's been disabled for that program already.

  • @SomeGuyNamedDavid Undo it the same way - open the program you want re-enabled, then open f.lux preferences > uncheck disable for [current app]. No master list yet.

  • Before I update everyone, look at 4.22?


    This one is all about color - we are trying to dial in better color calibrations even when Windows doesn't have one. Basically a lot of our laptops were too "green/yellow" and we tried to fix it using some embedded monitor info.

    Also trying to fix tone map so things look better when you dim a lot at night - looks amazing when it works.

    Color stuff may be buggy, so let me know! Options has "Use Monitor Data for Calibration" which you can turn off.

  • @herf Well....colors are more darker indeed :D can you explain what "Use Monitor Data for Calibration" means? I see little difference when I turn it off.

  • @sitayi2308 Well most monitors have a built-in record of their chromaticities (the exact colors that RGB are).

    It used to be, this wasn't a good place to look for information, but with the half-dozen machines around here, we found awful color profiles but perfect embedded panel profiles. So we turned this on, and for some of our machines it is dialing in perfect colors.

    "dUV" is "distance from the planckian locus", or how far a thing is off the blackbody curve. So we had one particular laptop that was dialing in +0.016 dUV (way into the green/yellow area), and now it is around -0.001. So you would call it a beautiful warm glow, rather than puke yellow!

  • indeed darker color, Halogen turned Incandescent (Benq xl2730z)

    my feedback:

    1. can you please add an option for disable the Notifications on hotkeys actions? (alt page down, etc) In Overwatch when i change brightness the notification makes the game minimize and send me to desktop

    2. If i'm seeing it right each step on brightness is 7%, can it be a option to set how much % we want to each step ? I prefer small steps (on of the good things that SunsetScreen has) because this monitor brightness is weird (too dark or burn your eyes)

    thanks for the work !

  • Whoa. I think Alt+Page Down dimming looks much better. I mean, correct me if I'm wrong, but I think that previously dimming resulted in a severe gamma shift effect whereas now it's much more even from the top to the bottom of my monitor.

    I've been meaning to say that I think it would be great if f.lux could remember my last Alt+Page Down dimming setting. That way, if I restart my computer or exit f.lux and then relaunch it, it will go right back to where I had it. I always dim 1 or 2 increments when I go to an extremely warm red color like 800K because dimming with Alt+Page Down restores proper contrast at these extremely red colors with my preferred NVIDIA Control Panel "Digital Vibrance" setting. Obviously I could just stop using Digital Vibrance when I go to a very warm color like 800K, but it takes far more time than just pressing Alt+Page Down and the result is the same.

    I'd even say the Alt+Page Down dimming should never be undone unless the user chooses to do so, even if the computer is restarted (or if f.lux is closed and relaunched). So, I would even go as far as saying the dimming setting should always remain until the user restores the brightness with Alt+Page Up. After all, there is a "Return to Full Brightness" menu item now. Right now, the dimming is undone way too easily. It happens when I disable f.lux too.

    I think it would be nice too if we had the ability to dim from the f.lux menu or the window too. I think it would need to be a slider. Or, at least arrow buttons to click. Or, maybe just a drop-down menu of the different dimming levels. Or a sub-menu. Or both. Or all of these.

    I noticed too that Darkroom Mode gets disabled if I Alt+Page Up at all while in Darkroom Mode regardless of where my dimming is currently set. I don't know how long it has been like this though; this is the first time I think I've pressed Alt+Page Up while in Darkroom Mode. I would say that this isn't desirable. Of course, I could look at it as an easy way to disable Darkroom Mode. heh :)

    All transitions are now only super choppy if the f.lux window isn't open. So, all transitions are very close to being butter-smooth when the f.lux window is open, but once it closes (or if I close it), they become a slide-show every time I have a transition.

    I think the transition speed when launching f.lux to the set color temperature (like 800K for me) should be much faster. The transition speed for disabling and re-enabling is wonderfully fast, so I'd like it if the transition on the launch of f.lux (or when restarting the computer) could be that fast or faster.

    I think a restart is required after upgrading to 4.22. Before I restarted my computer, I was able to break the "Disable for [program]" feature by doing this:

    1. Enable "Disable for [program]" (in this example, I am using Firefox)
    2. Switch to Firefox to disable f.lux
    3. Open the f.lux window (f.lux remains disabled at this point)
    4. Go into the f.lux menu using the f.lux window and turn off the "Disable for [program]" feature

    When doing this, f.lux would get stuck at 6500K because it was still disabled for that program while I turned the feature off. After that, the feature no longer worked, even if I closed all programs and exited f.lux and reopened everything. Apparently, I had to restart my computer to fix it because I can't break it anymore no matter how hard I try.

    Before restarting my computer, I was able to Alt+Page Up in Darkroom Mode without disabling Darkroom Mode. Now it disables it.

    I don't know how to reliably reproduce this next bug, but sometimes the percentage of daylight will read 0% when I choose 1200K, and sometimes it will read 1%. Sometimes it seems to depend on how I chose the previous color temperature, whether that's via the menu or via the slider. Sometimes it seems to depend on whether I had 6500K selected prior to choosing 1200K, sometimes it doesn't. It's strange. If it reads 1% at 1200K, I can get it to go to 0% and stay there by Alt+Page Down dimming, and then Alt+Page Up to restore the brightness. Note: I am using the Very Fast transition speed, if it makes any difference.

  • So to add, I think a restart should be required for this update. Version 4.22 is working noticeably better for me after restarting my computer. When I installed 4.22, I still had 4.21 installed - but it wasn't running of course. I always exit f.lux first. So, it's not like I had a fresh installation of 4.22.

  • @TwoCables So far the only difference is more yellowish in all settings, so i presume thats the correct color when "Use Monitor Data for Calibration" its activated.

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

    @TwoCables So far the only difference is more yellowish in all settings, so i presume thats the correct color when "Use Monitor Data for Calibration" its activated.

    I have no idea. That setting isn't changing anything for me.

  • @TwoCables we turn it off internally when the monitor doesn't give good data or just reports sRGB. Probably should hide the checkbox then too.

  • @TwoCables whether it says 1% or 0% is probably due to dimming - it should not care how you got there. And we aren't confident about these numbers to this level yet anyway!

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

    @TwoCables whether it says 1% or 0% is probably due to dimming - it should not care how you got there. And we aren't confident about these numbers to this level yet anyway!

    It's not due to dimming.

  • @lorna Bringing up the f.lux right-click menu while the program is launched doesn't show any disable options after the program has already been disabled.

    Though, on a separate note, I'd also like to see more options for how f.lux handles disabling-by-program. Currently, f.lux re-dims the color temperature as soon as the program window in question loses focus. Meaning that clicking in/out of the window frequently results in lots of temperature shifting. Either an option for "disable f.lux for out-of-focus programs" or a time-out period for f.lux's re-enabling (e.g. f.lux will wait 5 minutes after losing sight of the program before turning back on) would be great to see.

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

    @lorna Bringing up the f.lux right-click menu while the program is launched doesn't show any disable options after the program has already been disabled.

    Though, on a separate note, I'd also like to see more options for how f.lux handles disabling-by-program. Currently, f.lux re-dims the color temperature as soon as the program window in question loses focus. Meaning that clicking in/out of the window frequently results in lots of temperature shifting. Either an option for "disable f.lux for out-of-focus programs" or a time-out period for f.lux's re-enabling (e.g. f.lux will wait 5 minutes after losing sight of the program before turning back on) would be great to see.

    To put the disabled program back in the list, put it in focus and then open the f.lux menu or window. Then you can undo the disabling.

  • @TwoCables Alright, that worked, thanks. (Extremely prompt response, too!) There were difficulties in doing so because the window in question was in bordered fullscreen, meaning that the only way to get f.lux to see it was to open the f.lux window, click into the program in question, and tab back into the f.lux window before it closes. However, strangely, this method only works sometimes, rather than all of the time, so I may have to attempt it several times before the program in question will appear in f.lux's menu.

    Also strangely, the program in question appears in f.lux's menu twice when it does appear. Clicking the first one places/removes checkmarks on both, while clicking the second one does nothing.

    In the future, it might be better to have disable-able programs persist in f.lux's menu for a minute or so after they've been in focus, or to show the last few most recently in-focus programs in said menu, to prevent possible issues like these.

  • After what Lorna said in the post below, it sounds like they do have plans to make it far better.


    "No master list yet."

  • Yes this is still a work in progress. We held off on the feature in v3 because we didn't like the timing, which still needs improvement.

    I think we did a little better with the timing on Mac, where disable is very fast, but re-enable is very slow. The case for me is: working in Photoshop (disabled), alt-tab to a chat client (enable slowly), go back to Photoshop. Fast adjustments back and forth are not very good here.

  • @herf Alright, sounds great, will be looking forward to it. Keep up the good work, been loving much of the new beta changes so far.

  • @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 ;-)

  • @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....

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

  • @herf A humble ASUS X555L

  • Fixed another color bug, sorry!

  • @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.

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


  • 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.

  • @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

  • @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

  • 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,

    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

  • @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.

  • @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. :)

  • @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. :)

Log in to reply