4k@144Hz no longer available after upgrade to Big Sur
 
Notifications
Clear all

4k@144Hz no longer available after upgrade to Big Sur  

 of  10
  RSS

TiM
 TiM
(@tim)
Active Member
Joined: 5 years ago
 

I tried beta 2 of Monterey, but no joy. Same behaviour as Big Sur. 🙁

2017 13" MacBook Pro [7th,2C,U] + GTX 1080 Ti @ 32Gbps-TB3 (Razer Core) + Win10 [build link]  

ReplyQuote
Cương Trần
(@cuong_tran)
New Member
Joined: 2 years ago
 
Posted by: @tim

I tried beta 2 of Monterey, but no joy. Same behaviour as Big Sur. 🙁

That is too bad, 10bits 4k 144hz is just a waste now 🙁

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Bo Gao
(@bo_gao)
Active Member
Joined: 1 month ago
 

Have anyone tried Monterey 12 Beta 6 yet? is DSC enabled?

I have PG32UQ and can only get 4k 100hz 8bit, or 4k 60hz 10bit +HDR

I tried many type-c to DP cables and thunderbolt3 to DP Dock and I failed.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Bo Gao
(@bo_gao)
Active Member
Joined: 1 month ago
 

I found some therrible thing.... https://eve.community/t/4k-144hz-over-usb-c-from-macbook-pro/29500/60

Even if your cable does support the bandwidth, your Mac OS version matters.

There are a lot of people with different monitors complaining about 4K high refresh rate on Big Sur on Intel. Despite everything working fine on Catalina, Big Sur refuses to use DSC for anything except specific monitors, e.g. Apples own Pro Display XDR.

It’ll be interesting to see if Apple ever fix this, or if they only enable DSC for certain “blessed” monitors

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Bo Gao
(@bo_gao)
Active Member
Joined: 1 month ago
 

I tried beta 6 of Monterey, but no joy. Same behaviour as Big Sur. 🙁

image
This post was modified 4 weeks ago

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Bo Gao
(@bo_gao)
Active Member
Joined: 1 month ago
 

I tried beta 7 of Monterey, nothing changed.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
joevt
(@joevt)
Noble Member
Joined: 4 years ago
 

Create a display override with SwitchResX and edit it to add a disableDSC option?

 #38 

 #126 

 #16 

I haven't tried it myself.

 

Mac mini (2018), Mac Pro (Early 2008), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Radeon Pro W5700, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
Bo Gao
(@bo_gao)
Active Member
Joined: 1 month ago
 
Posted by: @joevt

Create a display override with SwitchResX and edit it to add a disableDSC option?

 #38 

 #126 

 #16 

I haven't tried it myself.

 

I see some config like this, but where should I add this config?

image

I just tried Monterey beta 8, nothing changed.

 

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
 

Everyone on this thread may want to keep an eye on this: https://github.com/acidanthera/bugtracker/issues/1812

As this may have the possibility to fix the issues. If not, it is a great starting point to discover problems with DSC and FEC on macOS.

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
Launching Apps on Specific (e)GPUs on macOS

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
joevt
(@joevt)
Noble Member
Joined: 4 years ago
 

@bo_gao, create an override using SwitchResX by clicking on the display in SwitchResX, go to Display Information, click Frequency Range checkbox, change Pixel clock maximum to 4000 MHz. Press Command-S to save.

In the Finder, open a new window, press Command-Shift-G and enter /Library/Displays/Contents/Resources/Overrides

Press return.

Find the override for your display. It should have a recent modification date (within the last 10 minutes). It should be named like this:

DisplayYearManufacture-####-DisplayWeekManufacture-##

Open it up in a text editor. Add those lines before the last </dict> in the file. Save it. I use BBEdit.app since it will automatically ask for your password for files that belong to root.

Disconnect the display and reconnect it. Did anything change?

To change the name of the display, select "Use custom display name system-wide" in the Display Information tab of SwitchResX, change the name at the top of the window, then type Command-S to save. Disconnect the display and reconnect it. You should see that the name has changed in the Displays System Preferences panel. Verify that the override file still has your DisplayPort changes.

I don't have a DSC display so I don't know if the above fixes it.

 

Mac mini (2018), Mac Pro (Early 2008), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Radeon Pro W5700, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
 of  10