Help: Asus M2A-VM HDMI vs. Yamaha RX-V663 receiver. HDMI connection treated as DVI - AVS Forum
Forum Jump: 
Reply
 
Thread Tools
post #1 of 103 Old 05-27-2008, 11:38 AM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Hi guys,

I have an issue that I've been trying to resolve for the past few days.
I have an HTPC based on the Asus M2A-VM HDMI motherboard (ATI 690G chipset) with the latest Catalyst 8.5 video drivers, 1.94 Realtek HD Audio drivers and 1.92 Realtek "AT HDMI Audio" drivers. The BIOS is the latest non-Beta from Asus (1605). The latest beta (1704 or so) makes my onboard LAN not connect, and does not affect the issue described below.

The entire setup worked perfectly when I had HDMI hooked up straight to my TV (Samsung HL-T5687S) and a coax SPDIF cable hooked up to my old receiver (Harman Kardon AVR320). I kept Realtek's HD Audio Output as the default audio output device, which gave me 2-channel PCM and 5.1 channel Dolby Digital for DVD's and media files with DD soundtracks. If I changed the audio output to ATI HDMI audio I instead got the sound through my TV's speakers. Again, no issues.

The trouble started when I upgraded to an HDMI receiver (Yamaha RX-V663). Now, if I connect the computer to the receiver using the HDMI cable, and I have ATI HDMI audio enabled, I get NO SOUND at the receiver. The HDMI indicator is lit, and I get a picture, but there is no sound transmitted.

What's interesting is that when I have the TV hooked up to the computer via HDMI, I can see the HDMI connection in Catalyst Control Center. When I have the receiver hooked up, the name of the monitor is still reported as "Samsung", but the connection is reported as DVI only.

The only relevant setting on the receiver is HDMI audio processing. HDMI audio is set to be processed on the receiver, and not passed through to the TV.

The receiver is NOT defective, because I get PCM 2.0 and DD 5.1 with no problem when I connect my satellite TV box (Dish VIP622) to either of the HDMI inputs on the receiver. They are able to negotiate a true HDMI connection, and transmit audio just fine. However, the computer doesn't seem to negotiate the same HDMI connection.

Does anyone know if it this is a known bug with the RX-V663? If it's a bug with the HDMI implementation on the 690G and whether upgrading to a 780G motherboard would fix it? Any particular registry tweaks for the Catalyst drivers to enhance compatibility with HDMI receivers?

Thanks in advance,

Alex
Odeen is offline  
Sponsored Links
Advertisement
 
post #2 of 103 Old 05-27-2008, 11:55 AM
AVS Special Member
 
archibael's Avatar
 
Join Date: Jul 2002
Location: Phoenix, AZ
Posts: 4,098
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Odeen View Post

Hi guys,

I have an issue that I've been trying to resolve for the past few days.
I have an HTPC based on the Asus M2A-VM HDMI motherboard (ATI 690G chipset) with the latest Catalyst 8.5 video drivers, 1.94 Realtek HD Audio drivers and 1.92 Realtek "AT HDMI Audio" drivers. The BIOS is the latest non-Beta from Asus (1605). The latest beta (1704 or so) makes my onboard LAN not connect, and does not affect the issue described below.

The entire setup worked perfectly when I had HDMI hooked up straight to my TV (Samsung HL-T5687S) and a coax SPDIF cable hooked up to my old receiver (Harman Kardon AVR320). I kept Realtek's HD Audio Output as the default audio output device, which gave me 2-channel PCM and 5.1 channel Dolby Digital for DVD's and media files with DD soundtracks. If I changed the audio output to ATI HDMI audio I instead got the sound through my TV's speakers. Again, no issues.

The trouble started when I upgraded to an HDMI receiver (Yamaha RX-V663). Now, if I connect the computer to the receiver using the HDMI cable, and I have ATI HDMI audio enabled, I get NO SOUND at the receiver. The HDMI indicator is lit, and I get a picture, but there is no sound transmitted.

What's interesting is that when I have the TV hooked up to the computer via HDMI, I can see the HDMI connection in Catalyst Control Center. When I have the receiver hooked up, the name of the monitor is still reported as "Samsung", but the connection is reported as DVI only.

The only relevant setting on the receiver is HDMI audio processing. HDMI audio is set to be processed on the receiver, and not passed through to the TV.

The receiver is NOT defective, because I get PCM 2.0 and DD 5.1 with no problem when I connect my satellite TV box (Dish VIP622) to either of the HDMI inputs on the receiver. They are able to negotiate a true HDMI connection, and transmit audio just fine. However, the computer doesn't seem to negotiate the same HDMI connection.

Does anyone know if it this is a known bug with the RX-V663? If it's a bug with the HDMI implementation on the 690G and whether upgrading to a 780G motherboard would fix it? Any particular registry tweaks for the Catalyst drivers to enhance compatibility with HDMI receivers?

Thanks in advance,

Alex

Can you post your EDID while hooked up to the Yamaha?

I do not speak officially in any sense for
Intel Corp., Technology Manufacturing Group
but I do work there.
archibael is offline  
post #3 of 103 Old 05-27-2008, 12:31 PM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
DumpEDID v1.01

Copyright (c) 2006 Nir Sofer

