Screen issue on new MacBook Pro M1?

Hello MrHarryEdwards,

these possible fixes are for Intel Mac .... not for M1 Mac - because NVRAM is available in the M1 Mac, but the machine is configured to automatically run test on startup and automatically reset the NVRAM if needed - you can't trigger it manually ....

You can’t reset the SMC, because the M1 Mac doesn’t have a System Management Controller

Best regards,

Ivaylo

Yes. I have definitely had that. And it got kinda repeatable in the oddest way:

You cannot really predict when will it happen, but when it DOES happen, you can basically rewind the video and it will happen in the same part of the video.

I have been playing with this error for a while on a video, and I got to repeat the bug every time IF:

• By the time you reach the frame in which the error happens, you make sure that the YouTube overlay controls are gone. (that is, skip back to a little earlier in the video so it gives time for them to fade away).

That way it will happen every single time. Once it happens, swiping to desktop and wiggling the mouse around makes it worse and makes it last longer, but after 5 seconds it abruptly stops.

If you exit the video (or just press esc and turn off fullscreen, not sure) the error is gone and will not repeat in the same spot.

P.D.: I observed it tends to happen in fairly still videos.

yes, I have had the same problem. I’m thinking it’s something like the screen not knowing how to process the pure black of the borders? It’s so annoying, it looks like someone is pushing up against the screen.

when I press escape to get out of the YouTube video, it happens for like .5 of a second on the desktop screen but then goes away. Or even waving my mouse over there makes it go away slightly.

We need a fix!

I'm having the same problem; it's kind of transient and doesn't always happen, so it's a little hard to replicate with any predictability. But it actually almost looks like a bleeding display for a second, but then it goes away and acts normal again.

Have not had this issue with any other programs or apps so far. Will update if it comes up anywhere else

UPDATE:

So far, it seems only to be an issue on Safari. I tried watching several YouTube videos on Google Chrome (optimized for M1), and so far, no problems at all.

On Safari, nearly every video will do it if I go fullscreen and interact with it at all while it's fullscreen. It can be something as simple as pressing the left or right arrows to jump a few seconds back or forward.

On Chrome, I tried jumping backwards and forwards, bringing up the volume menu, going in and out of fullscreen several times, and repeated the process with several videos. With as much as I was doing, Safari would DEFINITELY give me an issue with the weird flickering black corner. Fortunately, with Chrome, it seems there is no issue.

Leads me to believe it's simply some aspect of YouTube's video codec not being well optimized for M1 yet on Safari, or something in the coding of Safari that is causing this bug. It's definitely a software issue, because no other video sites are giving me any issues on either browser.

I am having the same issue and I was just given the MacBook Pro M1 as a christmas gift this evening. Although my screen appears to be doing the same thing when I exit safari for about 5 seconds. Really weird and I am wondering if I should take it back! I am so sad :((((

for me its also limited to safari, but. Thats not all, when scrolling in YouTube while watching a video, its not really responsive. Ive tried chrome which doesn't have issues, so I generally believe Google and others just doesn't fix the problems with Safari, which is a shame.

If you're okay with doing so, try using a different browser like Mozilla or Chrome. So far, no problems with either. It seems to be something specific to Safari.

I have the same issue but it happens on Netflix and Prime video too

Ive currently only experienced the flickering on videos with a white background.

Is it with white backgrounds? and are you watching it through safari?

Im not sure its limited to YouTube, someone else says they experienced it on Netflix and prime video. For now I haven't experienced the problem anywhere else.