AMD/ATI Pixel Clock Patcher
|
03-05-2017, 07:49 PM
Post: #726
|
|||
|
|||
RE: AMD/ATI Pixel Clock Patcher
Quote:Are you sure the monitor can handle lower horizontal blanking values? A monitor can accept lower porch/sync values and still limit the total blanking. I tried driver 16.11.5 and tried patched and not patched. The behaviour is the same like described above. What can we conclude from that? Is it really coincidence that both of my devices (TFT monitor and DLP projector) can exactly go down to hblankmin 57 and not any further? If so, then AMD seems to have made a useful restriction, if normal devices (I consider I have "normal" devices) can´t go below 57 hblank. I myself can´t test if it is the driver or the device, because how will I know that the resolution is "fired" through the DVI/HDMI port (so no restriction of the driver) or not? There is a small hint from my monitor (at least for me) that it is possibly not a violation of the monitor accepted range: My monitor gives an OSD feedback about range violations, it does so for - horizontal frequency too high (all above 84kHz) - vertical frequency too low (all below 48 Hz) - vertical frequency too high (all above 76 Hz) - vertical blanking too high (all above 65) Especially giving an error message for too high vertical blanking leads to assuming that the monitor should give a feedback about too low horizontal blanking as well I think. Instead it simply goes to standby. I´m really not sure about that. What would be a method to be sure that a resolution is really "fired"? I have a multimeter (but not an oscilloscope at home) for measurements. When e.g. a cable is not connected to the DVI port (so it is not terminated) are the signals still lying on the pins? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 13 Guest(s)