Flashing
-
@stalfos Yes. This is correct. I forgot to mention it. Super-obnoxious, but yeah, I know it's beta software. Just wanted to put it on someone's radar. Is there a repo to post issues/bugs?
-
In El Capitan, if you go to System Preferences -> Displays you'll find a new setting called "Ambient Light Compensation". Turning this off fixes the problem.
This new feature seems to be adjusting the response curve in bright rooms (based on Ambient Light Sensor readings). Since f.lux does most of its work at night when most rooms are dark, it might be possible for us to disable this feature at night, but leave it on during the day.
I wonder if Apple will ship it on by default as they've done with the betas.
-
Thanks @herf I don't see this option though :(
Am I missing something? I'm on a 2015 13" macbook pro with El Capitan.
Here's a screenshot of my system description and display options:
Evernote: OSX ScreenshotAny additional help or pointers would be greatly appreciated. I did a bit of searching and didn't see why this setting would/wouldn't show up.
Thanks again!
-
Here I have a MBP Retina 13" Early 2013, El Cap developer beta 3, no adaptative brightness option is shown. Those flashes are burning my eyes :'-(
Interestingly enough, in daylight, when testing sunset or bedtime mode via flux preferences, manual brightness adjustment via dedicated keys does not trigger flashing, but moving to a room with closed curtains is a surefire way to trigger it.
Reported this to Apple via feedback app.
-
It should be under System Preferences > Displays. The behavior you're describing definitely sounds like that's what is happening. :( I see you have "automatically adjust brightness" checked in that screenshot, so try unchecking it.
-
I am experiencing the same issue with f.lux 'flashing' (disabling for half a second might be a better description) when manually adjusting the brightness at night. I'm running a MacBook Air with an external monitor and the 10.11 public beta. I'm using a relatively old 24" Cinema Display and can't see any options relating to ambient brightness in System Preferences -> Displays.
-
@lorna said:
It should be under System Preferences > Displays. The behavior you're describing definitely sounds like that's what is happening. :( I see you have "automatically adjust brightness" checked in that screenshot, so try unchecking it.
I don't have the setting either (and am experiencing the flashing). The auto-brightness setting doesn't fix the issue I'm afraid.
-
The new Mac beta is working better when we write a color profile all the time. ("writeProfile")
-
@herf does that use more CPU power?
-
@herf I'm not sure how to enable this "writeProfile" in a color profile, but happy to follow any steps and report back what I get from testing.
I can confirm that toggling the auto-brightness setting doesn't seem to have any affect on the flashing issue.
When I try to 'calibrate' my internal display the Display Calibrator crashes unexpectedly and I get an error report - not sure if that's related, points to an issue with apple or would provide anything helpful here, but happy to report if so.
Thanks again everyone.
-
I was happy to find this thread and disable the 'Automatically adjust brightness' setting but alas, the flashing continues. (As someone else mentioned, it's like Flux gets disabled for half a second. Repeatedly.)
I'm on a mid-2012 MacBook Pro and using both the laptop screen and a Dell U2713HM .
Is the Beta that the team members have mentioned available to the public?
-Wendy
-
@Breezio are you using more than one monitor? The Feature is named Ambient Light Compensation.
@lorna
-
@wsmoak I haven't seen an available beta. I emailed and asked if the software had an open-source license and a public repo but got no response as of yet. Would love to help with debugging and trying to figure out how best to do that :)
-
@lorna Not all macs have the option to toggle ambient light compensation. My 2013 Retina MBP doesn't have it as an option in the displays preference pane when using the built-in or external displays.
-
@seajay Can you describe exactly what's happening on your 2013 MBP? Is it new with El Cap? I'm thinking there are two different problems we're talking about.There are some problems with flashing when the GPUs switch, and that is a different (but similar) issue to the Ambient Brightness El Capitan problem. No publicly available beta yet but soon.
-
@lorna Yeah, absolutely. It's new with El Cap - been using flux for years on osx without issue before. The symptom presents itself when manually adjusting brightness using either the keyboard (f1/f2) controls or dragging the slider in System Preferences>Displays. Any manual change to brightness results in flux flashing off until the new brightness locks in, which is pretty jarring at night.
-
This is super helpful, thanks. Hope we have a good answer for you soon. Meanwhile if you want, you could try gfx.io to lock one or the other card (I'm maybe making a big assumption that it's dual GPU here) and see if you can track down which one is causing the problem.
@seajay said:
@lorna Yeah, absolutely. It's new with El Cap - been using flux for years on osx without issue before. The symptom presents itself when manually adjusting brightness using either the keyboard (f1/f2) controls or dragging the slider in System Preferences>Displays. Any manual change to brightness results in flux flashing off until the new brightness locks in, which is pretty jarring at night.
-
@lorna Tried gfx.io and received the following error:
- You are using a system that gfxCardStatus does not support. Please ensure that you are using a MacBook Pro with dual GPUs.
That jives, since I'm fairly certain all 13" Macbooks use integrated graphics cards. The 2013 retina mpbs use Intel HD Graphics 4000.
Of note, I tried disabling rootless and that fixed the problem.
-
Oh boy, that is very interesting, thank you for the update. Wow.
-
@seajay Yeah, I know that's probably not the answer you were hoping for. I disabled rootless to see if it would help me get more functionality out of iStat Menus, which did work. It also fixed f.lux, which was an unexpected but much appreciated side effect.
I know most users should definitely NOT be disabling rootless, since it's an important security measure. Still though, it's nice to have my old apps working properly again.
