EnTech Taiwan EnTech Taiwan
June 26, 2017, 04:35:15 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: I'm confused about EDID from my LG.  (Read 12256 times)
TonyPh12345

Posts: 5


« on: December 27, 2010, 02:36:33 PM »

Ok, here's the EDID data from my LG 55LX6500.

Note that the STANDARD edid Block says that the Preferred/Native Timing is 1920x1080p.

In the CE VIC data block, it says the NATIVE is 1280px720, and OMITS the NATIVE tag next to 1920x1080p.

Is that a problem with the TV firmware?

What's a device to do that  is looking at this information?  What resolution should it choose?
================== EDID REPORT ==================
 
Monitor
  Model name............... LG TV
  Manufacturer............. LGE
  Plug and Play ID......... GSM0001
  Serial number............ n/a
  Manufacture date......... 2010, ISO week 1
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 160 x 90 mm (7.2 in)
  Power management......... Not supported
  Extension blocs.......... 1 (CEA-EXT)
  -------------------------
  DDC/CI................... n/a
 
Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.640 - Ry 0.330
  Green chromaticity....... Gx 0.300 - Gy 0.600
  Blue chromaticity........ Bx 0.150 - By 0.060
  White point (default).... Wx 0.313 - Wy 0.329
  Additional descriptors... None
 
Timing characteristics
  Horizontal scan range.... 31-82kHz
  Vertical scan range...... 57-63Hz
  Video bandwidth.......... 160MHz
  CVT standard............. Not supported
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
  Detailed timing #1....... 1280x720p at 60Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
 
Standard timings supported
     720 x  400p at  70Hz - IBM VGA
     640 x  480p at  60Hz - IBM VGA
     800 x  600p at  60Hz - VESA
    1024 x  768p at  60Hz - VESA
    1280 x 1024p at  60Hz - VESA STD
    1024 x  768p at  60Hz - VESA STD
     800 x  600p at  60Hz - VESA STD
     640 x  480p at  60Hz - VESA STD
 
EIA/CEA-861 Information
  Revision number.......... 3
  IT underscan............. Supported
  Basic audio.............. Supported
  YCbCr 4:4:4.............. Supported
  YCbCr 4:2:2.............. Supported
  Native formats........... 1
  Detailed timing #1....... 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 148.500 1920 2008 2052 2200 1080 1096 1116 1125 +hsync +vsync
  Detailed timing #2....... 1920x1080i at 60Hz (16:9)
    Modeline............... "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
  Detailed timing #3....... 1280x720p at 60Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
  Detailed timing #4....... 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 138.620 1920 1968 2000 2080 1080 1082 1087 1111 +hsync -vsync
 
CE video identifiers (VICs) - timing/formats supported
    1920 x 1080p at  60Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  30Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  24Hz - HDTV (16:9, 1:1)
    1920 x 1080i at  60Hz - HDTV (16:9, 1:1)
    1280 x  720p at  60Hz - HDTV (16:9, 1:1) [Native]
     720 x  480p at  60Hz - EDTV (16:9, 32:27)
     720 x  480p at  60Hz - EDTV (4:3, 8:9)
    NB: NTSC refresh rate = (Hz*1000)/1001
 
CE audio data (formats supported)
  LPCM    2-channel, 16/20/24 bit depths at 32/44/48 kHz
 
CE vendor specific data (VSDB)
  IEEE registration number. 0x000C03
  CEC physical address..... 1.0.0.0
  Supports AI (ACP, ISRC).. Yes
  Supports 48bpp........... No
  Supports 36bpp........... Yes
  Supports 30bpp........... Yes
  Supports YCbCr 4:4:4..... Yes
  Supports dual-link DVI... No
  Maximum TMDS clock....... 225MHz
  Audio/video latency (p).. n/a
  Audio/video latency (i).. n/a
  HDMI video capabilities.. Yes
  EDID screen size......... No additional info
  3D structures supported.. Top-and-bottom, Side-by-side w. horizontal sub-sampling
  3D formats supported..... Mandatory formats plus some primary VICs
    1920 x 1080p at  24Hz - HDTV (16:9, 1:1)
    1280 x  720p at  60Hz - HDTV (16:9, 1:1) [Native]
    NB: NTSC refresh rate = (Hz*1000)/1001
  Data payload............. 030C001000B82D20C00E0140001408201820282038204820
 
CE colorimetry data
  xvYCC709 support......... Yes
  xvYCC601 support......... Yes
  sYCC601 support.......... No
  AdobeYCC601 support...... No
  AdobeRGB support......... No
  Metadata profile flags... 0x01
 
Report information
  Date generated........... 12/15/2010
  Software revision........ 2.55.0.868
  Data source.............. File
  Operating system......... 5.1.2600.2.Service Pack 3
 
