AVS › AVS Forum › Video Components › Home Theater Computers › Yamaha RX-V663 and ATI card will not transmit HDMI audio, email ATI and Yamaha!
New Posts  All Forums:Forum Nav:

Yamaha RX-V663 and ATI card will not transmit HDMI audio, email ATI and Yamaha! - Page 3

post #61 of 317
8/14/08 at 1:31pm
Please give me your results in moninfo reports - I'll try to analyse
Idea is the same: 3 reports as discribe before
Reply
Reply

AVS Top Picks

post #62 of 317
8/14/08 at 3:22pm
Quote:
Originally Posted by Mikl1984 View Post

Please give me your results in moninfo reports - I'll try to analyse
Idea is the same: 3 reports as discribe before

I've already analysed the results hence my previous comments but I'll post the reports for you when I return to work on Monday. In the mean time I'll recount the findings for you.

The main config we're currently using for testing is an Onkyo 606 with a Sharp Aquos 32" LCD TV (Full HD).

The 606 has 4 HDMI inputs. When connecting an Intel G35 system to any of the inputs the EDID is correctly interpreted and both audio and video functions correctly. The available video formats (as defined by the EDID) are all present and correct including resolutions/ timings defined in DTD's, SVD's and Established Timings). DD, DTS and multi-channel LPCM audio are all selectable which you would expect as the EDID report (which can be obtained by generating a "Diagnostic Report" from with the Intel drivers) includes a correct 1.3 extension block which contains the relevant SAD's. It also contains SAD's for other audio formats but this is irrelevant to the problem.

When you connect an ATI system to the Onkyo receiver you get different results depending on which HDMI input you use. When connecting to HDMI1 both audio and video work as expected. The EDID stored in the registry exactly matches the EDID reported by the Intel diagnostic report when it is connected to HDMI1. Moninfo also reports an identical EDID.

When you connect an ATI system to any of the other HDMI inputs you can get video but no audio. When you examine the stored EDID you can see that the first block is correct but instead of the correct 1.3 extension block you see a repeat of the first block. This also means that any video timing stored in the extension block (DTD's or SVD's) are not selectable. However, when you use Moninfo it correctly reports the extension block (which exactly matches the EDID obtained using the Intel system).

The only differences in the EDID (when correctly read) between thefFirst HDMI input and the second (and 3rd and 4th) is a difference in the VSDB (relating to the CEC physical address) and obviously the checksum.

The fact that the Intel system currently reads the EDID from all Onkyo HDMI inputs as does Moninfo when it performs a direct DDC/I2C call is why I'm fairly sure this problem is specific to the ATI drivers at some level. Maybe there is another issue which is specific to the Yamaha situation but as you can see, our results strongly suggest (if not prove) that the issue with the Onkyo 606 (and maybe other Onkyo's) isn't caused by malformed EDID.

Wo0zy
Reply
Reply
post #63 of 317
8/14/08 at 8:26pm
Quote:
Originally Posted by Wo0zy View Post

When you connect an ATI system to any of the other HDMI inputs you can get video but no audio. When you examine the stored EDID you can see that the first block is correct but instead of the correct 1.3 extension block you see a repeat of the first block.
Wo0zy

Ok
Waiting reports. In your case 4x3.
Are you try to clean wrong registry records?
Please make reports for those wrong records too.
It may be key point in your case.
Reply
Reply
post #64 of 317
8/15/08 at 4:26am
Quote:
Originally Posted by Mikl1984 View Post

Ok
Waiting reports. In your case 4x3.
Are you try to clean wrong registry records?
Please make reports for those wrong records too.
It may be key point in your case.

Yes. We removed all registry entries just in case. The newly created entries also have the same problem.

BTW I should also mention that these findings are the same for 4 test ATI systems (X1250, 2600, 3650, 4850) so we're also fairly sure it's not graphics hardware specific and our findings have been confirmed by several of our resellers (those unlucky enough to have a "problem" combination).

Anyway, I'll happily send you the reports on Monday but sadly I'm not sure what you'll be able to find unless you work for ATI (please ) but I really hope I'm wrong.

