f.lux beta (another thread)
-
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?
-
@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.
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:
- same wake time
- same location
- same presets
- 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. :) -
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.
-
@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.
