BENQ XL2720Z 27" of goodness :) [Version 2 firmware is good]

[GitDat]

Great. I can't create custom resolutions with Surround

[Chief Blur Buster]

Great. I can't create custom resolutions with Surround

Can you at least temporarily undo surround, and test on one monitor? I want to post the news on Blur Busters about a temporary XL2720Z fix that doesn't require waiting for the firmware upgrade. I don't want to have to downgrade my BENQ XL2720Z to verify.

So can you confirm for me, pretty please? Be a volunteer guinea pig

Also, newer WHQL drivers now have a trick that lets you use custom resolutions during Surround Mode. However, try the simpler method of doing single-monitor temporarily.

[LogicElite]

Here is a temporary workaround to reduce BENQ strobe problem (I think)

Going to NVIDIA -> Create Custom Cesolution
-- Set Refresh Rate to "101Hz"
-- Change Timings from "Auto to Manual"
-- Set Vertical Total to "1350"
-- Click "Apply"
-- Switch to "101Hz"

This creates a large 270-line blanking interval between refreshes, which adds a good 2 millisecond delay betwen refreshes. This fits more of the 1ms-2ms pixel transition during the pause between refreshes. In this case, this actually greatly reduced strobe-backlight ghosting a lot, because more of the pixel transition fit inside the blanking interval. That pushes the strobe phasing to be more timed with the vertical blanking interval.

You can't do this at 120Hz because it's literally consuming the dotclock bandwidth of 1350p just to do 1080p, but you can do it at a lower refresh rate, such as 101Hz.

Unfortunately it doesn't work booo..

[Chief Blur Buster]

Unfortunately it doesn't work booo..

Can you specific about "doesn't work" in what way?
Do you get a black screen?
Do you still get ghosting?
There will be some bit of ghosting at top/bottom, but the ghosting will disappear from the middle of the screen.

[LogicElite]

Unfortunately it doesn't work booo..

Can you specific about "doesn't work" in what way?
Do you get a black screen?
Do you still get ghosting?
There will be some bit of ghosting at top/bottom, but the ghosting will disappear from the middle of the screen.

I created the custom resolution and set the vertical total pixel to 1350 and the hz at 101. No blackscreen but I still have the ghosting on the blur trail from the top to the bottom. The only difference is that the line goes slower since the refresh rate is at 101hz.

[Chief Blur Buster]

I created the custom resolution and set the vertical total pixel to 1350 and the hz at 101. No blackscreen but I still have the ghosting on the blur trail from the top to the bottom. The only difference is that the line goes slower since the refresh rate is at 101hz.

Actually, that's normal to always have ghosting.
The point is you want to push the worst ghosting off the edges of the screen as much as possible. With larger blanking intervals, there become thinner bands of worst ghosting at the very top/bottom edges.

When you view http://www.testufo.com/photo (with this custom 101Hz mode) with the photo scrolling across the middle of your screen, is the ghosting much better than during your default 120Hz mode?

[LogicElite]

I created the custom resolution and set the vertical total pixel to 1350 and the hz at 101. No blackscreen but I still have the ghosting on the blur trail from the top to the bottom. The only difference is that the line goes slower since the refresh rate is at 101hz.

Actually, that's normal to always have ghosting.
The point is you want to push the worst ghosting off the edges of the screen as much as possible. With larger blanking intervals, there become thinner bands of worst ghosting at the very top/bottom edges.

When you view http://www.testufo.com/photo (with this custom 101Hz mode) with the photo scrolling across the middle of your screen, is the ghosting much better than during your default 120Hz mode?

Chief, in fact, even with these parameters on the quebec image, I can see the a light red offset from red structure when motion blur is enabled. I tried to take a picture with my digital camera without success.

[GitDat]

I don't think that BENQ understands that probably 99% of people interested in this monitor and their 'Motion Blur Reduction' technology are tuned in to Blur Busters and this thread. I'm sure it has cost them a ton of sales and is damaging their reputation as a monitor manufacturer in general. They need to get this corrected firmware out of beta and make things right with their customers ASAP!

My recommendation for damage control, cross-ship new monitors to all customers who own a BENQ XL2720Z. Hopefully they'll save face and at least do SOMETHING soon. Customers should not have to find workarounds and deal with brokenness on a BRAND NEW PRODUCT due to their lack of Quality Control The Blur Chief even pointed out the problem and they're STILL cranking these faulty monitors out to people!

[Chief Blur Buster]

Chief, in fact, even with these parameters on the quebec image, I can see the a light red offset from red structure when motion blur is enabled. I tried to take a picture with my digital camera without success.

You need to pursuit the camera. Turn on the Pursuit Camera Grid, then take a picture while moving the camera sideways. A tracking camera more accurately simulates tracking eyes. It works best when you follow the pursuit camera instructions, but hand-pursuiting the camera has sometimes worked.

1. Turn on pursuit camera grid, example www.testufo.com/photo#pursuit=1
2. Set camera exposure to three or four refresh cycles long (1/30sec for 120Hz)
If you can't get an exact exposure, you can get close to this by playing around with exposure compensation & screen brightness
3. Pan the camera sideways while taking a picture (this simulates tracking eyes more accurately)
4. If the grid look bad, repeat step 3 until the grid looks reasonably good (less than 1 pixel offsets in alignment)
5. Post photo.

More complicated instructions are found in the pursuit camera instructions, for a better understanding of how this works.

Example hand-panned pursuit camera photo of www.testufo.com/photo


This is a photo of LightBoost/ULMB, camera panned by hand (rather than camera rail). Strobe crosstalk is very minor in this photo (see vertical edges).

[LogicElite]

Chief, in fact, even with these parameters on the quebec image, I can see the a light red offset from red structure when motion blur is enabled. I tried to take a picture with my digital camera without success.

You need to pursuit the camera. Turn on the Pursuit Camera Grid, then take a picture while moving the camera sideways. A tracking camera more accurately simulates tracking eyes. It works best when you follow the pursuit camera instructions, but hand-pursuiting the camera has sometimes worked.

1. Turn on pursuit camera grid, example http://www.testufo.com/photo#pursuit=1
2. Set camera exposure to three or four refresh cycles long (1/30sec for 120Hz)
If you can't get an exact exposure, you can get close to this by playing around with exposure compensation & screen brightness
3. Pan the camera sideways while taking a picture (this simulates tracking eyes more accurately)
4. If the grid look bad, repeat step 3 until the grid looks reasonably good (less than 1 pixel offsets in alignment)
5. Post photo.

More complicated instructions are found in the pursuit camera instructions, for a better understanding of how this works.

Example hand-panned pursuit camera photo of http://www.testufo.com/photo


This is a photo of LightBoost/ULMB, camera panned by hand (rather than camera rail). Strobe crosstalk is very minor in this photo (see vertical edges).

Ok is not perfect (taken from a Canon PowerShot SX210 IS) but you can notice the offset on the red structure.