Is there any documentation on what these updates improve?One needs to connect monitor WiFi for firmware updates. Check Source=>Wireless or Wifi. I had 3 consecutive updates from the start (one can hit the "update" line in menu to speed it up).
Is there any documentation on what these updates improve?One needs to connect monitor WiFi for firmware updates. Check Source=>Wireless or Wifi. I had 3 consecutive updates from the start (one can hit the "update" line in menu to speed it up).
Good question. I can’t seem to find a firmware download online for my non-wireless model. However, fortunately I have no sleep issues with the current model with my M1 Mac mini (other than the fact that wake takes several seconds instead of being nearly instantaneous like Apple displays). Wake from sleep was my main concern.Is there any documentation on what these updates improve?
Which version of Monterey? Sleep issues with some other monitors were fixed in later versions of Monterey. I’m on Ventura.No documentation during updates either - a blind process, like Airtags firmware.
I get wake from sleep issues on both DisplayPort and USB-C on Mini M1/Monterey, so maybe that's BECAUSE of the updates?
I've had a look at the HDMI EDID and see no mention of HDCP at all. But I'm not sure if that really means it's a no-go because I don't have a known HDCP 2.2-compliant monitor to compare.Does this monitor not support HDCP 2.2?
That is not a native HDMI port; it's hanging off an active DisplayPort-to-HDMI converter chip FWIW.I tried my M1 Mac mini's native HDMI port [...]
FWIW, it does support HDCP 1.x, since Disney+ does work in Safari, but it is limited to HD. (Netflix is also limited to HD, but I was able to get Netflix HD in Safari on a setup where Disney+ does not, so that doesn't necessarily mean much.)I've had a look at the HDMI EDID and see no mention of HDCP at all. But I'm not sure if that really means it's a no-go because I don't have a known HDCP 2.2-compliant monitor to compare.
Updated my Mini M1 from Monterey to Ventura 13.1 48 hours ago, no sleep issues since then. No major bugs either, for now. I usually stay one OS behind, for safety.Which version of Monterey? Sleep issues with some other monitors were fixed in later versions of Monterey. I’m on Ventura.
Did the LG arrive yet? Which monitor do you like more?Anyhow, I’ve ordered the LG Ultrafine 4K 27” 27UP850N for comparison.
Actually, I ended up cancelling that order. I just couldn't get over its very utilitarian design and aesthetics 🤪 and also, the several reports of bad backlight bleed spooked me. With the MateView I got, I won the no-backlight-bleed lottery, so I'll just stick with that for now and see what's coming next year. However, the LG apparently supports HDCP 2.2 over both DisplayPort and HDMIDid the LG arrive yet? Which monitor do you like more?
Assuming it truly doesn't support HDCP 2.2, that means you won't be able to stream DRM'd 4K video, but you can still stream non-DRM'd 4K video.So there is absolutely no way to stream 4K videos on this monitor? This sounds like a very odd design choice for a modern monitor ...
So there is absolutely no way to stream 4K videos on this monitor? This sounds like a very odd design choice for a modern monitor ...
Assuming it truly doesn't support HDCP 2.2, that means you won't be able to stream DRM'd 4K video, but you can still stream non-DRM'd 4K video.
I got my SpyderX Pro today. I'm not sure I like the included software, so I'll have to give DisplayCal a try. However, in the meantime I have used the SpyderX software to calibrate the MateView in its DCI-P3 mode at 100% brightness, 70% brightness (default), and 50% brightness. All three have removed the green tint I was seeing in the default MateView profile, and all three have also increased the saturation so it no longer looks undersaturated. 70% and 50% look extremely similar. 100% looks fairly close but a bit different than the others. However, it's moot since I won't be running this one, as 100% is far too bright.I have the MateView sitting on the same desk as my 2017 iMac 27".
I have no measurement tools, but by my eye for skin colour in studio photos of my kids, the iMac is just about perfect, but the MateView has a very slight green tint to it. I think most people wouldn't notice the difference, but it's there. I tried sRGB and DCI-P3 and it's there in both. Furthermore, with certain content (videos played in Infuse) if I use the DCI-P3 setting on the monitor and either the DCI-P3 colour profile or the MateView colour profile in Ventura, Infuse is washed out, but Photos looks fine.
What's the distance between the male and female plug? I'm thinking it has to be at least bare minimum 6 mm in between, but perhaps more like 6.5 mm.I got a couple of nice angled adapters for the USB-C and USB-A ports, it looks so much cleaner now.
View attachment 2131171
I didn’t think it was going to fit, but this one is just perfect for the Mateview.
View attachment 2131174
What's the distance between the male and female plug? I'm thinking it has to be at least bare minimum 6 mm in between, but perhaps more like 6.5 mm.
According to my calibration software, in sRGB mode, the brightness setting of 55 = 118 nits at the centre of the screen. The software recommends calibrating to 120 nits or a bit less, and 55 was 118 nits while 56 was 122 nits. The default 70 setting was 168 nits or something like that.I have used the SpyderX software to calibrate the MateView in its DCI-P3 mode at 100% brightness, 70% brightness (default), and 50% brightness. All three have removed the green tint I was seeing in the default MateView profile, and all three have also increased the saturation so it no longer looks undersaturated. 70% and 50% look extremely similar. 100% looks fairly close but a bit different than the others. However, it's moot since I won't be running this one, as 100% is far too bright.
I don’t know the exact measurements, but this is the one that fits just right (I had to apply a little bit of pressure):
https://amzn.eu/d/0PM1Jiq
And also important, it supports 100W charging and 10Gbps data speeds.
The AMD Radeon Pro 4xx (Polaris) dGPU in that MBP should support the MateView's resolution at 60 Hz, or more precise, the 631.75 MHz pixel clock required for it. However, it's possible that the Alpine Ridge Thunderbolt 3 controller or something else is imposing a lower pixel clock limit. To check: Install SwitchResX. Launch it, select the MateView (on the left of the main window) and post a screenshot of the SwitchResX window.I have the Mateview 28.2, and connected to a 2016 MBP 15" via USB-C I cannot output 60hz at any resolution, native or scaled, only 30hz.
Here's what I'm seeing:The AMD Radeon Pro 4xx (Polaris) dGPU in that MBP should support the MateView's resolution at 60 Hz, or more precise, the 631.75 MHz pixel clock required for it. However, it's possible that the Alpine Ridge Thunderbolt 3 controller or something else is imposing a lower pixel clock limit. To check: Install SwitchResX. Launch it, select the MateView (on the left of the main window) and post a screenshot of the SwitchResX window.
That's strange. I get all of those at 60 Hz. I normally run 2304x1536, but I have confirmed that 3008x2005 works fine at 60 Hz on this monitor with an M1 Mac mini over USB-C in macOS Ventura 13.1.Here's what I'm seeing: View attachment 2132695
My preferred scaled resolution is 3008 x 2005, only available in 30 Hz. It looks that the closest equivalent in 60 Hz is 3000 x 2000, though not HiDPI.
Can you post a screenshot of the "Display Information" tab so we can see the allowed pixel clock range?Here's what I'm seeing:
3600×2400 at 60 Hz is also available (at the bottom of the list). Can you check if that mode works (click the checkbox next to it)? The mode uses a 557 MHz pixel clock so if that works, but 3840×2560 at 60 Hz does not, the pixel clock limit may be something like 600 MHz. (Older pre-Polaris AMD dGPUs had a 600 MHz pixel clock limit.) In this case, you could (1) tell macOS to use 3600×2400 at 60 Hz as the base for all scaled modes or (2) create a custom 3840×2560 57 Hz mode (599.25 MHz pixel clock per CVT-RB) and use that.My preferred scaled resolution is 3008 x 2005, only available in 30 Hz. It looks that the closest equivalent in 60 Hz is 3000 x 2000, though not HiDPI.
M1 Mac mini ≠ 2016 15" MBP.That's strange. I get all of those at 60 Hz. I normally run 2304x1536, but I have confirmed that 3008x2005 works fine at 60 Hz on this monitor with an M1 Mac mini over USB-C in macOS Ventura 13.1.
Yeah, I just checked the 2016 15" MBP specs listed at Apple, and it is limited to 5120x2880 max resolution, which I guess means it can't support the scaling past 5K that is required to support HiDPI 3008x2005 60 Hz.M1 Mac mini ≠ 2016 15" MBP.
As I outlined, the 2016 15" MBP may be subject to a <630 MHz pixel clock limit. The M1 Mac mini is not as it can run the Pro Display XDR which requires a 1286 MHz pixel clock for 6K at 60 Hz.