What do you expect to find?

Thanks,

Wo0zy
Reply
Reply
post #65 of 317
8/15/08 at 6:18am
Quote:
Originally Posted by Wo0zy View Post

Anyway, I'll happily send you the reports on Monday but sadly I'm not sure what you'll be able to find unless you work for ATI (please ) but I really hope I'm wrong.

Yes, I have some connections with Toronto guys during last 12 years
More info from you - more chances to resolve issue
Reply
Reply
post #66 of 317
8/15/08 at 11:08am
Quote:
Originally Posted by Mikl1984 View Post

Yes, I have some connections with Toronto guys during last 12 years
More info from you - more chances to resolve issue

Good stuff

Reports to go with the findings will be with you Monday.

I hope other people will forward you some information as well!

Wo0zy
Reply
Reply
post #67 of 317
8/15/08 at 9:56pm
Quote:
Originally Posted by Mikl1984 View Post
Only real time reports are interesting
Please make reports for following configs
1. HTPC-Yamaha-Mitsubishi
2. Switch off Mitsubishi (or even better disconnect HDMI Out on recever) and make the same report
3. HTPC-Mitsubishi

Off course to avoid "blind" button press for config №2 better to connect second monitor to HTPC

Good luck
And here you are. I hope these can be of some help.

 

HTPC-HC3000U.txt 3k . file

 

HTPC-HTR6160.txt 3.9326171875k . file

 

HTPC-HTR6160-HC3000U.txt 3.72265625k . file
Reply
Reply
post #68 of 317
8/17/08 at 6:59am
Quote:
Originally Posted by Cpt. Jack View Post

And here you are. I hope these can be of some help.

Thanks for reports

Some analisis:

1. Your problem isn't issue of EDID
Audio reported right way.

I don't have any problem with 2-channel LPCM via HDMI on the same chipset and RX-V2700.
As temporary solution I recommend to use S/PDIF - no problem with 2-channel LPCM, DD & DTS for your chipset.


2. Yamaha use wrong way as repeater to modify EDID of your projector in
- Video Part (add own resolution which not supported by your projector and change native resolutions)
- CEC (you are not able to communicate with your projector via this interface)
Reply
Reply
post #69 of 317
8/17/08 at 10:50am
Answer to our prairs or buggus?
http://www.avsforum.com/avs-vb/showthread.php?t=1056687
http://www.cepro.com/article/honeywe..._corrupt_data/
Reply
Reply
post #70 of 317
8/17/08 at 1:26pm
Quote:
Originally Posted by Mikl1984 View Post
Thanks for reports

Some analisis:

1. Your problem isn't issue of EDID
Audio reported right way.

I don't have any problem with 2-channel LPCM via HDMI on the same chipset and RX-V2700.
As temporary solution I recommend to use S/PDIF - no problem with 2-channel LPCM, DD & DTS for your chipset.


2. Yamaha use wrong way as repeater to modify EDID of your projector in
- Video Part (add own resolution which not supported by your projector and change native resolutions)
- CEC (you are not able to communicate with your projector via this interface)
I have an Intel G33 based Shuttle with an Onkyo TX-SR806 and a Panasonic plasma.
  • Intel GMA and HDMI audio with Onkyo works fine, full 7.1 audio.
  • 4850 will not show up as an HDMI device unless connected directly to Panny, shows up as DVI thus no audio.

Moninfo reports with 4850 connected directly to TV and 4850 connected to Onkyo 806 attahed.

 

pan.txt 3.1611328125k . file

 

onkyo806.txt 1.869140625k . file
Reply
Reply
post #71 of 317
8/17/08 at 9:51pm
Quote:
Originally Posted by kemac View Post

I have an Intel G33 based Shuttle with an Onkyo TX-SR806 and a Panasonic plasma.
  • Intel GMA and HDMI audio with Onkyo works fine, full 7.1 audio.
  • 4850 will not show up as an HDMI device unless connected directly to Panny, shows up as DVI thus no audio.

Moninfo reports with 4850 connected directly to TV and 4850 connected to Onkyo 806 attahed.