Raw data
  00,FF,FF,FF,FF,FF,FF,00,1E,6D,01,00,01,01,01,01,01,14,01,03,80,10,09,78,0A,EE,91,A3,54,4C,99,26,
  0F,50,54,A1,08,00,81,80,61,40,45,40,31,40,01,01,01,01,01,01,01,01,02,3A,80,18,71,38,2D,40,58,2C,
  45,00,A0,5A,00,00,00,1E,01,1D,00,72,51,D0,1E,20,6E,28,55,00,A0,5A,00,00,00,1E,00,00,00,FD,00,39,
  3F,1F,52,10,00,0A,20,20,20,20,20,20,00,00,00,FC,00,4C,47,20,54,56,0A,20,20,20,20,20,20,20,01,04,
  02,03,2D,F1,47,10,22,20,05,84,03,02,23,09,07,07,78,03,0C,00,10,00,B8,2D,20,C0,0E,01,40,00,14,08,
  20,18,20,28,20,38,20,48,20,E3,05,03,01,02,3A,80,18,71,38,2D,40,58,2C,04,05,A0,5A,00,00,00,1E,01,
  1D,80,18,71,1C,16,20,58,2C,25,00,A0,5A,00,00,00,9E,01,1D,00,72,51,D0,1E,20,6E,28,55,00,A0,5A,00,
  00,00,1E,26,36,80,A0,70,38,1F,40,30,20,25,00,A0,5A,00,00,00,1A,00,00,00,00,00,00,00,00,00,00,22
Logged
Ashley Saldanha
Administrator
*****
Posts: 1806


« Reply #1 on: December 27, 2010, 03:19:59 PM »

While that may seem odd, all *detailed timings* are considered native, so the VIC that is actually tagged as native, is the 5th native format enumerated, not the one and only.
Logged

TonyPh12345

Posts: 5


« Reply #2 on: December 27, 2010, 03:26:26 PM »

I don't understand.

Why would it "enumerate" the 5th one as Native if they are ALL native?

Why is a 720p resolution NATIVE in that list, but the Non-extended block says that 1920x1080 is the PREFERRED / NATIVE?

In other words, what is the point of the NATIVE tag on the CE VIC listing?

Logged
TonyPh12345

Posts: 5


« Reply #3 on: January 02, 2011, 04:11:23 PM »

Still with me, Ashley?  Thnx!
Logged
Ashley Saldanha
Administrator
*****
Posts: 1806


« Reply #4 on: January 03, 2011, 04:10:31 AM »

I don't understand.

Why would it "enumerate" the 5th one as Native if they are ALL native?

Why is a 720p resolution NATIVE in that list, but the Non-extended block says that 1920x1080 is the PREFERRED / NATIVE?

In other words, what is the point of the NATIVE tag on the CE VIC listing?



You are asking me questions best directed to the manufacturer...

The point of the CE VIC is to eliminate the need for detailed timings, since the VIC points to industry standard timings. But lots of manufacturers use both and duplicate timings, as well as tags. Some manufacturers don't tag anything in the VIC as native, since the DTDs are to be used first anyway.

For some reason, your manufacturer chose to tag 720p as a native VIC where another manufacturer might tag nothing, or tag 1080p as well as 720p. But *I* can't tell you what that reason might be....


Logged

TonyPh12345

Posts: 5


« Reply #5 on: January 03, 2011, 09:09:07 AM »

Ashley, thanks for your patience...  I understand your answer.

Let me pose it from a different angle...

If I was an HDMI SOURCE, which of those settings should be considered first?   Should the NATIVE/PREFERRED timings be considered before the CE VIC section, when determining the Native resolution?
Logged
Ashley Saldanha
Administrator
*****
Posts: 1806


« Reply #6 on: January 03, 2011, 11:42:24 AM »

If you were a CE source, you should be using suported timings in the following order:

1. first DTD listed
2. second DTD listed
3. third DTD listed
etc.
...
n. first native VIC listed
n+1. second native VIC listed
etc.
...
nn. first non-native VIC listed
nn+1. second non-native VIC listed
etc.

But as a CE source you might not support all the native timings listed, i.e., even though a display might be native 1080p, an older Roku device that only supports 720p would probably look for that first.

In other words, you might not be using what the display wants first (preferred and native). Instead you might have a preferred output and simply check to see if the display supported that - native or not.

But I'm not a CE source, and I honestly don't know how a CE firmware engineer would approach this. As with firmware from display manufacturers, it probably depends on the engineer in question.
Logged

TonyPh12345

Posts: 5


« Reply #7 on: January 03, 2011, 01:18:05 PM »

Thanks, Ashley!  I appreciate your time.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.15 | SMF © 2006-2008, Simple Machines Valid XHTML 1.0! Valid CSS!