So you are saying you were able to run 7680x4320 downscaled to 4K UHD on a 4K UHD display before Sequoia? 🤔
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
DP/USB-C/Thunderbolt 3/4 to HDMI 2.1 4k@120hz RGB4:4:4 10b HDR with Apple Silicon M1/M2/M3 now possible !
- Thread starter AironMan
- Start date
- Sort by reaction score
He's saying your screenshot shows the same problem. 3840x2160 is not available in HiDPI anymore under Sequoia.
Not only 4k, also near 4k is not possible anymore. Like stevemr123 says its because of the framebuffer limit 7k since macOS 15 ONLY for M1/M2
but I can do 4k @ 120 hz hidpi on sequoia right now, check out my previous screenshots
(
okay now i realise what AironMan meant, i can't do hidpi at pure 4k but a little less than that
Only with the M3 models is it possible to achieve up to an 8K frame buffer, allowing for 4k@120Hz with HiDPI and HDR. Since macOS 14.1, Apple has limited M1 and M2 models, first by restricting HDR + HiDPI at 4k@120Hz, and now with macOS 15.0, we can’t even achieve 4k@120Hz with HiDPI anymore.
What makes this even more absurd is that the M2 models, despite having a native HDMI 2.1 port, are also capped at a 7K frame buffer. This limitation feels like an intentional restriction imposed on older devices, despite them being fully capable of handling these features.
What makes this even more absurd is that the M2 models, despite having a native HDMI 2.1 port, are also capped at a 7K frame buffer. This limitation feels like an intentional restriction imposed on older devices, despite them being fully capable of handling these features.
- Please pull a request to Apple and credit my Apple ticket request (FB15247887) so they can see that we’re all raising the same issue
Using M3 Air + 201310-BLK + LG C2 and can enable HDR at every resolution scale, except this specific resolution scale I prefer it's not allowed:
Greetings,
has anyone tested the new adapter from Belkin?
Here in Germany it is even listed in the official Apple Store.
It claims to support 8k60hz and 4k@120hz plug and play. Compatible with all recent MacBooks.
It is odd though that in other countries Apple lists the old adapter supporting only 4k60.
What do you guys think?
has anyone tested the new adapter from Belkin?
Here in Germany it is even listed in the official Apple Store.
It claims to support 8k60hz and 4k@120hz plug and play. Compatible with all recent MacBooks.
It is odd though that in other countries Apple lists the old adapter supporting only 4k60.
What do you guys think?
Last edited:
Turns out that the dscTargetBPP preference can only be changed if the Apple Internal SIP bit is set, and that bit cannot be set by csrutil. I don't know how to change that bit.
My WhateverGreen fork (Intel Macs only) has a new patch to change dscTargetBPP (add a boot-arg
dscbpp=8 - for Catalina and later). If you're using Open Core or OCLP, then you can replace Lilu and WhateverGreen with my versions. If you use any other Lilu based kexts then they need to be recompiled using the headers from my Lilu.kext. That patch, in conjunction with the CheckTimingWithRange patch (add a boot-arg -cdfon - For Tiger and later), can enable 4K240 and beyond on Intel Macs with a GPU that supports DSC (tested with 6800XT and Sequoia). DP to HDMI adapters are not tested.I think Apple Silicon Macs automatically support DSC with values ≤ 12 (4K240 tested on M3 with Sequoia).
I would be very interested to know if it works, but if you search it up and look at the amazon reviews it seems that it does not in fact support 4k 120hz on macs.
I'm having a hell of a time trying to update the firmware on my adapter. I understand you can't use parallels with the adapter I have which is 201310(only after a few hours of trying, didnt' realize I had that model) so just to confirm is the ONLY option to use windows laptop? I do have a MacBook that has bootcamp, my last resort is to try and use that to update it.
After loading Paralells and UTM to try and get the firmware to update, even tried using my gaming PC, it refuses to update.
My last resort is to try and use my old MacBook with windows that happens to have a USB C connections and and a Intel chip to flash it with that, otherwise I don't know how I can update this stupid adapter.
For those who have updated the firmware, I just want to confirm, does the adapter need to be connected to a monitor for it to update the firmware, can it be ANY monitor, does it need an active connection?
After loading Paralells and UTM to try and get the firmware to update, even tried using my gaming PC, it refuses to update.
My last resort is to try and use my old MacBook with windows that happens to have a USB C connections and and a Intel chip to flash it with that, otherwise I don't know how I can update this stupid adapter.
For those who have updated the firmware, I just want to confirm, does the adapter need to be connected to a monitor for it to update the firmware, can it be ANY monitor, does it need an active connection?
Well, it updated instantly after loading the windows update and firmware program. All is working now.
4K/120hz/HDR on my LG C2. This is great..now I can just have 1 cable going to it and use my existing mouse and keyboard via KVM to control it and not need to unplug a bunch of cables.
do I need to always open the laptop first to have it connect to the tv or is there an option where if I connect it or is already connected it awakes without intervention?
4K/120hz/HDR on my LG C2. This is great..now I can just have 1 cable going to it and use my existing mouse and keyboard via KVM to control it and not need to unplug a bunch of cables.
do I need to always open the laptop first to have it connect to the tv or is there an option where if I connect it or is already connected it awakes without intervention?
Does anybody know if 4K 120Hz will work on an M2 Macbook when connected over to a monitor directly that's equipped with a USB-C 3.2 Gen 1 (5Gbps) with DP-Alt mode input? So without any sort of adapter, just with USB-C directly?
Specifically I'm talking about the Philips 32M2N8900 Evnia.
Specifically I'm talking about the Philips 32M2N8900 Evnia.
Okay so I spoke too soon. After testing this for a while, it starts to randomly stop waking up properly. At times it seemed to be triggered by flux, but then it still does that without flux running sometimes.
I just installed BetterDisplay, which seems to reset the adapter device on wake. It causes some annoying flashing of the display sometimes (because it's initialized properly sometimes, and then it gets reset), but it's better than having to unplug and plug it in again.
At this point I'm very happy it's working at all, so that will do for now. I'll update if the BetterDisplay method stops working.
Thanks!
Hi,
Maybe this is a bit off topic, because my question doesn't implicate HDMI but DP.
I have a Macbook Pro 14 M1 Pro and a Caldigit TS3+ and I can't seem to achieve 4k 120hz with HDR through USB C to DP or regular DP to DP. Only when I change to 60hz I can activate HDR.
Anyone know if this is a M1 Pro limitation or a dock limitation? If I bought a Caldigit TS4 would this problem be resolved?
Maybe this is a bit off topic, because my question doesn't implicate HDMI but DP.
I have a Macbook Pro 14 M1 Pro and a Caldigit TS3+ and I can't seem to achieve 4k 120hz with HDR through USB C to DP or regular DP to DP. Only when I change to 60hz I can activate HDR.
Anyone know if this is a M1 Pro limitation or a dock limitation? If I bought a Caldigit TS4 would this problem be resolved?
It does not work. It seems that BetterDisplay is unable to reset the adapter, so I'm guessing this isn't actually a macOS problem and it's actually a problem with the adapter getting stuck and not wanting to reset, even through the interface.
I looked on Cable Matters' website and it looks like the article was last updated on September 26. The old firmware I was using was 7.02.112, according to VmmHidTool. The "new" firmware that the automatic updater script installs claims to be 7.02.123, but when manually flashed in VmmHidTool and checked with FW version, the version is actually 7.02.105, which is older (?). I have no way of telling if the version number is just incorrect.. I am using a 201398, chip version A1. VMM7100.
The tool didn't work on Windows 11 the first time I tried it. You need to connect a monitor first through the adapter (and see some image on the screen). When you open the tool, it will just stay on a blank terminal. To get around this you can manually open (then close) both VmmHidTool and VmmDPTool under the bin folder, accepting the Windows SmartScreen popup (click more information or whatever, then Run Anyway). Then the command prompt application will work. You can also just flash it manually, but it's easy to make mistakes so I don't recommend it. If anything, backup your firmware using the FLASH tab/Save to file function. Load to FLASH is what downloads the new firmware to the adapter, and there is no need to erase the flash because it will do that for you. There is a file in there that will give you .112 but I had that originally so I thought I'd try something different.
Both the DP and the HID tools seem to do the same thing. I'm guessing HID uses the USB HID interface to do the flashing and the DP tool does it over the DisplayPort I2C or something. The DP tool is painfully slow, but you may want to try both if one of them does not work i.e. if you're trying to flash through a virtual machine or something like that.
Will report back on whether this works properly or not.
Doing this did not work, the monitor still sporadically has issues waking up from sleep.
I'm starting to wonder whether this is a hardware issue with the particular adapter I have, or if anyone has an adapter with a chip version that's not A1.
Is anyone having a similar monitor wake issue? (Notably, this is when the computer is on all the time, but the monitor goes to sleep for a while and has trouble waking up after a few hours and needs to be replugged)
It is truly outrageous how Apple is handling my feedback. Not only do they completely ignore it, but they also claim that no similar reports of this issue have been made, which is an absolute lie and deceitful on their part. There are plenty of people experiencing this problem. Just within our forum, we can confirm that we’ve reported this issue many times, and I know from other sources that the problem is well-known. This is simply unacceptable behavior from Apple.
What’s happening here is deliberate cover-up, and older Mac devices are being purposefully crippled. One really has to question whether what Apple is doing is even legal. Can we take legal action against this? It seems like they’re pushing boundaries, and we should look into the possibility of legal recourse.
I want to express my frustration about how Apple is handling this. They’re not addressing the problem at all and are merely trying to cover it up, acting as if they don’t even know what’s going on. However, we in the forum can clearly point out that first, the HDR feature was disabled, and now the High-DPI function has also been removed—intentionally, but only for older devices, not for the latest models. This clearly shows what Apple is doing: deceiving us customers and putting up barriers to force us to buy newer devices.
Features that previously worked are now being eliminated with macOS updates, without any mention of these changes in the changelog. This is simply outrageous.
- Please pull a request to Apple and credit my Apple ticket request (FB15247887) so they can see that we’re all raising the same issue since macOS 14.1 and macOS 15
macOS Sequoia 15.0 and newer breaks HiDPI with 4k@120hz 4:4:4 and beyond. The maximum possible is: 3424x1926 for 16:9. LowRes with 4k@120hz 4:4:4 is still possible. The reason: Apple limit the framebuffersize to 7K. M3 users are NOT effected.
macOS Sonoma 14.1 and newer breaks HDR with HiDPI 4k@120hz 4:4:4 and beyond. The reason: Apple change some pixel clock for HDR . M3 users are NOT affected.
Last edited:
Hmmmm got the right adapter and right firmware but only getting 30hz max on my M1 Mini. My HDMI cable is an 8k certified cable as well and my PC gives me 120hz via that cable.
Edit: Changed input name to PC and success!
Edit: Changed input name to PC and success!
Last edited:
Is this a public discussion forum thing? How can I upvote this or highlight this from my side?
To be fair, Apple's Feedback system is not very useful. An extreme amount of feedbacks are pouring in and some ancient software is trying to cross-reference them (no fancy AI there) with little success. 99.9% of these reports don't actually reach an engineer or receive any human touch. So it is not really something intentional they do with the your ticket specifically, it's just a rather outdated system that is overdue for some serious update - but is probably rather low on the priority list. There are probably a handful of engineers at Apple stuffed away somewhere who really know what is going on with the DCP firmware and why these limits are being changed this way and that - if you want any answers you'd need to figure a way to get in touch with them or raise their attention.