Web site: http://www.nirsoft.net



************************************************************ *****

Registry Key : DISPLAY\\HSD04C6\\5&3035ca71&0&10000080&05&00

Monitor Name : JC199D

Serial Number : 616GJ30JA3927

Manufacture Week : 16 / 2006

ManufacturerID : 25634 (0x6422)

ProductID : 1222 (0x04C6)

Serial Number (Numeric) : 3927 (0x00000F57)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 50 - 76 Hz

Horizontal Frequency : 30 - 83 KHz

Image Size : 37.6 X 30.1 cm (19.0 Inch)

Maximum Image Size : 38 X 30 cm (19.1 Inch)

Maximum Resolution : 1280 X 1024

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : Yes

Support Default GTF : No

Digital : No



Supported Display Modes :

720 X 400 70 Hz

640 X 480 60 Hz

640 X 480 67 Hz

640 X 480 72 Hz

640 X 480 75 Hz

800 X 600 56 Hz

800 X 600 60 Hz

800 X 600 72 Hz

800 X 600 75 Hz

832 X 624 75 Hz

1024 X 768 60 Hz

1024 X 768 70 Hz

1024 X 768 75 Hz

1280 X 1024 75 Hz

1280 X 1024 60 Hz

1152 X 864 75 Hz

1280 X 960 60 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\PNP09FE\\5&3260c160&0&10000081&01&05

Manufacture Week : 0 / 1990

ManufacturerID : 53313 (0xD041)

ProductID : 2558 (0x09FE)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 1.00

Maximum Resolution : 1024 X 768

Support Standby Mode : Yes

Support Suspend Mode : Yes

Support Low-Power Mode : Yes

Support Default GTF : No

Digital : No



Supported Display Modes :

640 X 480 60 Hz

800 X 600 60 Hz

1024 X 768 60 Hz

248 X 155 60 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\SAM029B\\5&3260c160&0&10000080&01&05

Monitor Name : SAMSUNG

Manufacture Week : 45 / 2006

ManufacturerID : 11596 (0x2D4C)

ProductID : 667 (0x029B)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 60 - 75 Hz

Horizontal Frequency : 30 - 81 KHz

Image Size : 128.9 X 72.5 cm (58.2 Inch)

Maximum Image Size : 129 X 73 cm (58.4 Inch)

Maximum Resolution : 1280 X 1024

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : No



Supported Display Modes :

720 X 400 70 Hz

640 X 480 60 Hz

640 X 480 72 Hz

640 X 480 75 Hz

800 X 600 60 Hz

800 X 600 72 Hz

800 X 600 75 Hz

1024 X 768 60 Hz

1024 X 768 70 Hz

1024 X 768 75 Hz

1280 X 1024 75 Hz

1280 X 1024 60 Hz

1280 X 960 60 Hz

1152 X 864 75 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\SAM029B\\5&3260c160&0&10000090&01&05

Monitor Name : SAMSUNG

Manufacture Week : 45 / 2006

ManufacturerID : 11596 (0x2D4C)

ProductID : 667 (0x029B)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 60 - 75 Hz

Horizontal Frequency : 30 - 81 KHz

Image Size : 128.9 X 72.5 cm (58.2 Inch)

Maximum Image Size : 129 X 73 cm (58.4 Inch)

Maximum Resolution : 1280 X 1024

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : No



Supported Display Modes :

720 X 400 70 Hz

640 X 480 60 Hz

640 X 480 72 Hz

640 X 480 75 Hz

800 X 600 60 Hz

800 X 600 72 Hz

800 X 600 75 Hz

1024 X 768 60 Hz

1024 X 768 70 Hz

1024 X 768 75 Hz

1280 X 1024 75 Hz

1280 X 1024 60 Hz

1280 X 960 60 Hz

1152 X 864 75 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\SAM029C\\5&3260c160&0&10000082&01&05

Monitor Name : SAMSUNG

Manufacture Week : 45 / 2006

ManufacturerID : 11596 (0x2D4C)

ProductID : 668 (0x029C)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 59 - 71 Hz

Horizontal Frequency : 30 - 70 KHz

Image Size : 16.0 X 9.0 cm (7.2 Inch)

Maximum Image Size : 16 X 9 cm (7.2 Inch)

Maximum Resolution : 1280 X 1024

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : Yes



Supported Display Modes :

720 X 400 70 Hz

640 X 480 60 Hz

800 X 600 60 Hz

1024 X 768 60 Hz

1280 X 1024 60 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\SAM029C\\5&3260c160&0&10000083&01&05

Monitor Name : SAMSUNG

Manufacture Week : 45 / 2006

ManufacturerID : 11596 (0x2D4C)

ProductID : 668 (0x029C)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 59 - 61 Hz

Horizontal Frequency : 30 - 68 KHz

Image Size : 16.0 X 9.0 cm (7.2 Inch)

Maximum Image Size : 16 X 9 cm (7.2 Inch)

Maximum Resolution : 640 X 480

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : Yes



Supported Display Modes :

640 X 480 60 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\SAM029C\\5&3260c160&0&10000093&01&05

Monitor Name : SAMSUNG

Manufacture Week : 45 / 2006

ManufacturerID : 11596 (0x2D4C)