Moninfo has limited compatibility with 48X0

But you have right report for your TV
Is it connected via G33?

According report for Onkyo no EDID (HDMI or DVI) exist at all.
Please make sure that you choose Real time (not Registry) entry report
Try to receive it via G33.
Reply
Reply
post #72 of 317
8/18/08 at 6:11am
Quote:
Originally Posted by Mikl1984 View Post
Moninfo has limited compatibility with 48X0

But you have right report for your TV
Is it connected via G33?

According report for Onkyo no EDID (HDMI or DVI) exist at all.
Please make sure that you choose Real time (not Registry) entry report
Try to receive it via G33.
That is the correct report for the TV however I may have attached an old report for the receiver so I am attaching a new one.

Moninfo didn't report any EDID/audio information for the G33 even thou I had 8ch PCM so I assume moninfo is even more limited for intel?

 

onkyo806.txt 1.869140625k . file
Reply
Reply
post #73 of 317
8/18/08 at 6:31am
Quote:
Originally Posted by kemac View Post

That is the correct report for the TV however I may have attached an old report for the receiver so I am attaching a new one.

Moninfo didn't report any EDID/audio information for the G33 even thou I had 8ch PCM so I assume moninfo is even more limited for intel?

Use the Intel "information" button in the Graphics Tray to produce a diagnostic report. When you save the file the resulting .txt contains the Raw EDID. You can either manually decode it of use DTDCalc to "interpret" it for you (alternatively post the file and I'll do it for you). My guess is the reported capabilities will match the moninfo report from the ATI system.

Would you mind doing something for me? On the ATI system, could you export and post the corresponding registry key for for the Onkyo connection? You should be able to find it in

HKLM\\System\\CurrentControlSet\\Enum\\Display.

Once you find the Onkyo Entry, drill down and find "Device Parameters". In there you'll find the EDID Key. Why guess is the EDID found here will not be correct.

Mikl1984 will then see what I'm talking about in my previous posts.

Mikl1984, I won't be in the office until tomorrow now. I'll post my reports for you then.

Thanks,

Wo0zy
Reply
Reply
post #74 of 317
8/18/08 at 7:02am
Quote:
Originally Posted by Wo0zy View Post

Use the Intel "information" button in the Graphics Tray to produce a diagnostic report. When you save the file the resulting .txt contains the Raw EDID. You can either manually decode it of use DTDCalc to "interpret" it for you (alternatively post the file and I'll do it for you). My guess is the reported capabilities will match the moninfo report from the ATI system.

Would you mind doing something for me? On the ATI system, could you export and post the corresponding registry key for for the Onkyo connection? You should be able to find it in

HKLM\\System\\CurrentControlSet\\Enum\\Display.

Once you find the Onkyo Entry, drill down and find "Device Parameters". In there you'll find the EDID Key. Why guess is the EDID found here will not be correct.

Mikl1984 will then see what I'm talking about in my previous posts.

Mikl1984, I won't be in the office until tomorrow now. I'll post my reports for you then.

Thanks,

Wo0zy

Thanks Wo0zy, I knew their was a way to print out the EDID info with the Intel Driver, since I couldn't see my taskbar because of overscan I didn't think to look there.

Mikl1984, if you still need the Intel EDID I can send it to you, its just time consuming to switch back and forth since its the same system with jumpers on the motherboard I have to change etc.


Here is the ATI EDID

Code:
[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\DISPLAY\\ONK0882\\5&3741c1f7&0&UID268435460\\Device Parameters]
"EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,3d,cb,82,08,00,00,00,00,00,12,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,98,06,32,00,00,1e,\\
  01,1d,80,18,71,1c,16,20,58,2c,25,00,98,06,32,00,00,9e,00,00,00,fc,00,54,58,\\
  2d,53,52,38,30,36,0a,20,20,20,20,00,00,00,fd,00,3b,3d,0f,44,0f,00,0a,20,20,\\
  20,20,20,20,01,43,00,ff,ff,ff,ff,ff,ff,00,3d,cb,82,08,00,00,00,00,00,12,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,98,06,32,\\
  00,00,1e,01,1d,80,18,71,1c,16,20,58,2c,25,00,98,06,32,00,00,9e,00,00,00,fc,\\
  00,54,58,2d,53,52,38,30,36,0a,20,20,20,20,00,00,00,fd,00,3b,3d,0f,44,0f,00,\\
  0a,20,20,20,20,20,20,01,43
Reply
Reply
post #75 of 317
8/18/08 at 9:22am
Quote:
Originally Posted by kemac View Post

Thanks Wo0zy, I knew their was a way to print out the EDID info with the Intel Driver, since I couldn't see my taskbar because of overscan I didn't think to look there.

Mikl1984, if you still need the Intel EDID I can send it to you, its just time consuming to switch back and forth since its the same system with jumpers on the motherboard I have to change etc.


Here is the ATI EDID

Code:
[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\DISPLAY\\ONK0882\\5&3741c1f7&0&UID268435460\\Device Parameters]
"EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,3d,cb,82,08,00,00,00,00,00,12,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,98,06,32,00,00,1e,\\
  01,1d,80,18,71,1c,16,20,58,2c,25,00,98,06,32,00,00,9e,00,00,00,fc,00,54,58,\\
  2d,53,52,38,30,36,0a,20,20,20,20,00,00,00,fd,00,3b,3d,0f,44,0f,00,0a,20,20,\\
  20,20,20,20,01,43,00,ff,ff,ff,ff,ff,ff,00,3d,cb,82,08,00,00,00,00,00,12,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,98,06,32,\\
  00,00,1e,01,1d,80,18,71,1c,16,20,58,2c,25,00,98,06,32,00,00,9e,00,00,00,fc,\\
  00,54,58,2d,53,52,38,30,36,0a,20,20,20,20,00,00,00,fd,00,3b,3d,0f,44,0f,00,\\
  0a,20,20,20,20,20,20,01,43

Thanks kemac.

If you format the EDID like so

00 ff ff ff ff ff ff 00 3d cb 82 08 00 00 00 00
00 12 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 98 06 32 00 00 1e 01 1d 80 18 71 1c 16 20
58 2c 25 00 98 06 32 00 00 9e 00 00 00 fc 00 54
58 2d 53 52 38 30 36 0a 20 20 20 20 00 00 00 fd
00 3b 3d 0f 44 0f 00 0a 20 20 20 20 20 20 01 43
00 ff ff ff ff ff ff 00 3d cb 82 08 00 00 00 00
00 12 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 98 06 32 00 00 1e 01 1d 80 18 71 1c 16 20
58 2c 25 00 98 06 32 00 00 9e 00 00 00 fc 00 54
58 2d 53 52 38 30 36 0a 20 20 20 20 00 00 00 fd
00 3b 3d 0f 44 0f 00 0a 20 20 20 20 20 20 01 43

You'll see that the second block is a repeat of the first as per my previous posts.

If you do get a chance to produce the Intel report and compare the EDID data you'll see that the first 8 lines are the same (the first block) but the second 8 lines (the extension block) will be completely different.

However, this isn't the same EDID that Moninfo reports when it does a direct DDC call. If it was, you wouldn't get an accurate assessment of the audio capabilities. You can compare this for yourself within Moninfo.

Mikl1984, this is exactly what we see in the lab. I'll still produce my reports for you tomorrow but this is a perfect example.

Wo0zy
Reply
Reply
post #76 of 317
8/18/08 at 11:49am
Quote:
Originally Posted by kemac View Post

That is the correct report for the TV however I may have attached an old report for the receiver so I am attaching a new one.

Good report, thanks
Please make real-time report for TV-Onkyo-PC too
Reply
Reply
post #77 of 317
8/18/08 at 12:40pm
Quote:
Originally Posted by Mikl1984 View Post

Good report, thanks
Please make real-time report for TV-Onkyo-PC too

Moninfo report and Intel Diagnostic report with EDID attached.

If you or Wo0zy need anything else please let me know.
Reply
Reply
post #78 of 317
8/18/08 at 12:42pm
Quote:
Originally Posted by kemac View Post
Moninfo report and Intel Diagnostic report with EDID attached.

If you or Wo0zy need anything else please let me know.
Here are the attachments!

 

intel.txt 3.97265625k . file

 

DiagnosticReport.txt 2.375k . file
Reply
Reply
post #79 of 317
8/18/08 at 1:30pm
Quote:
Originally Posted by kemac View Post

Here are the attachments!

Wrong EDID report
Extension blocs.......... 1 but no ext block in reality

Abs different situation in comparison with last Yamaha case!

Are you able to make it with previous generation cards (ATI less than 4XXX, Nvidia less than 9XXX)?

Intel report right??? EDID according DTD Calc, but not fully decode every byte of it (VSDB&HD Formats).
No Established Timings Found
Block 1 DTD Found (See List)
Block 1 DTD Found (See List)
Display does not support underscan
Display supports basic audio
Display supports YCbCr 4:4:4
Display supports YCbCr 4:2:2
1 native formats in DTDs
Short Video Descriptor:
Resolution Supported - 1920x1080p @ 59.94/60Hz 16:9 Native
Short Video Descriptor:
Resolution Supported - 1920x1080i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 1280x720p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480p @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480i @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 640x480p @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 1440x480p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 1440x480p @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 2880x480i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 2880x480i @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Short Video Descriptor:
Short Audio Descriptor:
Audio Format - LPCM
2 Channel Sound
Sampling Frequencies Supported :192kHz, 176kHz, 96kHz, 88kHz, 48kHz, 44kHz, 32kHz
Bit Depth :24 bit, 20 bit, 16 bit
Short Audio Descriptor:
Audio Format - LPCM
8 Channel Sound
Sampling Frequencies Supported :192kHz, 176kHz, 96kHz, 88kHz, 48kHz, 44kHz, 32kHz
Bit Depth :24 bit, 20 bit, 16 bit
Short Audio Descriptor:
Audio Format - AC-3
8 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz, 32kHz
Maximum supported bitrate :640
Short Audio Descriptor:
Audio Format - DTS
8 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz
Maximum supported bitrate :1536
Short Audio Descriptor:
6 Channel Sound
Sampling Frequencies Supported :44kHz
Short Audio Descriptor:
8 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz
Short Audio Descriptor:
8 Channel Sound
Sampling Frequencies Supported :192kHz, 176kHz, 96kHz, 88kHz, 48kHz, 44kHz
Maximum supported bitrate :8
Short Audio Descriptor:
8 Channel Sound
Sampling Frequencies Supported :192kHz, 96kHz, 48kHz
Speaker Allocation Block :
Speakers Present :
Rear Left Centre / Rear Right Centre
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)

Also find reporting issue in moninfo - doesn't report aspect ratio for
720x480p at 60Hz
1440x480i at 60Hz
Will inform Rik from Entech
http://forums.entechtaiwan.net/viewtopic.php?t=6387
Reply
Reply
post #80 of 317
8/18/08 at 2:26pm
Quote:
Originally Posted by Mikl1984 View Post

Thanks for reports
I don't have any problem with 2-channel LPCM via HDMI on the same chipset and RX-V2700.
As temporary solution I recommend to use S/PDIF - no problem with 2-channel LPCM, DD & DTS for your chipset.

The RX-V2700 is not reported to have the same issue as the RX-V663 (HTR-6160).

That's what I'm doing right now - but that won't let me do DTS-MA or Dolby TrueHD, which is the point of running HDMI audio, at least to me. I'm assuming that ATI will eventually work this out.
Reply
Reply
post #81 of 317
8/18/08 at 2:28pm
Quote:
Originally Posted by bokis View Post

Answer to our prairs or buggus?
http://www.avsforum.com/avs-vb/showthread.php?t=1056687
http://www.cepro.com/article/honeywe..._corrupt_data/

Except that the trouble isn't with the EDID itself - it looks to be a problem with the way ATI is handling it.
Reply
Reply
post #82 of 317
8/18/08 at 2:28pm
Quote:
Originally Posted by Mikl1984 View Post

Wrong EDID report
Extension blocs.......... 1 but no ext block in reality

Abs different situation in comparison with last Yamaha case!

Are you able to make it with previous generation cards (ATI less than 4XXX, Nvidia less than 9XXX)?

Intel report right??? EDID according DTD Calc, but not fully decode every byte of it (VSDB&HD Formats).
No Established Timings Found
Block 1 DTD Found (See List)
Block 1 DTD Found (See List)
Display does not support underscan
Display supports basic audio
Display supports YCbCr 4:4:4
Display supports YCbCr 4:2:2
1 native formats in DTDs
Short Video Descriptor:
Resolution Supported - 1920x1080p @ 59.94/60Hz 16:9 Native
Short Video Descriptor:
Resolution Supported - 1920x1080i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 1280x720p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480p @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 720x480i @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 640x480p @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 1440x480p @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 1440x480p @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Resolution Supported - 2880x480i @ 59.94/60Hz 16:9 Non-Native
Short Video Descriptor:
Resolution Supported - 2880x480i @ 59.94/60Hz 4:3 Non-Native
Short Video Descriptor:
Short Video Descriptor:
Short Audio Descriptor:
Audio Format - LPCM
2 Channel Sound
Sampling Frequencies Supported :192kHz, 176kHz, 96kHz, 88kHz, 48kHz, 44kHz, 32kHz
Bit Depth :24 bit, 20 bit, 16 bit
Short Audio Descriptor:
Audio Format - LPCM
8 Channel Sound
Sampling Frequencies Supported :192kHz, 176kHz, 96kHz, 88kHz, 48kHz, 44kHz, 32kHz
Bit Depth :24 bit, 20 bit, 16 bit
Short Audio Descriptor:
Audio Format - AC-3
8 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz, 32kHz
Maximum supported bitrate :640
Short Audio Descriptor:
Audio Format - DTS
8 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz
Maximum supported bitrate :1536
Short Audio Descriptor:
6 Channel Sound
Sampling Frequencies Supported :44kHz
Short Audio Descriptor:
8 Channel Sound
Sampling Frequencies Supported :48kHz, 44kHz
Short Audio Descriptor:
8 Channel Sound
Sampling Frequencies Supported :192kHz, 176kHz, 96kHz, 88kHz, 48kHz, 44kHz
Maximum supported bitrate :8
Short Audio Descriptor:
8 Channel Sound
Sampling Frequencies Supported :192kHz, 96kHz, 48kHz
Speaker Allocation Block :
Speakers Present :
Rear Left Centre / Rear Right Centre
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)
Block 2 DTD Found (See List)

