v1.23 CRT Support - Timing adjustments? NEED to be able to tweak
I had a 3D Vision kit a while ago but returned it to the Fry's where I purchased it when I wasn't able to get satisfactory results with the CRT displays I have.
The list of supported devices does still show "â—¦100 Hz and higher analog CRTs" and I would like to be able to use at least one of the monitors we have.
Our monitors all displayed different levels of ghosting on different parts of the display - either at the top or bottom. But for each one it remained consistent at different refresh rates which to me points more toward sync timing issues than phosphor decay (which increases in significance as the HZ go up).
It seems clear to me that being able to adjust the timing is key to getting usable results with a CRT monitor. The one generic set of timings does not produce consistent results on my displays. Being able to adjust the timings (even just exposed as registry settings outside the general UI) would make it so we could mitigate the ghosting/crosstalk.
In any event I'm eager to know if the new v1.23 drivers have any changes or adjustments for supporting CRT displays. Is there anything new?
I had a 3D Vision kit a while ago but returned it to the Fry's where I purchased it when I wasn't able to get satisfactory results with the CRT displays I have.
The list of supported devices does still show "â—¦100 Hz and higher analog CRTs" and I would like to be able to use at least one of the monitors we have.
Our monitors all displayed different levels of ghosting on different parts of the display - either at the top or bottom. But for each one it remained consistent at different refresh rates which to me points more toward sync timing issues than phosphor decay (which increases in significance as the HZ go up).
It seems clear to me that being able to adjust the timing is key to getting usable results with a CRT monitor. The one generic set of timings does not produce consistent results on my displays. Being able to adjust the timings (even just exposed as registry settings outside the general UI) would make it so we could mitigate the ghosting/crosstalk.
In any event I'm eager to know if the new v1.23 drivers have any changes or adjustments for supporting CRT displays. Is there anything new?
I dont get it. Is there really a strong business case not to expose timing adjustments?
It seems like many people are experiencing ghosting issues even with supported displays. CRT in particular seems like there is a good deal of variation in performance from one display to another.
I also wonder about the consistency in USB timing from PC to PC. In general USB does not guarantee real time performance and I would think with the sensitivity of timing for 120Hz stereo having user adjustments would be a basic requriement.
I dont get it. Is there really a strong business case not to expose timing adjustments?
It seems like many people are experiencing ghosting issues even with supported displays. CRT in particular seems like there is a good deal of variation in performance from one display to another.
I also wonder about the consistency in USB timing from PC to PC. In general USB does not guarantee real time performance and I would think with the sensitivity of timing for 120Hz stereo having user adjustments would be a basic requriement.
The list of supported devices does still show "â—¦100 Hz and higher analog CRTs" and I would like to be able to use at least one of the monitors we have.
Our monitors all displayed different levels of ghosting on different parts of the display - either at the top or bottom. But for each one it remained consistent at different refresh rates which to me points more toward sync timing issues than phosphor decay (which increases in significance as the HZ go up).
It seems clear to me that being able to adjust the timing is key to getting usable results with a CRT monitor. The one generic set of timings does not produce consistent results on my displays. Being able to adjust the timings (even just exposed as registry settings outside the general UI) would make it so we could mitigate the ghosting/crosstalk.
In any event I'm eager to know if the new v1.23 drivers have any changes or adjustments for supporting CRT displays. Is there anything new?
The list of supported devices does still show "â—¦100 Hz and higher analog CRTs" and I would like to be able to use at least one of the monitors we have.
Our monitors all displayed different levels of ghosting on different parts of the display - either at the top or bottom. But for each one it remained consistent at different refresh rates which to me points more toward sync timing issues than phosphor decay (which increases in significance as the HZ go up).
It seems clear to me that being able to adjust the timing is key to getting usable results with a CRT monitor. The one generic set of timings does not produce consistent results on my displays. Being able to adjust the timings (even just exposed as registry settings outside the general UI) would make it so we could mitigate the ghosting/crosstalk.
In any event I'm eager to know if the new v1.23 drivers have any changes or adjustments for supporting CRT displays. Is there anything new?
It seems like many people are experiencing ghosting issues even with supported displays. CRT in particular seems like there is a good deal of variation in performance from one display to another.
I also wonder about the consistency in USB timing from PC to PC. In general USB does not guarantee real time performance and I would think with the sensitivity of timing for 120Hz stereo having user adjustments would be a basic requriement.
It seems like many people are experiencing ghosting issues even with supported displays. CRT in particular seems like there is a good deal of variation in performance from one display to another.
I also wonder about the consistency in USB timing from PC to PC. In general USB does not guarantee real time performance and I would think with the sensitivity of timing for 120Hz stereo having user adjustments would be a basic requriement.