ProductID : 668 (0x029C)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 59 - 61 Hz

Horizontal Frequency : 30 - 68 KHz

Image Size : 16.0 X 9.0 cm (7.2 Inch)

Maximum Image Size : 16 X 9 cm (7.2 Inch)

Maximum Resolution : 640 X 480

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : Yes



Supported Display Modes :

640 X 480 60 Hz



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\YMH3127\\5&3260c160&0&10000083&01&05

Monitor Name : RX-V663

Manufacture Week : 0 / 2008

ManufacturerID : 43109 (0xA865)

ProductID : 12583 (0x3127)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 23 - 121 Hz

Horizontal Frequency : 15 - 91 KHz

Image Size : 70.8 X 39.8 cm (32.0 Inch)

Maximum Resolution : 0 X 0

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : Yes



Supported Display Modes :



************************************************************ *****



************************************************************ *****

Registry Key : DISPLAY\\YMH3127\\5&3260c160&0&10000093&01&05

Monitor Name : RX-V663

Manufacture Week : 0 / 2008

ManufacturerID : 43109 (0xA865)

ProductID : 12583 (0x3127)

Serial Number (Numeric) : 0 (0x00000000)

EDID Version : 1.3

Display Gamma : 2.20

Vertical Frequency : 23 - 121 Hz

Horizontal Frequency : 15 - 91 KHz

Image Size : 70.8 X 39.8 cm (32.0 Inch)

Maximum Resolution : 0 X 0

Support Standby Mode : No

Support Suspend Mode : No

Support Low-Power Mode : No

Support Default GTF : No

Digital : Yes



Supported Display Modes :



************************************************************ *****


This is REALLY interesting.. it shows some of the past monitors that have been connected to the computer (Like the Hanns-G 199D) and the Yamaha V663 gets its own entry as a monitor, yet it can't support any display modes..
Odeen is offline  
post #4 of 103 Old 05-27-2008, 01:14 PM
AVS Special Member
 
archibael's Avatar
 
Join Date: Jul 2002
Location: Phoenix, AZ
Posts: 4,098
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Need the raw EDID hex stream. Use MonInfo.

I do not speak officially in any sense for
Intel Corp., Technology Manufacturing Group
but I do work there.
archibael is offline  
post #5 of 103 Old 05-27-2008, 01:54 PM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Here is the MonInfo report:

Monitor
Windows description......... Plug and Play Monitor
Manufacturer description.... SAMSUNG
Manufacturer................ Samsung

Plug and Play ID............ SAM029C
Serial number............... n/a
EDID data source............ Registry (stored)

