- Posts: 14
- Joined: Wed Aug 08, 2018 6:29 pm
- Location: Chicago, IL
- Real Name: C. Ryan Stemple
Howdy BMD Forum Folks,
I've noticed a persistent UI scaling issue when using Resolve on the 2022 MacBook Air M2 (v. 18.1.1 currently, but this has been a consistent issue with all releases of v18 at the least). The symptom of the problem lies in how the Palette Area of the Color page is incorrectly adjusted to combine the Left, Center and Right Palettes into just a Left and Right Palette, while the root of the problem (assumedly) lies in that Resolve does not recognize the M2's Liquid Retina display (2560 × 1664) as an HD display, regardless of the HiDPI scaled display setting used in System Settings. I'm assuming this based on Blackmagic's own literature; pgs. 2743 & 2744 of the Resolve 18.1 manual state:
As you can see in the attached stills, this ends up being a fairly significant misuse of screen real estate on what is assuredly an increasingly common machine for this application. The software scopes (locked to 1-up display without expanding) are stretched to a frankly ludicrous and in-adjustable degree.
My initial theory supposes that Resolve's UI is not currently HiDPI-aware, and instead sees the M2 Air's screen as having it's "effective" scaled resolution instead of it's "actual" resolution. The M2 Air's System Settings exclusively allow for HiDPI settings for the built-in display, and while the hover-over info for the M2's "Default" display option reads "1470 x 956, and the "More Space" hover-over reads "1710 x 1112," it is my understanding that the nominal resolution of the display is still in fact 2560 × 1664. In previous iterations, this hover-over info has read "looks like [resolution]," which is both more and less helpful than showing what Apple's scaling filter is effectively showing, but I digress. I've included stills of Resolve on the M2 using the "More Space" display setting, and have examples of the "Default" setting as well if desired.
One thing to note is that when a second display is connected to the M2 Air and it's set to mirror displays, and that second display is at least 1920x1080, Resolve then does show all 3 palettes in the Color Page. This isn't surprising, but it is illustrative of the larger problem.
Here's the make-up of this machine:
MacBook Air ('22) | Apple M2 | 24 GB | Ventura 13.0.1
I have updated both MacOS and Resolve to their currently most up-to-date versions (13.0.1 and 18.1.1, respectively). I have attempted all of the display settings in System Settings, and each time, I clicked "Reset UI Layout" in Resolve's "Workspace" menu. I have not yet attempted to turn off HiDPI with an app such as SwitchResX, primarily because this seems by my testing thus far to be a Resolve specific issue, and I'm disinclined to turn off a setting that functions properly to accommodate software that is not functioning properly.
One big caveat to all of this: It is entirely possible that I am quite wrong, and I have missed something exceedingly, embarrassingly obvious. Nothing would make me happier.
Looking forward to hearing the community's and dev team's thoughts! Thanks in advance.
I've noticed a persistent UI scaling issue when using Resolve on the 2022 MacBook Air M2 (v. 18.1.1 currently, but this has been a consistent issue with all releases of v18 at the least). The symptom of the problem lies in how the Palette Area of the Color page is incorrectly adjusted to combine the Left, Center and Right Palettes into just a Left and Right Palette, while the root of the problem (assumedly) lies in that Resolve does not recognize the M2's Liquid Retina display (2560 × 1664) as an HD display, regardless of the HiDPI scaled display setting used in System Settings. I'm assuming this based on Blackmagic's own literature; pgs. 2743 & 2744 of the Resolve 18.1 manual state:
[pg. 2743] At 1920x1080 resolution or higher, a second set of palettes is organized at the bottom center of the Color page. [...]
[pg.2744] NOTE At lower resolutions, the Left and Center palettes are merged to fit the DaVinci Resolve interface into a smaller area.
As you can see in the attached stills, this ends up being a fairly significant misuse of screen real estate on what is assuredly an increasingly common machine for this application. The software scopes (locked to 1-up display without expanding) are stretched to a frankly ludicrous and in-adjustable degree.
My initial theory supposes that Resolve's UI is not currently HiDPI-aware, and instead sees the M2 Air's screen as having it's "effective" scaled resolution instead of it's "actual" resolution. The M2 Air's System Settings exclusively allow for HiDPI settings for the built-in display, and while the hover-over info for the M2's "Default" display option reads "1470 x 956, and the "More Space" hover-over reads "1710 x 1112," it is my understanding that the nominal resolution of the display is still in fact 2560 × 1664. In previous iterations, this hover-over info has read "looks like [resolution]," which is both more and less helpful than showing what Apple's scaling filter is effectively showing, but I digress. I've included stills of Resolve on the M2 using the "More Space" display setting, and have examples of the "Default" setting as well if desired.
One thing to note is that when a second display is connected to the M2 Air and it's set to mirror displays, and that second display is at least 1920x1080, Resolve then does show all 3 palettes in the Color Page. This isn't surprising, but it is illustrative of the larger problem.
Here's the make-up of this machine:
MacBook Air ('22) | Apple M2 | 24 GB | Ventura 13.0.1
I have updated both MacOS and Resolve to their currently most up-to-date versions (13.0.1 and 18.1.1, respectively). I have attempted all of the display settings in System Settings, and each time, I clicked "Reset UI Layout" in Resolve's "Workspace" menu. I have not yet attempted to turn off HiDPI with an app such as SwitchResX, primarily because this seems by my testing thus far to be a Resolve specific issue, and I'm disinclined to turn off a setting that functions properly to accommodate software that is not functioning properly.
One big caveat to all of this: It is entirely possible that I am quite wrong, and I have missed something exceedingly, embarrassingly obvious. Nothing would make me happier.
Looking forward to hearing the community's and dev team's thoughts! Thanks in advance.
- Attachments
-
- 01_vector_more-space-display.jpg (1022.13 KiB) Viewed 2131 times
-
- 02_waveform_more-space-display.jpg (960.84 KiB) Viewed 2131 times
-
- 03_more-space-display.jpg (109.14 KiB) Viewed 2131 times
C. Ryan Stemple, CSI
Colorist | Owner | Operator, Quicksilver Color
quicksilvercolor.com
- Windows 10 Pro | RTX 3090 | AMD Ryzen 9 5900X | 64GB DDR4 RAM
- MacBook Air ('22) | Apple M2 | 24 GB | Ventura 13.0.1
Colorist | Owner | Operator, Quicksilver Color
quicksilvercolor.com
- Windows 10 Pro | RTX 3090 | AMD Ryzen 9 5900X | 64GB DDR4 RAM
- MacBook Air ('22) | Apple M2 | 24 GB | Ventura 13.0.1