I haven't looked for a way to determine what ColorElement is being used by the current display mode. Also, there's no way (with the known APIs) to map the current display mode to a TimingElement except for the current mode. #302 In your AllRez output,Unfortunately, no luck on getting any more detailed output form the OSD.
I dumped the output off the AllRez tool (attached) but could not identify whether im getting 4:4:4.
What exactly should it say?
DPTimingModeId
is 83. Here's the info for TimingElement with ID:83. { ID:83 ElementType:0 5120x2880@3932160(3932160)Hz 11534336(11501568)kHz H(5280: 48 32 80 ±:1 *:0) V(2925: 3 5 37 ±:0 *:0) AspectRatio:15 IsInterlaced:0 IsOverscanned:0 IsPreferred:1 IsPromoted:0 IsSplit:0 IsVirtual:0 PreciseAspectRatio:116508 ScanInformation:2 StandardType:1 TimingStandard: TimingType:3 ValidPixelEncodings:6989 CEAShortID: Score:16985
ColorModes = (
{ ID:1 ElementType:1 Depth:8 PixelEncoding:0 DynamicRange:0 Colorimetry:10 EOTF:0 IsVirtual:1 SupportsDSC:1 StandardType:1 Chromaticity: R:, G:, B:, W:, WhiteGamma: Score: },
{ ID:3 ElementType:1 Depth:8 PixelEncoding:3 DynamicRange:1 Colorimetry:1 EOTF:0 IsVirtual:1 SupportsDSC:1 StandardType:2 Chromaticity: R:, G:, B:, W:, WhiteGamma: Score: },
{ ID:6 ElementType:1 Depth:12 PixelEncoding:2 DynamicRange:1 Colorimetry:7 EOTF:2 IsVirtual:1 SupportsDSC:1 StandardType:2 Chromaticity: R:, G:, B:, W:, WhiteGamma: Score: },
{ ID:7 ElementType:1 Depth:12 PixelEncoding:6 DynamicRange:1 Colorimetry:7 EOTF:2 IsVirtual:1 SupportsDSC:1 StandardType:2 Chromaticity: R:, G:, B:, W:, WhiteGamma: Score: },
{ ID:86 ElementType:1 Depth:8 PixelEncoding:0 DynamicRange:0 Colorimetry:16 EOTF:0 IsVirtual:0 SupportsDSC:1 StandardType:2 Chromaticity: R:42112,22016 G:20544,40640 B:9920,3456 W:20544,21568 WhiteGamma:144179 Score:240999 },
{ ID:88 ElementType:1 Depth:10 PixelEncoding:0 DynamicRange:0 Colorimetry:16 EOTF:0 IsVirtual:0 SupportsDSC:1 StandardType:2 Chromaticity: R:42112,22016 G:20544,40640 B:9920,3456 W:20544,21568 WhiteGamma:144179 Score:440999 }
)
DSCRequiredColorElementIDs = (
88
)
}
•••••••••••••IOAVVideoAspectRatioString
1: 27:64
2: 135:256
3: 9:16
4: 9:15
5: 10:16
6: 9:14
7: 3:4
8: 4:5
9: 1:1
10: 5:4
11: 4:3
12: 14:9
13: 16:10
14: 15:9
15: 16:9
16: 256:135
17: 64:27
•••••••••••••IOAVVideoScanInformationString
0: None
1: Overscan
2: Underscan
3: Selectable
•••••••••••••IOAVStandardTypeString
0: None
1: VESA
2: CEA
•••••••••••••IOAVVideoTimingStandardString
0: None
1: DMT
2: GTF
3: CVT
4: CEA
•••••••••••••IOAVVideoTimingTypeString
0: Established
1: Standard
2: Calculated
3: Detailed
4: CEAShortID
•••••••••••••IOAVVideoPixelEncodingString
0: RGB 4:4:4
1: YCbCr 4:2:0
2: YCbCr 4:2:2
3: YCbCr 4:4:4
4: DolbyVision (native)
5: DolbyVision (HDMI tunneling)
6: YCbCr 4:2:2 (DP tunneling)
7: YCbCr 4:2:2 (HDMI tunneling)
8: DolbyVision LL YCbCr 4:2:2
9: DolbyVision LL YCbCr 4:2:2 (DP tunneling)
10: DolbyVision LL YCbCr 4:2:2 (HDMI tunneling)
11: DolbyVision LL YCbCr 4:4:4
12: DolbyVision LL RGB 4:4:4
13: GRGB Tunneled as YCbCr422 (Even line blue)
14: GRGB Tunneled as YCbCr422 (Even line red)
•••••••••••••IOAVElementTypeString
0: Video Timing
1: Video Color
2: Audio
3: Audio Channel Layout
4: Vendor Specific Data Block
•••••••••••••IOAVVideoColorDynamicRangeString
0: Full
1: Limited
2: Unknown
•••••••••••••IOAVVideoColorimetryString
0: SMPTE 170M/BT.601
1: BT.709
2: xvYCC601
3: xvYCC709
4: sYCC601
5: AdobeYCC601
6: BT.2020 (YcCbcCrc)
7: BT.2020 (YCbCr)
8: DolbyVision VSVDB
9: BT.2020 (RGB)
10: sRGB
11: scRGB
12: scRGBfixed
13: AdobeRGB
14: DCI-P3 (D65)
15: DCI-P3 (Theater)
16: Default RGB
•••••••••••••IOAVVideoColorEOTFString
0: Traditional gamma (SDR)
1: Traditional gamma (HDR)
2: SMPTE ST 2084 (PQ)
3: BT.2100 HLG
•••••••••••••IOAVStandardTypeString
0: None
1: VESA
2: CEA
At least on the 2014 I opened, the standoffs seem to have used different welding methods depending on the location. I don't know that they would pop off without damage... but you could certainly grind one off if necessary?Is it possible to remove the standoffs like in the Powermac G5 ? Or most probably the iMac will bend when pulling?
I dumped the output off the AllRez tool (attached) but could not identify whether im getting 4:4:4.
What exactly should it say?
So far, I did not go through the commands to force RGB mode because the test image you referenced looked crisp.
Colorimetry 1,7,10,16 are: BT.709, BT.2020 (YCbCr), sRGB, Default RGB
Most likely you are running full Default RGB.
Thanks to both of you for this.
So with a positive visual result on the test pattern, and what looks like a good result from AllRez (?), this sounds like an overall good result for the T18 as a single-cable display? Am I correct @pSpitzner that your only real concern now is color calibration?
Theoretically it would be possible to profile the sound output, and add an equalizer to correct for this?I wanted to reuse the speakers. But be aware, it doesn't matter if you wire them in series, parallel or leave out one of the drivers - they will sound terrible. I bought the cheapest crossovers I could find - a massive overkill but they do improve the sound. They were a pain to wire up given none of the speaker connectors are labelled! Apple must be doing some EQ magic to get them sounding so good (relatively) by default!
Did you keep the original speakers and add the audio pipe ones, or are the original speakers just there for structural support?My build
I've decided to use the original speakers. The quality is not the best, but I'm ok with it - I will not be listening to music and for movies or games the quality is acceptable.Did you keep the original speakers and add the audio pipe ones, or are the original speakers just there for structural support?
My setup: LM270QQ2 + Haijing T18 (the one with USB). Mounting details below.
That's kind of what the crossovers are doing, but obviously no actual EQing. I did try using software to boost the treble, but the tweeters are funnelled to the bottom of the screen - without them connected it sounds like you have some speakers at the back.Theoretically it would be possible to profile the sound output, and add an equalizer to correct for this?
It could be done with a separate box, but would probably nullify any cost savings for having converted your own display. I wonder if it could be done globally (for the system audio output, not just specific programs) via software on the mac? 🤔
If cheap is a priority, and you don't want or need USB-C charging, then the R9A18 is probably the way to go?cheapness
Yeah, I thought about doing a thunderbolt hub + R9A18 inside at first as well. but now Haijing T19 is kinda pushing me over the edge since it has HDMI 2.1 which is a real nice to have imo for the longevity of it. Not sure though.If cheap is a priority, and you don't want or need USB-C charging, then the R9A18 is probably the way to go?
They are about $60 less expensive than the equivalent T18 bundle, and have plenty of long-term reviews here.
Just read the rest of this thread, and know what you are ordering, so that you get one with the correct firmware for your usage.