Manufacture date............ 2006, ISO week 45
EDID revision............... 1.3
Display type and signal..... Digital
Sync input support.......... n/a
Screen size................. 160 x 90 mm (~8")
Power management............ n/a

Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.640 - Ry 0.340
Green chromaticity.......... Gx 0.300 - Gy 0.620
Blue chromaticity........... Bx 0.150 - By 0.060
White point (default)....... Wx 0.291 - Wy 0.300

Timing characteristics
VESA GTF support............ Not supported
Horizontal scan range....... 30-68kHz
Vertical scan range......... 59-61Hz
Video bandwidth............. 150MHz
Extension blocks............ 1
Timing recommendation #1.... 1920x540 at 60Hz
Modeline................ "1920x540" 74.250 1920 2008 2052 2200 540 542 547 562 +hsync +vsync
Timing recommendation #2.... 1920x1080 at 30Hz
Modeline................ "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
Timing recommendation #3.... 1280x720 at 60Hz
Modeline................ "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync

Standard timings supported
640 x 480 at 60Hz - IBM VGA
1280 x 720 at 60Hz - Samsung
1920 x 540 at 60Hz - Samsung
1920 x 1080 at 30Hz - Samsung

Raw EDID base
00: 00 FF FF FF FF FF FF 00 4C 2D 9C 02 00 00 00 00
10: 2D 10 01 03 80 10 09 78 0A CF 9B A3 57 4C 9E 26
20: 0F 4A 4C 20 00 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 01 01 1D 80 18 71 1C 16 20 58 2C
40: 25 00 A0 5A 00 00 00 9E 01 1D 00 72 51 D0 1E 20
50: 6E 28 55 00 A0 5A 00 00 00 1E 00 00 00 FC 00 53
60: 41 4D 53 55 4E 47 0A 20 20 20 20 20 00 00 00 FD
70: 00 3B 3D 1E 44 0F 00 0A 20 20 20 20 20 20 01 29

Raw EDID extension (reserved)
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Display adapter
Adapter description......... ATI Radeon X1200 Series
Adapter device ID........... 0x791E1002
Display settings............ 1920x1080, 32bpp

User/computer information
Registered user name........ Alex
Registered organization..... n/a
Network user name........... Alex
Network computer name....... HTPC
Windows version ............ Windows XP
Windows build .............. 5.01.2600 Service Pack 3
Installation date .......... 7/16/2007 12:00:00 PM


My notes:
I guess SAM029B is the VGA port on the Samsung. I have had it hooked up briefly via VGA for testing.

What's curious is that the Yamaha RX-V663 gets its own EDID entry in the registry. If Samsung's EDID is passed through the Yamaha to the HTPC, how would the RX-V663 ever end up there?


Hopefully this helps.. I really appreciate your help and I'm looking forward to learning something about HT and computers that I didn't know before.
Odeen is offline  
post #6 of 103 Old 05-27-2008, 03:25 PM
AVS Special Member
 
archibael's Avatar
 
Join Date: Jul 2002
Location: Phoenix, AZ
Posts: 4,098
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
That's what you get while hooked up to the Yamaha? This might indeed be your problem... unless perhaps MonInfo is malfunctioning, you're not getting the second EDID block filled in (it's all zeroes), and that's where all the audio information is stored. If the ATI drivers work anything like Intel's, they check the 2nd EDID block and see if the receiver supports audio. Right now, with all zeroes, that would be "no audio".

I do not speak officially in any sense for
Intel Corp., Technology Manufacturing Group
but I do work there.
archibael is offline  
post #7 of 103 Old 05-27-2008, 03:37 PM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
That's what I get while hooked up to the Yamaha. It's weird that it neither passes the Samsung's 2nd block through (which, I imagine, identifies it as a stereo audio receiver) nor does it identify itself as a 7.1 channel receiver.

I imagine that's why CCC identifies the Yamaha as a DVI device!

Are there any particular power-on sequences to try to make sure that 2nd EDID block gets passed through correctly? 1st TV, then the receiver, then the HTPC, perhaps?

Also, is it possible to erase the saved EDID information and force redetection?

Won't be able to reply until late tonight (going over to my parents' house, as it's my birthday ), but I will definitely play with it some more when I return.
Odeen is offline  
post #8 of 103 Old 05-27-2008, 03:45 PM
AVS Special Member
 
archibael's Avatar
 
Join Date: Jul 2002
Location: Phoenix, AZ
Posts: 4,098
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
MonInfo is redetection-- that is, not saved data; it sends the command to the graphics card/mobo to query the receiver/TV realtime and posts the response.

I suspect that TV-->recevier--> PC is the right order, but not sure it will help you.

But, yes, without the second block the PC will detect it as DVI only.

I do not speak officially in any sense for
Intel Corp., Technology Manufacturing Group
but I do work there.
archibael is offline  
post #9 of 103 Old 05-27-2008, 05:18 PM
AVS Special Member
 
SpHeRe31459's Avatar
 
Join Date: Nov 2004
Location: Sacramento, CA
Posts: 1,017
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Wasn't it Onkyo's that have that wierd nonsequitor option that passesthrough the TV's EDID info, instead of the receivers?

I see in the Yamaha user manual something about HDMI Set on Page 98?
SpHeRe31459 is offline  
post #10 of 103 Old 05-27-2008, 08:22 PM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
The Yamaha has an option for HDMI whether it decodes audio, or if it passes the audio through to the monitor.

I have played with the HDMI audio option while connected to my HD satellite receiver, and, when the HDMI audio option is set to "other", I get stereo audio ONLY, but I get it from both the receiver and the TV if I choose. When the HDMI audio option is set to "RX-V663", I get proper Dolby Digital 5.1.

This makes sense, since the Yamaha probably passes through the TV's EDID info when in "Other" mode, and the TV can only handle stereo and, while in the onboard decoder mode it presents its own capabilities. On the other hand, why doesn't the Yamaha present the same EDID info to the HTPC?


And, looking at my second post, with the cached displays EDID info, the Yamaha ended up being a display to the HTPC at SOME point. (Since there IS cached EDID info for the RX-V663). However, every time I've actually used Catalyst Control Center, the monitor name is Samsung.
Odeen is offline  
post #11 of 103 Old 05-27-2008, 08:40 PM
AVS Special Member
 
SpHeRe31459's Avatar
 
Join Date: Nov 2004
Location: Sacramento, CA
Posts: 1,017
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Odeen View Post

The Yamaha has an option for HDMI whether it decodes audio, or if it passes the audio through to the monitor.

I have played with the HDMI audio option while connected to my HD satellite receiver, and, when the HDMI audio option is set to "other", I get stereo audio ONLY, but I get it from both the receiver and the TV if I choose. When the HDMI audio option is set to "RX-V663", I get proper Dolby Digital 5.1.

This makes sense, since the Yamaha probably passes through the TV's EDID info when in "Other" mode, and the TV can only handle stereo and, while in the onboard decoder mode it presents its own capabilities. On the other hand, why doesn't the Yamaha present the same EDID info to the HTPC?


And, looking at my second post, with the cached displays EDID info, the Yamaha ended up being a display to the HTPC at SOME point. (Since there IS cached EDID info for the RX-V663). However, every time I've actually used Catalyst Control Center, the monitor name is Samsung.

That makes sense since the Yamaha is correcty passing the Samsung's info along. Still really odd about the audio. I don't think the previous model the 661 had this issue. I'm looking at the 663 for possible HTPC use, so this is rather disheartening.

Also about the caching you refer to, it's not EDID caching per-say. The EDID data should be negotiated every time you plug in a new device. The history you found is simply what Windows stores in the registry as monitors you've had attached to the PC, which is a bit different. If you want you can actually delete all those entries and Windows will rebuild only whatever the current device(s) are connected.
SpHeRe31459 is offline  
post #12 of 103 Old 05-28-2008, 01:26 AM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I connected the VGA cable between the HTPC and the TV, just to test things out. Checked CCC - CCC reports "Samsung + Samsung" monitors.

Disconnected HDMI out from the receiver. Redetected monitors. Now have "RX-V663 + Samsung". Okay, that makes sense, since the RX-V663 ONLY passes its EDID info if it doesn't have the display's.

Went into the Sound control panel.. and ATI HDMI Audio is GONE. The only output option is Realtek High Definition Audio. The odd thing is that the device still shows up in the Hardware tab of the Sound control panel, and it shows up in the Device Manager. I just can't select it in the hardware selection tab of the Sound control panel.

Reconnected the Receiver-TV HDMI cable. Redetected displays. STILL "RX-V663 + Samsung". Disconnected the VGA cable, switched TV to HDMI. Rebooted. SSaw the BIOS startup screens, saw the Windows splash screen... and then the screen went into "No Signal".

Going to power cycle the receiver and reboot again. If the RX-V663 stayed in continuous HDMI contact with the HTPC, why would the ATI HDMI Output option disappear?!

UPDATE:
This has gone from bad to stupid. I power cycled the receiver, and rebooted the computer. The CURRENT behavior of the system is this:
When I boot (or reboot) the computer, the red HDMI indicator lights up on the receiver display. I get an image on the TV. System goes through the BIOS screen, then the windows splash screen. Once it's time to switch to 1920x1080x60P, the HDMI indicator TURNS OFF, and the TV shows "Check signal cable."

I'm going to bed now, but I'm wondering if I should repair install my Windows installation (I have uninstalled and reinstalled Catalysts, and both Realtek drivers), reformat, upgrade to a 780G board, or buy a different receiver that has better control over its HDMI facilities...
Odeen is offline  
post #13 of 103 Old 05-28-2008, 02:02 AM
Member
 
NaTT's Avatar
 
Join Date: Apr 2007
Posts: 185
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
My Yamaha RX-V2700 is away for warranty repair at the moment because when used as an HDMI switch for my Sky HD, PS3 and HCPC the image/sound drops out intermittently (although oddly I've not seen it when the HCPC is attached - DVI/Analogue audio only there though until the G45's are released).

Not sure how old your 663 is, but don't receiver manufacturers have a responsibility to implement HDMI switching correctly, however early a model it is? If a source - switch - screen chain has a problems, that aren't there without the switch, then surely the switch has to be the culprit and the manufacturer offer you a refund or replacement? Do they have to be fit for all purposes we throw at them?

Perhaps I should post this in the Receiver forum, but it I think it's related to this.
NaTT is offline  
post #14 of 103 Old 06-01-2008, 09:57 AM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I mentioned this HTPC/Receiver incompatibility on another message board (discussing a new pre/pro that I'm considering), and I got the following reply:

"I recall seeing some video card manufacturers having trouble with this. I think the issue was the HDMI settings default to a 2.0 mode that some receivers are not picking up on, but TVs do. There should be a 5.1 default mode somewhere in the video card settings that corrected this.

I know alot of manufacturers are having a few issues with this. It may or may not solve your problem, but it is worth a shot."

Besides the fact that there's no HDMI 2.0, this seems like a plausible explanation. Is it possible to alter some HDMI information that the motherboard presents to the receiver, in order to coax the receiver to report full audio capabilities?
Odeen is offline  
post #15 of 103 Old 06-05-2008, 01:20 AM
Newbie
 
AntHill's Avatar
 
Join Date: Jun 2008
Posts: 2
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Just thought I'd chime in and say I've got the same issue. I've got an older Sony CRT HDTV, a Yamaha RX-V663 and a computer with the onboard ATI HDMI port (Gigabyte motherboard).

The HDMI audio is detected when the cable is connected from the pc to the TV (even though the TV only supports stereo PCM) and the display drivers register it as an HDTV. When it's plugged from pc to reveiver to TV then I get no audio and the drivers think it's a DVI flat panel.

I ran the MonInfo tool and I see no difference in the EDID data when I have the PC directly connected to the TV vs. through the receiver.

I'm running the latest version of the HDMI audio drivers on my pc.

I think I'll try to contact Yamaha to see if they have anything useful to say on the matter.

The only thing I have to add is that if you go into the menu on the receiver and choose "signal info", you can flip between the audio and video details. For me the audio always shows analog on the pc source (or blank if I force it to use only the hdmi audio). The video screen shows the resolution the pc is putting out over hdmi and the type of video connection that's active. For the pc it shows DVI -> HDMI, so the receiver also thinks it's a DVI-only connection. If I keep this menu open and change inputs on the receiver I can see what the other inputs register as. When I switch to my Pioneer upconverting DVD player I can see it handshaking because it switches between different modes before finally settling on an HDMI -> HDMI connection. One of the modes it briefly goes through is DVI->HDMI but it immediately changes up to HDMI->HDMI. This whole handshaking thing results in the HDMI light on the receiver flickering a few times. When I change back to the pc source it remains solidly on DVI->HDMI without any apparent handshaking.

I don't know how much this has anything to do with the problem, but I thought I'd mention that you can use the receiver's onscreen menu to get a bit more info on what's going on. But I have yet to find any additional settings, either on the receiver or the pc, that can solve the issue.
AntHill is offline  
post #16 of 103 Old 06-05-2008, 02:58 AM
AVS Special Member
 
Wo0zy's Avatar
 
Join Date: Sep 2007
Posts: 1,816
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Has anyone tried downgrading the ATI Drivers/CCC to 8.3? There is a similar issue with some older discrete cards. Audio worked perfectly up to and including 8.3 but 8.4 and 8.5 break it. However, audio still works with newer cards (that have the Rev.B dongles) and the latest drivers.

I'll also add that this problem also effects HDMI audio when connecting directly to a TV as well.

Anyway, I've just been given one of these boards to test so I'll let you know later.

Wo0zy
Wo0zy is offline  
post #17 of 103 Old 06-06-2008, 12:39 AM
Newbie
 
AntHill's Avatar
 
Join Date: Jun 2008
Posts: 2
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
This evening I went through a marathon of trying a sampling of the various different driver versions available (7.5, 7.10 and 8.3). None of them made any difference. Now I'm back on 8.5 (I had 8.4 before that and it was the same).

It is worth noting that I haven't had an issue getting sound when connecting directly to my TV, and no dongle is required for my motherboard (it has an actual HDMI connector).

I also contacted ATI/AMD support and, surprise surprise, they said it was the receiver's problem because I was able to get sound on the TV. But I'm not buying it... at least not just because some first-tier support person said so without any evidence to back it up.
AntHill is offline  
post #18 of 103 Old 06-06-2008, 07:23 AM
Newbie
 
Shao128's Avatar
 
Join Date: Sep 2007
Posts: 5
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Just an FYI, there is a new bios out for the M2A-VM HMDI, 1801 (labelled as beta). Not much of a change log posted though:
1. Fix fail to resume from S3 with AMD 5000+ CPU issue.
2. Fix show wrong AM2+ CPU HT/NB frequency in BIOS.

There might be more fixes, but Asus is horrible at posting details
Shao128 is offline  
post #19 of 103 Old 06-11-2008, 11:15 AM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I'm glad that it's not just me that's having this issue..

Anthill - I tried Catalyst 8.3's, and, like you, I saw no change. In the process, I somehow lost the ability to display 1080p60 at all (the output is now limited to 1080i30).

I'm going to try the new BIOS, and then installing Catalyst 8.5's while connected directly to the TV, to make sure I get 1080p60 back.
Odeen is offline  
post #20 of 103 Old 06-11-2008, 11:39 AM
AVS Special Member
 
archer75's Avatar
 
Join Date: Dec 2003
Location: Oregon
Posts: 1,692
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 23 Post(s)
Liked: 34
Here's a dumb question, but is your receiver set to HDMI audio? Typically it's set to auto by default but if it was changed to coax or optical you wouldn't get HDMI audio.
And of course the PC must be set to output audio over HDMI. But i'm sure you already did that.

Are you using the correct DVI to HDMI adapter from ATI? Not any adapter will work. It must be specifically made for this purpose so that audio will transfer. With generic ones audio won't transfer.

HTPC: Intel e6300 2.8ghz, Intel DG45ID, 2gb DDR2, Radeon 5570, MCE IR receiver, Yamaha RX-V663 receiver via HDMI, panasonic ax100u, 145" S-I-L-V-E-R painted screen, 2x Roku 3's, chromecast, Amazon Fire TV, Vizio M602i-B3
archer75 is offline  
post #21 of 103 Old 06-12-2008, 06:21 AM
AVS Special Member
 
Wo0zy's Avatar
 
Join Date: Sep 2007
Posts: 1,816
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I get the feeling there's something more at work here.

I've been following a thread over at AVForums. It seems people with ATI cards/IGP's and Onkyo 606 AVR's are having the same problem.

One guy has an NVIDIA card system as well and that works fine. I got him to post the EDIDs (from the registry so I can see the extension block) for both systems and they are different. Both correctly report the first block but the NVIDIA system correctly reports the second block while the ATI card repeats the first block.

As the audio information (SADs) are in the second (extension) block this certainly explains why they can't get audio to work.

Not sure how this happens or why yet but thought I'd mention it.

Wo0zy
Wo0zy is offline  
post #22 of 103 Old 06-13-2008, 08:47 AM
Member
 
goemonate's Avatar
 
Join Date: Nov 2006
Posts: 62
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Ok, finally i know that i am not alone... I have a V863 and I have the same problem with ATI cards. My onkyo 705 was fine on all cards and drivers.

Please someone post the result with Nvidia cards with Yamaha new Vx63 series.
goemonate is offline  
post #23 of 103 Old 06-13-2008, 10:09 AM
AVS Special Member
 
Wo0zy's Avatar
 
Join Date: Sep 2007
Posts: 1,816
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by goemonate View Post

Ok, finally i know that i am not alone... I have a V863 and I have the same problem with ATI cards. My onkyo 705 was fine on all cards and drivers.

Please someone post the result with Nvidia cards with Yamaha new Vx63 series.

I can't post NVIDIA results for you unfortunately (I don't have acces to a Yamaha AVR) but I can confirm that I have no problems with an Onkyo 705 either.

Can you post your stored EDID from the registry for the Yamaha ? I'd like to see if it's showing the same issue as the 606's.

Thanks,

Wo0zy
Wo0zy is offline  
post #24 of 103 Old 06-13-2008, 11:05 AM - Thread Starter
Member
 
Odeen's Avatar
 
Join Date: Dec 2002
Location: Northern California (Bay Area). 94546
Posts: 32
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by archer75 View Post

Here's a dumb question, but is your receiver set to HDMI audio? Typically it's set to auto by default but if it was changed to coax or optical you wouldn't get HDMI audio.
And of course the PC must be set to output audio over HDMI. But i'm sure you already did that.

Are you using the correct DVI to HDMI adapter from ATI? Not any adapter will work. It must be specifically made for this purpose so that audio will transfer. With generic ones audio won't transfer.

1) Receiver is set to audio over HDMI
2) Computer has HDMI audio enabled in the BIOS, and ATI HDMI Audio is selected as the output device. On occasion, though, the only sound output device is Realtek HD Audio, but reinstalling Realtek drivers tends to at least enable ATI HDMI Audio device
3) The motherboard (M2A-VM HDMI) comes with a PCI-Express breakout card that has a real HDMI port, SPDIF coax out, and S-Video and Composite out. (The S-Video connector also serves the Component out dongle). Therefore, I have a straight HDMI-HDMI cable going to the receiver. And, again, it works just ducky if I connect HDMI out on the computer to HDMI in on the TV.

