EDID data from U4 HDMI port

[prl]

This continues discussion about possible EDID anomalies on the U4 HDMI IN port from U4 HDMI input with video camera.

Also see Bug #617: U4 HDMI IN doesn't supply supported resolutions in its EDID data

[prl]

As can be seen in the screenshots in the bug report linked above, the Beyonwiz DP-H1 doesn't display any supported video formats. I initially thought that that was the problem, but at I have since looked in more detail at the raw EDID data initially using code that I'd written myself, then at peteru's suggestion, used http://www.edidreader.com/ to decode it.

Here is the native U4 EDID data entered from the screenshots in the bug report. I've checked it by entering it twica and comparing, so I'm reasonably sure that it's correct. It also has a per-block checksum, but it's a simple modulo sum that can't detect some input errors, like swaps of complete bytes (i.e. 12 34 checksums the same as 34 12), so if someone else would like to compare the data with the screenshots, that would be appreciated.

Code: Select all

#00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
# Block 0
 00 ff ff ff ff ff ff 00 08 6d 45 74 67 45 23 01
 18 18 01 03 80 80 48 78 0a da ff a3 58 4a a2 29
 17 49 4b 20 00 00 31 40 01 01 01 01 01 01 01 01
 01 01 01 01 01 01 08 e8 00 30 f2 70 5a 80 b0 58
 8a 00 ba 88 21 00 00 1e 02 3a 80 18 71 38 2d 40
 58 2c 45 00 ba 88 21 00 00 1e 00 00 00 fc 00 42
 72 6f 61 64 63 6f 6d 20 32 2e 30 0a 00 00 00 fd
 00 17 3d 0f 88 3c 00 0a 20 20 20 20 20 20 01 68
# Block 1
 02 03 3d f0 4d 10 05 20 22 04 03 02 07 06 61 5d
 5f 60 23 09 07 01 77 03 0c 00 10 00 b8 3c 21 c8
 6a 01 03 04 81 41 00 16 06 08 00 56 58 00 67 d8
 5d c4 01 78 88 03 e2 00 4b e3 0f 00 12 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55

To get a decode, copy/paste the two blocks of hex data one after the other into the input panel in http://www.edidreader.com/ and click on the "Parse EDID" button. The decoded EDID data appears to the right of the data entry panel as a clickable hierarchical list. There doesn't seem to be an easy way to get a complete report.

[prl]

For comparison, here are two raw EDID dumps for the T4 HDMI IN and for the Digitel ET16SA6DA TV in my test setup.

T4 HDMI IN:

Code: Select all

#00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
# Block 0
 00 ff ff ff ff ff ff 00 08 6d 74 22 05 01 11 20
 00 14 01 03 80 00 00 78 0a da ff a3 58 4a a2 29
 17 49 4b 00 00 00 01 01 01 01 01 01 01 01 01 01
 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
 45 00 ba 88 21 00 00 1e 01 1d 80 18 71 1c 16 20
 58 2c 25 00 ba 88 21 00 00 9e 00 00 00 fc 00 42
 43 4d 37 34 32 32 2f 37 34 32 35 0a 00 00 00 fd
 00 17 3d 0f 44 0f 00 0a 20 20 20 20 20 20 01 89
# Block 1
 02 03 3c 71 7f 03 0c 00 40 00 b8 2d 2f 80 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 e3 05 1f 01 49 90 05 20 04 03 02 07
 06 01 29 09 07 01 11 07 00 15 07 00 01 1d 00 72
 51 d0 1e 20 6e 28 55 00 ba 88 21 00 00 1e 8c 0a
 d0 8a 20 e0 2d 10 10 3e 96 00 ba 88 21 00 00 18
 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 0b 88 21 00
 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 9d

Digitel ET16SA6DA TV:

Code: Select all

#00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
# Block 0
 00 ff ff ff ff ff ff 00 0e d4 03 00 00 00 00 00
 10 14 01 03 80 64 3d 00 8a ee 95 a3 54 4c 99 26
 0f 50 54 a5 4e 00 01 01 01 01 01 01 01 01 01 01
 01 01 01 01 01 01 66 21 50 b0 51 00 1b 30 40 70
 36 00 3f 43 21 00 00 1e 00 00 00 fd 00 18 55 0f
 50 10 00 0a 20 20 20 20 20 20 00 00 00 fc 00 43
 56 54 45 20 54 56 0a 20 20 20 20 20 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03
# Block 1
 02 03 23 74 4f 90 05 04 03 07 02 06 01 1f 14 13
 12 16 11 15 23 09 07 03 83 01 00 00 66 03 0c 00
 30 00 80 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 c4
 8e 21 00 00 1e 01 1d 80 d0 72 1c 16 20 10 2c 25
 80 c4 8e 21 00 00 9e 8c 0a d0 8a 20 e0 2d 10 10
 3e 96 00 13 8e 21 00 00 18 8c 0a d0 90 20 40 31
 20 0c 40 55 00 13 8e 21 00 00 18 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 85