Also find reporting issue in moninfo - doesn't report aspect ratio for
720x480p at 60Hz
1440x480i at 60Hz
Will inform Rik from Entech
http://forums.entechtaiwan.net/viewtopic.php?t=6387

This might help Rik Wang but it won't help resolve the problem .

DTDCalc doesn't fully report all HD audio formats because we don't have access to all the SAD data yet (need to purchase the latest spec docs first) but as you can see, Intel IGP's have no issue reporting the correct EDID (including the extension block) where as calls by the ATI drivers do. Minor descrepancies with Moninfo are not relevant.

I think we're working towards the same objective but language is causing a problem. Sorry my Russian isn't anywhere near as good as your English

ATI need to address this.

Wo0zy
Reply
Reply
post #83 of 317
8/18/08 at 2:42pm
Quote:
Originally Posted by Mikl1984 View Post
Are you able to make it with previous generation cards (ATI less than 4XXX, Nvidia less than 9XXX)?
Attached is the moninfo report for an 8500GT and registry export with the EDID.

Hope this helps!

 

8500gt.txt 6.09375k . file

 

8500gt.reg.txt 1.921875k . file
Reply
Reply
post #84 of 317
8/18/08 at 9:21pm
Quote:
Originally Posted by Wo0zy View Post

but as you can see, Intel IGP's have no issue reporting the correct EDID (including the extension block) where as calls by the ATI drivers do.
ATI need to address this.

