Originally Posted by blackcell
What may I ask is this magical INF mod you are performing as a service to those who need it where you appear to be the only one capable of doing? You're just combining two INFs into one with what I assume to be some EDID override modification. Some special tool you're using or what? You could of written up a how-to by now, no? Just curious is all.
Wanna give me a hand?
The technical process is exactly what vladd so precisely describes. T
To tell you thw whole story, the main reason we went into this was 5xxxs cards not bitstreaming on PDVD9 on some AVRs, mostly Denons & Sonys, and to a lesser degree Onkyos. The problem was obviously in the drivers and their (bad) parsing of the audio block, so knowing that the EDID could be modded, it just occurrred to me to replace the audio block of my "failing" Denon EDID with one known to work with the 5xxxs, and this worked wonderfully.
I, we all, certainly expect ATI to work this out ASAP. They "promised" that the problem would be fixed for January or February driver releases, but so far, at least up to 10.2 RC2 beta, nada!
Of course, EDID is also about video, and here we have a real MESS! 1) because of the "weakness", to put it bluntly, of the EDID VESA standard itself. 2) And then we have the already traditional crappiness of ATI drivers in parsing the EDID.
The problem with the EDID standard is most apparent when you have the specific hdmi chain of a HDTV or proj. going through the AVR/AVP to your HTPC. You certainly would expect that the HTPC will receive an EDID with video descriptors from the HDTV + audio descriptors from the AVR/AVP. Right? Simple, isn't it?
Well, from what I've seen so far the EDID VESA standard can be fullfilled in too many different ways. For instance Sonys and HK AVRs tend to have 2 audio blocks!!! Why? OTH compare a wonderfully detailed Sharp Aquos EDID, but try to combine it with a Sony AVR EDID and you'll find that all info doesn't fit in the standard 256-byte EDID allocation.
And what happens when you plug-in a standard PC monitor, i.e. a non-HDTV device, to the AVR/AVP-HTPC chain?
The answer is, you guessed it right?, that with any EDID issue/incompatibility the AVR/AVP EDID gets precedence. If the AVR/AVP video data is in line with your HDTV you shouldn't have any video issues but otherwise
... So the "full mod" consists in replacing all
video data in the AVR/AVP EDID with the HDTV's.
These EDID video mods have helped me
solving unbearable handshake issues with my ATI 4670 & 5770 when switching sources, powering on/off the HDTV or AVR. Most of the time I lost all detection of the HDTV and had to power on/off the HTPC.
In the end, this is the reason that the EDID override feature has been made available by M$ since Vista: to cope with EDID issues that, neither the Windows monitor driver architecture, nor graphic drivers, can solve right now.