Just tried, not working
Just tried, not working
You are not the only one, I've tried everything on this thread including checking all those Experimental features and also changing user agent > other to Safari 11_0 but still stuck on 1080pI am surprised only me can't play 4k Netflix with T2 chip?
I am having the same issues with my MBP 2018 13 inch. 4K is playing in Youtube nicely, but not in Netflix or Amazon Prime Video. I do not even see the UHD logo's when selecting movies or shows on the web site.I am surprised only me can't play 4k Netflix with T2 chip?
Just to clarify. Only safari on Big Sur can support 4K hdr now.I'm not only not able to play 4k (check using Netflix's Test Pattern sample movie) but also keeps getting HDCP 2.2 S7336 issue. My monitor is LGUL600 which supports HDCP 2.2 with 4k HDR. I'm connecting using Type-c to Display Port adapter which supports Display Port 1.4
Yep. I tried safari on Big Sur and it's totally not working. Keep getting HDCP 2.2 error. This only come after big sur upgrade. Previously at least I could play full HDJust to clarify. Only safari on Big Sur can support 4K hdr now.
So I just checked, and mine was only going up to 1080 again (I have same iMac). First time I've checked since the update. I was able to fix it. Try this:I have a 27" iMac 2020 and Samsung 4K monitor (with HDCP 2.2). 4K finally started working on Sunday after the update, but now today it's stuck on 1080P.
Strangely if I clear my history, restart Netflix. Load the content, it will start with a black picture and sound only, then after a few seconds, it will glitch and display the content. I replicated this again, I noticed it would push 4K resolution but no picture, and then when it glitches and displays the picture it's scaled back down to 1080P.
This is so frustrating, not sure why they can't just get it to work.
Do you have your cable directly hooked to your computer or through a hub? it is highly unlikely for the hub to support hdcpSo I just checked, and mine was only going up to 1080 again (I have same iMac). First time I've checked since the update. I was able to fix it. Try this:
1) Develop > Experimental Features > Reset all to defaults
2) Develop > Empty caches
3) Close Safari > Launch Safari
After doing that, mine went back up to 3840 x 2160. Try that and let us know if it also worked for you. Good luck! Oh, and remember to give it a minute to ramp up to full res.
It’s an iMac.Do you have your cable directly hooked to your computer or through a hub? it is highly unlikely for the hub to support hdcp
I tried this method on macOS 11.0 no joy.Update: This is weird, I found a "trigger" on Safari to get into 4K mode by clicking on a the part of the timeline that is not buffered yet.
It's almost like when a show starts buffering if it starts in 1080p then it will be stuck on 1080p but if you click to a part that hasn't buffered yet, it will get into 4k mode and if you start from the beginning the whole show will be in 4k.
This is a ridiculous way of getting 4k on Safari.
So I just checked, and mine was only going up to 1080 again (I have same iMac). First time I've checked since the update. I was able to fix it. Try this:
1) Develop > Experimental Features > Reset all to defaults
2) Develop > Empty caches
3) Close Safari > Launch Safari
After doing that, mine went back up to 3840 x 2160. Try that and let us know if it also worked for you. Good luck! Oh, and remember to give it a minute to ramp up to full res.
Nice! Glad you’re back to 4K!! Yes, crossing fingers things “just work” going forward.Thanks for the reply, definitely had to empty the caches and reset all default settings and got it to work. Hopefully, we won't be needing to reset and empty the cache all the time to get it working haha
Followed the steps with 2020 iMac 5K i7 on 11.6.1, no luck. Even skipping around on timeline and leaving time to buffer. Frustrating and silly. We pay enough money to Netflix and Apple that we shouldn't have to struggle like this for basics.Thanks for the reply, definitely had to empty the caches and reset all default settings and got it to work. Hopefully, we won't be needing to reset and empty the cache all the time to get it working haha