Update 23.01: I have since confirmed that HDR PQ modes do indeed work with the Asus PA32UCX, UltraStudio 4K Mini and Final Cut Pro. Also, I did not realize at the time I posted this that Daniel was not using an I/O box. The BMD UltraStudio works with both DaVinci Resolve and Final Cut Pro. Mac Pro HDMI 1.4 does not support HDR.
Whether working in Final Cut Pro or just playing YouTube videos, HDR PQ reference modes are greyed-out in the OSD of the Asus PA32UCX, the only flavor of HDR available being HLG BT. 2100. As an added bonus, when scrolling through modes, the entire screen blacks out, which is annoying af. The know-nothing after-sales support at Asus is infuriating: I’m still waiting for an answer since emailing them this morning, but I’m not expecting a helpful response. If you ask them where the on/off switch is located, they’ll tell you to take a photograph of the monitor and get back with you in a week. I’m only exaggerating a little. When asked if they could put me directly in touch with a product manager, I was told that was not possible! Blackmagic forum member Daniel Boist was experiencing the same issue. He writes:
“Guys, is there a way to force the PA32UCX to go into HDR-mode? When feeding the display via Displayport or HDMI from the MacPro i can‘t get it into HDR (all HDR-modes are greyed out in the settings). I tried it from the mac-desktop as well as via DR16.1.2 video-clean-feed and HDR-Meta-Data over HDMI on and off. Did a factory-reset, re-installed firmware on the display etc. but no luck. When connecting an AppleTV 4K via HDMI it automatically switches into HDR (same cables).so at least this works… I‘m going to get an Ultrastudio 4K Mini soon…but would like to test around with HDR in the meantime. Any thoughts?”
Asus needs to get their act together and not only write a decent owner’s manual, but also hire qualified individuals and train them properly. As an example of outstanding customer service, my brand new 16″ MacBook Pro wouldn’t shut down. After chatting with an Apple support team member for less than fifteen minutes, we were able to isolate and fix the problem: two apps running in the background that I promptly deleted from Users and Groups.