Resolution setting for Philips display broken #940
Replies: 9 comments 5 replies
-
|
Also, I have had an issue with the Philips flickering sometimes when I first startup, and requiring a reboot to get a stable display. |
Beta Was this translation helpful? Give feedback.
-
|
Oh yeah. Right along I've been using this with the HDMI Port. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @billsouthworth - if you are using native smooth scaling, the max. horizontal resolution for M1 Pro/Max/Ultra is 3840. If you are using dummy mirroring, there is no such limitation. In the latter case make sure that you are mirroring the dummy to the screen, not the other way around. If you post a screenshot about how your menu looks like and what do you see under Settings/Displays, I might help you out. The HDMI port of the M1 MBP is a pain, if you can, I'd advise you to use USB-C/DisplayPort. This is also required for DDC brightness control to work. |
Beta Was this translation helpful? Give feedback.
-
|
@waydabber I tried it all with no success. |
Beta Was this translation helpful? Give feedback.
-
|
I tried all your suggestions and I've attached some screenshots of the controls. I mirrored the dummy to the Philips and tried various combinations of setting and not setting the resolution of the Philips. It seems like I should be setting a resolution for the dummy but the controls only allow setting the ratio, which I set to 32x16. This all worked for me several days ago before it broke and I'm wondering if I should go back to an earlier release of BetterDummy |
Beta Was this translation helpful? Give feedback.
-
|
Hi there,
However due to the funny aspect ratio of the display, you'll need to enable the following settings in order to allow the dummy a bit more flexibility in terms of resolution options (on the screenshot they are disable but don't let this distract you!):
However if you see that this does not work, you can try an earlier build of BetterDisplay, or it might be some issue with the new 12.5.1 update? I am on the latest Ventura beta and things seems to work fine with these settings, including the 32:9 dummy. |
Beta Was this translation helpful? Give feedback.
-
|
All right, if it works and the image seems all right, I don't want to complicate things. I was just saying that based on the screenshots it looks as if the display's native resolution is not properly detected. Also it seemed like the display was treated as a TV which is also less than optimal (no nightshift, true-tone for example).
|
Beta Was this translation helpful? Give feedback.
-
|
After many hours of screwing around, I got this to work again at 5120x1440 by going back to the release from November. |
Beta Was this translation helpful? Give feedback.
-
|
All right. However I am not sure if this entire approach actually makes sense. The Philips 499P9H has a 5K panel (5120x1440). If your Mac drives this display at 3840x1080 then even if you successfully create a dummy set to 5120x1440 mirror it to the display, you'll still have it scaled to 3840x1080. The GUI size will be all right, but this is not a real solution as the picture quality will needlessly suffer. Trying to overwrite the native resolution from 3840x1080 to 5120x1440 won't work since the limitation is not due to an EDID issue but probably comes from some kind of connection limitation. I suppose you are trying to connect the display via HDMI instead of USB-C-DisplayPort cable (the HDMI port on the M1 Macs do not support 5120x1440 afaik, even if the bandwidth should be below the limits of HDMI 2.0). |
Beta Was this translation helpful? Give feedback.
-
|
I tried using a USB-C cable to one of the USB Thunderbolt 4 ports and it didn't work but I think that may be a cable problem. The display seems to work just fine again with little degradation on HDMI using the November BetterDummy release. |
Beta Was this translation helpful? Give feedback.
-
|
The hardware config shows as this: Apple M1 Max: Chipset Model: Apple M1 Max |
Beta Was this translation helpful? Give feedback.
-
|
That’s how it was detected with the current BetterDisplay version. I have it running nicely now after going back to the November ’21 version of BetterDummy. Here’s how that one lists the display:
- Bill
… On Aug 29, 2022, at 1:18 PM, Istvan Toth ***@***.***> wrote:
All right, if it works and the image seems all right, I don't want to complicate things. I was just saying that based on the screenshots it looks as if the display's native resolution is not properly detected. Also it seemed like the display was treated as a TV which is also less than optimal (no nightshift, true-tone for example).
<https://user-images.githubusercontent.com/37590873/187258298-0358e3c6-e459-4d89-b272-1ecd2535ad5e.png>
<https://user-images.githubusercontent.com/37590873/187258308-eb5b01f0-ec45-4d51-ab78-6b0b0e82cf7a.png>
—
Reply to this email directly, view it on GitHub <#940 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWUVDVBYLAHH3RZLRLZ2Z3V3TWFXANCNFSM57256QSA>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
Totally by experimentation, I’ve got things working again with 1.0.12. I feel like I’m balanced on the head of a pin. Everything is working EXCEPT when the system sleeps or the Philips display is disconnected. The goal is to have the Philips PHL 499P9 run at its native resolution of 5120x1440 with my Macbook M1 Max Pro. I’ve had this working since last fall but everything broke when I installed the latest BetterDisplay release. I’ve attached the System Hardware Report which shows that, with version 1.0.12, the Macbook is treating both the Philips and the dummy as 5120x1440.
My remaining problems are that the Philips will either start flickering or the settings will be lost after sleep or sometimes after a reboot. Enough screwing around disassociating or deleting the dummy and rebuilding will fix this. It’s working but the whole thing is kind of unstable.
I’d love to switch to a more recent release but I spent about three days experimenting with settings with the latest version and could never duplicate the operation of 1.0.12.
I know the arguments about OSX not supporting native 5120x1440, but my Macbook doesn’t seem to have gotten the memo about that.
Suggestions?
- Bill
… On Aug 28, 2022, at 10:14 AM, Istvan Toth ***@***.***> wrote:
All right. However I am not sure if this entire approach actually makes sense. The Philips 499P9H has a 5K panel (5120x1440). If your Mac drives this display at 3840x1080 then even if you successfully create a dummy set to 5120x1440 mirror it to the display, you'll still have it scaled to 3840x1080. The GUI size will be all right, but this is not a real solution as the picture quality will needlessly suffer.
Trying to overwrite the native resolution from 3840x1080 to 5120x1440 won't work since the limitation is not due to an EDID issue but probably comes from some kind of connection limitation. I suppose you are trying to connect the display via HDMI instead of USB-C-DisplayPort cable (the HDMI port on the M1 Macs do not support 5120x1440 afaik, even if the bandwidth should be below the limits of HDMI 2.0).
—
Reply to this email directly, view it on GitHub <#940 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWUVDQQ7RQ2LTWLSR7KESDV3NX5ZANCNFSM57256QSA>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
As far as I know the M1 macbook does support 5120x1440, but I understand that there seems to be some kind of issue with your setup which causes the macbook to recognize the display as 3840x1080. I think this might be a connection issue (if you use HDMI, then it is understandable, but if you use USB-C to DisplayPort, the issue should not happen). If the native resolution is detected as 3840x1080 then even if you use a dummy and mirror its screen to the display, it won't help. Even though the dummy GUI will be rendered 5120x1440, the end result will be scaled down to 3840x1080 (as scaling and mirroring always honors the detected native resolution). The fact that with a dummy you see 5120x1440 in System Report for the external display does not mean that everything is all right, because in mirroring scenarios the System Report app will simply show the resolution of the mirror source for the mirror target. So for example I can make it so that my 4K display will show huge resolutions when mirroring a huge dummy screen to it:
But despite what System Report says, in fact the display is driven at its native pixel resolution (in my case 4K). So the resolutions shown in mirroring scenarios for the physical display are not valid real world resolutions which faithfully describe the video connection. This is why I say that your problem will not be solved by utilizing a dummy, and BetterDummy 1.0.12 will not really help with this. You need to understand what is wrong with the connection (or maybe display settings) that the connection cannot push through the proper native pixel resolution suitable for the display. |
Beta Was this translation helpful? Give feedback.
-
I've been using BetterDummy for a year or so successfully with a 49" Philips 499P9, recently on an M1 Max Macbook Pro. Originally I used a dummy to set the resolution to 5120x1440. More recently, I've been resetting the native resolution successfully. I've had a couple of software updates happen recently including an update to Monterey 12.5.1. Somewhere along the way, things have broken and I can no longer get the display resolution on the Philips to go above 3840x1080, no matter what I do. I've re-installed the latest BetterDisplay 1.2.9 Pro. I've tried creating a dummy to set the resolution. Tried to reset native and default without the dummy. And with the dummy. Nothing works.
Beta Was this translation helpful? Give feedback.
All reactions