I abs agree with you. But I try to understand why it happened.
And in this case all details are important.

Quote:
Originally Posted by kemac View Post

Attached is the moninfo report for an 8500GT and registry export with the EDID.

Please make report for TV-Onkyo-PC with this 8500
Reply
Reply
post #85 of 317
8/19/08 at 5:37am
Quote:
Originally Posted by Mikl1984 View Post

Id
Please make report for TV-Onkyo-PC with this 8500

I provided a Moninfo report and the EDID info attached to my last post when using an 8500. Is their something else your looking for?
Reply
Reply
post #86 of 317
8/19/08 at 11:11am
Last 8500gt.txt show Onkyo EDID, not your TV
Model name............... TX-SR806
Manufacturer............. ONK
Plug and Play ID......... ONK0882

Something wrong
Reply
Reply
post #87 of 317
8/19/08 at 11:24am
Quote:
Originally Posted by Mikl1984 View Post

Last 8500gt.txt show Onkyo EDID, not your TV
Model name............... TX-SR806
Manufacturer............. ONK
Plug and Play ID......... ONK0882

Something wrong

Right, isn't this you asked for TV-Onkyo-PC , do you need a report without the Onkyo in the middle? Did you mean to ask for TV-PC?
Reply
Reply
post #88 of 317
8/19/08 at 1:54pm
No
In this case Onkyo generate wrong EDID.
As normal repeater according HDMI 1.3a it should copy all EDID info from TV, add own EDID sound info and generate new EDID.