Those two raw EDID samples have correct checksums, but I haven't re-entered the data as a check.

[prl]

Now, to the possible issues in the U4 HDMI IN EDID data that may be causing the resolution problems reported in U4 HDMI input with video camera.

In that report, jayjay says that the input quality for the HDMI IN recording from the video camera is 720x576p 4:3, but I don't think that that is a measured value.

In both the T4 and Digitel EDID data above, the devices report a "native" resolution in Block 1 Extenstion [sic] Header Information / CEA Data Block / Video Data Block

T4 HDMI IN

Code: Select all

Native: TRUE
VIC: 16
Format: 1920x1080p
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 1:1 

AR = Aspect Ratio

Digitel TV:

Code: Select all

Native: TRUE
VIC: 16
Format: 1920x1080p
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 1:1 

However, none of the entries in the Video Data Block for the U4 HDMI IN are marked as "native":

Code: Select all

Native: FALSE
VIC: 16
Format: 1920x1080p
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 5
Format: 1920x1080i
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 32
Format: 1920x1080p
Field Rate: 23.97Hz/24Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 34
Format: 1920x1080p
Field Rate: 29.97Hz/30Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 4
Format: 1280x720p
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 3
Format: 720x480p
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 32:27
Native: FALSE
VIC: 2
Format: 720x480p
Field Rate: 59.94Hz/60Hz
Picture AR: 4:3
Pixel AR: 8:9
Native: FALSE
VIC: 7
Format: 720(1440)x480i
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 32:27
Native: FALSE
VIC: 6
Format: 720(1440)x480i
Field Rate: 59.94Hz/60Hz
Picture AR: 4:3
Pixel AR: 8:9
Native: FALSE
VIC: 97
Format: 3840x2160p
Field Rate: 59.94Hz/60Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 93
Format: 3840x2160p
Field Rate: 23.98Hz/24Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 95
Format: 3840x2160p
Field Rate: 29.97Hz/30Hz
Picture AR: 16:9
Pixel AR: 1:1
Native: FALSE
VIC: 96
Format: 3840x2160p
Field Rate: 50Hz
Picture AR: 16:9
Pixel AR: 1:1 

Due to the way these resolutions are coded, only VIC (Video Identification Code) values 0-63 can be marked as native. See the Wikipedia EDID entry for a full list of VIC values.

It is this Video Data Block information that is being reported in the DP-H1's decoded EDID data (or failing to be reported in the case of the U4).

However there is other resolution information (timing information in EDID terminology) in the EDID for the U4:
Block 0 / Timing Bitmap:

Code: Select all

640×480 @ 60 Hz

Block 0 / Standard Timing Information / Standard Display Modes

Code: Select all

X Resolution: 640
X:Y Pixel Ratio: 4:3
Vertical Frequency: 60 

(that's actually the image aspect ratio, and means 640x480 with 1:1 pixels)

Block 0 / Standard Timing Information / Descriptor 1

Code: Select all

Pixel Clock: 594MHz
Horizontal Active: 3840
Horizontal Blanking: 560
Vertical Active: 2160
Vertical Blanking: 90
Horizontal Sync Offset: 176
Horizontal Sync Pulse: 88
Vertical Sync Offset: 8
Vertical Sync Pulse: 10
Horizontal Display Size: 698
Vertical Display Size: 392
Horizontal Border: 0
Vertical Border: 0
Interlaced: false
Stereo Mode: 0
Sync Type: 3

Block 0 / Standard Timing Information / Descriptor 2

Code: Select all

 Pixel Clock: 148.5MHz
Horizontal Active: 1920
Horizontal Blanking: 280
Vertical Active: 1080
Vertical Blanking: 45
Horizontal Sync Offset: 88
Horizontal Sync Pulse: 44
Vertical Sync Offset: 4
Vertical Sync Pulse: 5
Horizontal Display Size: 698
Vertical Display Size: 392
Horizontal Border: 0
Vertical Border: 0
Interlaced: false
Stereo Mode: 0
Sync Type: 3

Block 0 / Basic Display Parameters / Preferred Timing Mode is set on the U4's HDMI IN EDID (it is required to be set in EDID version 1.3, and Block 0 / Header Information says that it is in fact EDID version 1.3). When Preferred Timing Mode is set, the first descriptor in Standard Timing Information is the devices's preferred timing, 3840x2160p.

Since I don't think jayjay's camera is capable of that, it must be selecting one of the other available resolutions, perhaps the first one in block 0, 640x480.

[peteru]

A new beta is being pushed out now. It has a more appropriate EDID.