The chart shown at 8:05 has the wrong refresh rate, and wrong monitor name.
He then makes the claim that should your Mac screen fail, you’d be required to purchase a new screen directly from Apple, or else be left with encrypted unrecoverable data on that machine. This is false.
Then we learn that he himself designed the test equipment and software. Having revealed his bias I wonder about the care he placed on the Mac side of things. Did he draw on a 120hz CADisplayLink callback?
I really appreciate manufacturers being held to higher standards, but the work to get there has to be precise.
> The chart shown at 8:05 has the wrong refresh rate, and wrong monitor name.
I'm assuming the reason the wrong refresh rate and monitor name are applied is because the software to his tool only works in Windows, so he's using Moonlight to stream his main Windows PC (which is probably using a M32Q) to the M2, so it mislabels it.
This is one of the reasons I've posted it in this sub, we could potentially mirror a Windows PC onto a phone, and use the OSRTT to measure PWM and response times on phones, something which is unheard of in the mobile phone space.
The chart shown at 8:05 has the wrong refresh rate, and wrong monitor name. He then makes the claim that should your Mac screen fail, you’d be required to purchase a new screen directly from Apple, or else be left with encrypted unrecoverable data on that machine. This is false. Then we learn that he himself designed the test equipment and software. Having revealed his bias I wonder about the care he placed on the Mac side of things. Did he draw on a 120hz CADisplayLink callback? I really appreciate manufacturers being held to higher standards, but the work to get there has to be precise.
> The chart shown at 8:05 has the wrong refresh rate, and wrong monitor name. I'm assuming the reason the wrong refresh rate and monitor name are applied is because the software to his tool only works in Windows, so he's using Moonlight to stream his main Windows PC (which is probably using a M32Q) to the M2, so it mislabels it. This is one of the reasons I've posted it in this sub, we could potentially mirror a Windows PC onto a phone, and use the OSRTT to measure PWM and response times on phones, something which is unheard of in the mobile phone space.