Are there AVR which made it right way?
Reply
Reply
post #89 of 317
8/20/08 at 12:51pm
Hi everyone. I have been following this post since I bought a Sapphire 4850 and an RX-v663. I was hoping that it would be easy to plug it all in and get 5.1, but I am obviously wrong.

Please understand that I am upgrading from a Marantz 2285b from the 70's so hooking things up have been easy up till now. I have no clue and just dont know where to begin when faced with the task of getting it all running properly. I cant even get the setup to display on my monitor.

Does someone know of a post that explains how the components listed below (or similar ones) are setup to get the best picture and best audio out from the pc through the 663 to my 5.1 system and pc monitor? I.E. Do I use hdmi adapter to go through the amp, or just go straight to the monitor? Since audio isnt passed through the hdmi, do I use optical or the digital coax? How is this set up on the amp? How is this set up on the pc and soundblaster software? Which inputs do I use on the back?

I am really sorry if this is really pathetic on my part for not knowing how to do any of this...I am just overwhelmed.

Thanks in advance for any kind help that is offered, as I am about to just pack it up.

My components are as follows:

Sound system:

Yamaha RX-v663
Paradigm Studio 20's for fronts
Klipsch rw-10d sub
Small Energys for rear
Paradigm cc-190 center

PC:

Intel Core 2 Duo 8400
4 gigs DDR2 1066
Gigabyte p35-ds3r motherboard
Sapphire 4850 video card
Soundblaster X-FI Extreme Audio PCI express soundcard
Windows Vista Premium 64 bit
Reply
Reply
post #90 of 317
8/21/08 at 3:37pm
Actually, if all you're needing is 5.1 PCM, it's pretty easy to do. I'm going to assume the following (and if not, look in the other forums for information - it's not really relevant to this topic):

The PC works.
The speakers are connected to the 663 and you've run the YPAO (if not, look it up in your manual and do it).

You'll need to run an optical or coaxial audio cable from your PC to your RX-V663, and configure your sound card (and DVD software) for SPDIF output. You may then either run an HDMI cable from your PC to your RX-V663 and then from the RX-V663 to your display device, or you may connect your display device to your PC directly (although, the OSD on the 663 makes running it through the receiver worthwhile, IMHO).

Either way, you'll need two cables plugged in to your PC - one for audio, and one for video. Hope this helps!
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers

AVS Top Picks

AVS › AVS Forum › Video Components › Home Theater Computers › Yamaha RX-V663 and ATI card will not transmit HDMI audio, email ATI and Yamaha!