That may be, but if you don't hear it in regular daily use and have to create a circumstance in order to hear it then it really isn't something you should be concerned over in my opinion.
Sure, unless those circumstances are skipping time in YouTube, closing Quicktime while something is playing, Logic presenting you with rhythmic crackling, FCPX popping as you scrub a clip... Pretty common activities. Some devices present lower than others, it seems to be related to volume level, maybe you have an application open that happens to mask the issue (there are workarounds like leaving Quicktime ready to record, having Logic open with a 512+ buffer size) - the users report that even though they didn't hear it before, once they did hear it, they always noticed it.
So... definitely something to be concerned about.
[automerge]1575524344[/automerge]
Ahhhhhhhh, fair enough. I didn't know adjusting white point had that effect. I don't, however, think that it undermines the brightness problems. Sure, True Tone (and similar 3rd party applications) can make the display appear dimmer in certain environments, but wouldn't that have been the case since 2018, when Apple incorporated it into the MacBook Pro? I'm assuming all the people who've complained of lower brightness aren't using their display in significantly different environments. Why would they be perceiving lower brightness with True Tone on now than they did with True Tone on then?
The screen's still dimmer. And while (after hearing your white point explanation) I'm sure that True Tone would take the screen a couple of perceived nits down anyway, but it now takes it down a couple extra nits than it used to. Enough to bother people.
With your comparison, you make it sound like True Tone takes down perceived brightness to an extremely low level, now matter how bright the display actually is. This doesn't make sense. If you want to overcome the effect of something that makes the display seem dim (like strobing on gaming displays), the solution is to make the base brightness HIGHER, not lower.
Yeah, I was moreso commenting on how the user was complaining about having to turn off a feature that is meant to adjust the display in ways that could make it appear dimmer in order to have it brighter. If the display is dimmer than your liking regardless, that's too subjective for me to comment on apart from if it's bad enough, unfortunately maybe the laptop isn't for them this time. However relating what is essentially an optional QoL feature and having to disable it to the price of the laptop seems like a non-sequitur.
[automerge]1575524602[/automerge]
Why? Why would I go out of my way (more than I already have) to test for a software/driver bug that is nonconsequential and going to get fixed soon anyway?
Even if I did have it, I wouldn't care since it's just software...and it'll get fixed.
I mean, should people also go find every possible way to reproduce every tiny software bug in Catalina so they can use a fixable software bug to complain about a hardware release? That's literally what people are doing with this popping issue.
No, but there is obviously a substantial enough amount of people reporting the issue, so your help in identifying any patterns wrt working units vs units presenting the issue is valuable to determine possible conclusions, since the most any of us are getting from Apple is "engineers are working on a solution as we speak".
Any data is good data, and when I called Apple support, the information gathered by that thread helped me communicate with him so he had a good case to take to the engineers.
Don't have any clue why you had to use such a patronizing tone.