News for hackers. Stuff that matters.
Re:Night Shift compared to f.lux by BigJono on Tuesday March 28, 2017 @09:40PM (#13982571)
This seems like a bug. I've been using f.lux for years across multiple home and work computers and never had a problem with YouTube videos.
Re:Night Shift compared to f.lux by bdrool on Tuesday March 28, 2017 @11:27PM (#13983125)
It happens when you play full-screen videos on a mac. The full screen mode displays in a more direct screen access manner (but only after any overlays, like video controls, have faded out). In this mode, f.lux's color profile changes can cause weird blooming issues, especially in bright ares of the video (like a blue sky). Apple seems to have built their solution in a way that avoids this issue.

It's likely f.lux cannot ever do anything about it. Until Night Shift was available, I've been in the habit of of creating "low color temp" color profiles and manually setting my display to them when it gets late in the day (a crude approximation of f.lux, but ultimately the same thing they are doing). It always produced the same artifact.

Incidentally, I find it strange that f.lux is claiming they output so much less blue light than Apple's Night Shift, since as far as I can tell, all they do is shift the color profile, just like Night Shift does. Anyone who has seen the video issues I'm describing above can attest that there is still plenty of blue light coming out of the screen with f.lux (and manual color profile adjustments). All three accomplish the same thing, it's just that Apple's implementation appears to be cleaner and work in more cases (not surprising -- it's their system, so presumably they know how to integrate with it better than anyone). I think perhaps at most they have a point that the default settings are maybe not "warm" enough, but that's the only flaw I can see.

Re:Night Shift compared to f.lux by Snackchez on Tuesday March 28, 2017 @09:45PM (#13982597)
I have artifact issues with f.lux whenever I'm watching videos in full screen mode. It seems that anything "white" coloured becomes fluorescent. Making the nav / time bar pop up with my mouse seems to make this all disappear. This is on a 2014 MacBook Air running the 2nd latest version of OS X.
Re:Night Shift compared to f.lux by mortenjorck on Wednesday March 29, 2017 @12:06AM (#13983311)
I don't entirely understand the reasons for it, but if you have a MacBook Pro that can switch between integrated graphics and discrete graphics, disabling Automatic Graphics Switching under Energy Saver will fix the problem.
Re:Night Shift compared to f.lux by russjr08 on Wednesday March 29, 2017 @02:17AM (#13983862)
Yep, the issue only seems to happen on the intel graphics card. I believe it's a driver problem.
Re:Night Shift compared to f.lux by ahh on Tuesday March 28, 2017 @10:20PM (#13982779)
I have had the same bug for about a year.
Re:Night Shift compared to f.lux by BigJono on Tuesday March 28, 2017 @09:46PM (#13982606)
Interesting. Is it a subtle effect? Maybe I just haven't noticed it before.
Re:Night Shift compared to f.lux by pyre on Wednesday March 29, 2017 @01:13AM (#13983609)
It's not very subtle. I just whipped together an example[1]. Note that I had to take a photo of the screen with my phone to show what the screen is actually displaying.

[1] http://imgur.com/a/2amF8

Re:Night Shift compared to f.lux by Snackchez on Tuesday March 28, 2017 @09:55PM (#13982655)
Not really. These artifacts are very bright white coloured. It's almost as if F.lux can't deal with certain shades of white and forgets them.
Re:Night Shift compared to f.lux by DiabloD3 on Tuesday March 28, 2017 @10:38PM (#13982881)
F.lux doesn't "deal" with anything, it just takes your existing ICC/ICM file, alters it, and resets your GPU's LUT with it.

I've had the same issue with an Intel GPU'ed MBPR 13" (ie, no Radeon or Nvidia GPU also), and it rarely happened in OSX, but only during certain HW accelerated overlays (such as YUV acceleration in videos, or OpenGL programs doing sufficiently interesting things).

I don't think F.lux has the bug, but OSX's rendering pipeline does. I had similar issues with color profiles I generated myself that noticeably differed from the screen itself (Apple has yet to produce an actually fucking accurate-to-sRGB screen, I don't care how many Photoshop jockeys praise their lord and savior, St. Jobs).

So, yeah. In other news, my MBPr runs Windows 10 and I'm never going back; and I've also never seen the bug here.

The side effect is: F.lux's Windows version is not feature complete with OSX's, and noticeably redshifts at different times than OSX does depending on what settings you prefer.

Re:Night Shift compared to f.lux by spilk on Tuesday March 28, 2017 @10:34PM (#13982858)
It occurs on machines with Intel integrated video only in my experience. Does it on my 2011 MBA and 2016 touchbarMBP, but not my 2012 rMBP. It's well documented here:

https://forum.justgetflux.com/topic/58/strange-colors-blue-f...

Re:Night Shift compared to f.lux by rodorgas on Tuesday March 28, 2017 @10:40PM (#13982891)
F.lux team claims that's an Apple bug. If it's true, Apple doesn't have reasons to fix it.
Re:Night Shift compared to f.lux by krackers on Tuesday March 28, 2017 @10:38PM (#13982875)
I always use gfxcard status to force machines into integrated only mode and I've still never encountered that issue.
Re:Night Shift compared to f.lux by coldtea on Wednesday March 29, 2017 @02:30AM (#13983914)
Perhaps because it is related with the automated switching which you disable in this way?

(Also if you have an external display connected, "integrated only mode" is ignored in gfx).

Re:Night Shift compared to f.lux by Filligree on Tuesday March 28, 2017 @09:46PM (#13982607)
I've got the same problem. It disappears if any UI element other than the video is visible; this includes even UI elements inside the video itself.

But I usually just leave my mouse over the Mac menu bar.

Re:Night Shift compared to f.lux by coldtea on Wednesday March 29, 2017 @02:26AM (#13983899)
I have constant artifacts with flux enabled and youtube videos.