Oh well, since I still like the Yamaha, it's time to start shopping for nVidia 8200 motherboards...
Odeen is offline  
post #25 of 103 Old 06-13-2008, 11:14 AM
Member
 
goemonate's Avatar
 
Join Date: Nov 2006
Posts: 62
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
This is my result. My plasmas is Pioneer 435.
------------------------------------------
Monitor
Windows description......... Generic PnP Monitor
Manufacturer description.... PDP-R05
Manufacturer................ Pioneer
??????????????
Plug and Play ID............ PIO0047
Serial number............... n/a
EDID data source............ Registry (stored)
??????????????
Manufacture date............ 2005
EDID revision............... 1.3
Display type and signal..... Digital
Sync input support.......... n/a
Screen size................. 960 x 540 mm (~45")
Power management............ Active off/sleep

Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.683 - Ry 0.317
Green chromaticity.......... Gx 0.313 - Gy 0.581
Blue chromaticity........... Bx 0.139 - By 0.050
White point (default)....... Wx 0.289 - Wy 0.280

Timing characteristics
VESA GTF support............ Not supported
Horizontal scan range....... 15-46kHz
Vertical scan range......... 49-61Hz
Video bandwidth............. 80MHz
Extension blocks............ 1
Timing recommendation #1.... 1920x540 at 50Hz
Modeline................ "1920x540" 74.250 1920 2448 2492 2640 540 574 579 562 +hsync +vsync
Timing recommendation #2.... 1920x1080 at 25Hz
Modeline................ "1920x1080" 74.250 1920 2448 2492 2640 1080 1148 1158 1124 interlace +hsync +vsync
Timing recommendation #3.... 720x576 at 50Hz
Modeline................ "720x576" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync

Standard timings supported
720 x 576 at 50Hz - Pioneer
1920 x 540 at 50Hz - Pioneer
1920 x 1080 at 25Hz - Pioneer

Raw EDID base
00: 00 FF FF FF FF FF FF 00 41 2F 47 00 01 01 01 01
10: 00 0F 01 03 80 60 36 78 2A D7 B3 AE 51 50 94 23
20: 0C 4A 47 00 00 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 01 01 1D 80 D0 72 1C 16 20 10 2C
40: 25 80 B8 18 32 00 00 9E 8C 0A D0 90 20 40 31 20
50: 0C 40 55 00 B8 18 32 00 00 18 00 00 00 FD 00 31
60: 3D 0F 2E 08 00 0A 20 20 20 20 20 20 00 00 00 FC
70: 00 50 44 50 2D 52 30 35 0A 20 20 20 20 20 01 45

Raw EDID extension (reserved)
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Display adapter
Adapter description......... ATI Radeon HD 3400 Series
Adapter device ID........... 0x95C51002
Display settings............ 1280x720, 32bpp

User/computer information
Registered user name........ HTPC
Registered organization..... n/a
Network user name........... HTPC
Network computer name....... HTPC-PC
Windows version ............ Windows 2000
Windows build .............. 6.00.6001 Service Pack 1
Installation date .......... 20/4/2008 12:00:00
goemonate is offline  
post #26 of 103 Old 06-13-2008, 11:47 AM
Senior Member
 
Meparch's Avatar
 
Join Date: Mar 2008
Posts: 222
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I got this lemon of a receiver too. You guys do realize is clips the video signal from 0-255 to 16-235? Best to just pass hdmi straight to the TV and audio via optical to the receiver. Most of the files out there are compressed as is, so standard 5.1 is fine. I plan to pick up one of the new 80gigs for SACD and blurays as soon as more stores other than fleebay actually have them for sale.
Meparch is offline  
post #27 of 103 Old 06-13-2008, 12:09 PM
AVS Special Member
 
Wo0zy's Avatar
 
Join Date: Sep 2007
Posts: 1,816
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by goemonate View Post

This is my result. My plasmas is Pioneer 435.
------------------------------------------
Monitor
Windows description......... Generic PnP Monitor
Manufacturer description.... PDP-R05
Manufacturer................ Pioneer
??????????????
Plug and Play ID............ PIO0047
Serial number............... n/a
EDID data source............ Registry (stored)
??????????????
Manufacture date............ 2005
EDID revision............... 1.3
Display type and signal..... Digital
Sync input support.......... n/a
Screen size................. 960 x 540 mm (~45")
Power management............ Active off/sleep

Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.683 - Ry 0.317
Green chromaticity.......... Gx 0.313 - Gy 0.581
Blue chromaticity........... Bx 0.139 - By 0.050
White point (default)....... Wx 0.289 - Wy 0.280

Timing characteristics
VESA GTF support............ Not supported
Horizontal scan range....... 15-46kHz
Vertical scan range......... 49-61Hz
Video bandwidth............. 80MHz
Extension blocks............ 1
Timing recommendation #1.... 1920x540 at 50Hz
Modeline................ "1920x540" 74.250 1920 2448 2492 2640 540 574 579 562 +hsync +vsync
Timing recommendation #2.... 1920x1080 at 25Hz
Modeline................ "1920x1080" 74.250 1920 2448 2492 2640 1080 1148 1158 1124 interlace +hsync +vsync
Timing recommendation #3.... 720x576 at 50Hz
Modeline................ "720x576" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync

Standard timings supported
720 x 576 at 50Hz - Pioneer
1920 x 540 at 50Hz - Pioneer
1920 x 1080 at 25Hz - Pioneer

Raw EDID base
00: 00 FF FF FF FF FF FF 00 41 2F 47 00 01 01 01 01
10: 00 0F 01 03 80 60 36 78 2A D7 B3 AE 51 50 94 23
20: 0C 4A 47 00 00 00 01 01 01 01 01 01 01 01 01 01
30: 01 01 01 01 01 01 01 1D 80 D0 72 1C 16 20 10 2C
40: 25 80 B8 18 32 00 00 9E 8C 0A D0 90 20 40 31 20
50: 0C 40 55 00 B8 18 32 00 00 18 00 00 00 FD 00 31
60: 3D 0F 2E 08 00 0A 20 20 20 20 20 20 00 00 00 FC
70: 00 50 44 50 2D 52 30 35 0A 20 20 20 20 20 01 45

Raw EDID extension (reserved)
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Display adapter
Adapter description......... ATI Radeon HD 3400 Series
Adapter device ID........... 0x95C51002
Display settings............ 1280x720, 32bpp

User/computer information
Registered user name........ HTPC
Registered organization..... n/a
Network user name........... HTPC
Network computer name....... HTPC-PC
Windows version ............ Windows 2000
Windows build .............. 6.00.6001 Service Pack 1
Installation date .......... 20/4/2008 12:00:00

Thanks but I'm guessing you used MonInfo which doesn't seem to pass the extension block these days and I know there is one because the second to last byte is "01".

Try looking in the registry under HKLM\\System\\CurrentControlSet\\Enum\\Display

There should be an entry with a title that resembles the name of your AVR. Under here there will be a long ID key and under here you'll find a "Device Parameters" key and under here (at last) will be an "EDID" binary value. Export the whole key and post that. If the extension block is being read (or not as with the 606) this will tell me.

Thanks,

Wo0zy
Wo0zy is offline  
post #28 of 103 Old 06-13-2008, 12:14 PM
AVS Special Member
 
Wo0zy's Avatar
 
Join Date: Sep 2007
Posts: 1,816
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Meparch View Post

I got this lemon of a receiver too. You guys do realize is clips the video signal from 0-255 to 16-235?

So do most HDTV's if they are spec compliant and use "video" levels" but you should be able to compensate if you have an ATI card.

Check out the last few pages of the Radeon 2xxx thread. This will explain further.

Wo0zy
Wo0zy is offline  
post #29 of 103 Old 06-13-2008, 12:28 PM
Senior Member
 
Meparch's Avatar
 
Join Date: Mar 2008
Posts: 222
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
My samsung 52A650 will do 0-255 just fine. I do have to readjust the TV when playing video sources so those don't look washed out.
Meparch is offline  
post #30 of 103 Old 06-13-2008, 02:37 PM
AVS Special Member
 
Wo0zy's Avatar
 
Join Date: Sep 2007
Posts: 1,816
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Meparch View Post

My samsung 52A650 will do 0-255 just fine. I do have to readjust the TV when playing video sources so those don't look washed out.

There are TV's with support for PC levels (no question) but if you use an ATI DVI>HDMI dongle, output levels will be compressed to 16-235 (video levels) anyway. You'll also need to apply the "UseBT601CSC=1" registry tweak and then all levels will be displayed the same on a display that is calibrated for video (SD, HD and desktop)

There are a few threads here which will provide further details. If you can't find the information let me know and I'll point you in the right direction.

Wo0zy
Wo0zy is offline  
Reply Home Theater Computers

User Tag List

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off