BenQ XL2411Z Bad Ghosting?

[Falkentyne]

Hi
Yes those timings work
In fact the only thing to make 1024x768@144 work is to change the vertical total.
1100 and 1098 are close enough so the scaler identifies it as 144hz.
So the scaler is 'tricked' to accept 144hz at lower res. This is not official timing and should be considered an overclock.

What you did is a basic VT tweak.

I use this trick in other ways.

You know VT 1500 is our low blur reduction crosstalk tweak right?

Well you can use this VT to make the scaler accept out of range resolution, IF resolution can accept this VT legally. And refresh rate.

Example: 60hz will not accept VT 1500. "No signal detected". But 61hz acceps it!! strange right?

Now you know this res? 2560x1440 ????
This is out of monitor spec too. but...scaler can be tricked to accept it.
Because 1440p can use VT 1500!
Default VT for 1440p resolution is around VT 1510.
VT 1502 is close enough to be valid by official timings.

So.....

2560x1440
Front porch 48 pixels 3 lines
sync width 32 pixels 5 lines
Horizontal total 2720 (use 2656 or 2641 if out of range on DVI).
Vertical total 1500.
Refresh rate 100hz.

(MUST USE NVIDIA OR AMD pixel clock patch first).

Try it. It works.
Then check OSD.

Note: only VT 1497-1502 is accepted by scaler. This seems to be VT used for Lightboost mode internally, that's why. scaler reports 1280x1440 on factory service menu. Even at 2560x1440 scaler reports 1280x1440.
VT 1503 will black screen. Default VT will black screen. VT lower than 1497 will out of range.

You can also get 3200x1800@60hz to work.
This requires a Displayport connect. DVI will error.
How to make it work? Use VT from 3840x2160@30 hz !!!!
steal the VT, use it for 3200x1800, (VT 2220 I think). Big VT overclock.
Replace default VT for 3200x1800 (will black screen out of range) with 2200 ---->>> will work!!!
Blur reduction will not work. Backlight will turn off if you enable MBR..........

[urut]

Hoh, 2560x1440 rly works . But its to small and blured i think (maybe cuz 2560x1440 on 24' is to high). But what the hell is with this scaler? He's broken or what .

Lol, this is funny. Now i create 1920x1080 @ 144hz with this timings http://scr.hu/2ykh/s8lf4
GTF preset on nvidia control panel.

It works, osd shows 1920x1080 @ 120hz (DUNNO WHY) but testufo normally shows 144 fps 144hz. Thats weird

Can timings affect on input lag?

[Falkentyne]

SWEET MOTHER OF GOD.

Can you please do frameskip test here??

http://www.testufo.com/#test=photo&phot ... &height=-1

please turn on SINGLE STROBE in service menu and turn on blur reduction
check for UFO moving smooth or skipping frames. If image is blurry then strobes are in wrong sync.

set strobe duty to "006-010" in service menu.

Factory menu is:
XL2411Z only: hold button #3 and button #5 with the power off for 5 seconds, then press power while still holding them down.

Service menu is: For the XL2411Z (also the older XL2411T), it's button #2 (down button) for 5 seconds with power off, instead of button #4, then press power on+button #2

Hoh, 2560x1440 rly works . But its to small and blured i think (maybe cuz 2560x1440 on 24' is to high). But what the hell is with this scaler? He's broken or what .

it's firmware bugs. Benq admitted to me in email when I asked about XL2730Z.
Scaler uses vertical total to control backlight pulse width persistence (strobing) timing. If VT is "known" match with known refresh rate VT, it will use that persistence, OSD will report that as the refresh rate.
If VT is not known or not identified with preset refresh rate, persistence will be 0.167ms per point of strobe duty value (60hz pulse widths)=16.7ms per every full strobe cycle.

formula is hard to understand.

Persistence pulse width(strobe duty 001 value) = (1000 divided by "hz") divided by strobe phase range.
or PW= P / SP
PW=pulse width, P=refresh rate persistence, SP=strobe phase max range.
Normally persistence is variable determined by refresh rate and strobe phase=100.

Example: 60hz:
0.167 = 16.7 / 100.
SP=100, P=16.7. so persistence is 0.167ms

Example: 120hz (KNOWN):
0.083 = (1000 / 120) / 100
0.083= (8.3) / 120

So strobe duty persistence is 0.083ms.

But if you use VT tweak to unknown range (VT 1500) 120hz:
scaler will switch persistence to 60hz values. I don't know why. it just does. maybe its failsafe if it can't identify the VT.

Since persistence is know KNOWN: 60hz:
0.167ms = (1000 divided by 120) / SP.
0.167ms= (8.3) / SP
SP is unknown
0.167 * SP = 8.3 (solve for SP like algebra)
SP = 8.3 / 0.167
SP = 049
max strobe phase is 049 with VT tweak at 120hz.

So ...strobe phase 050=backlight will turn off.

And scaler will accept VT if it is in a known value.

VT 1497-VT 1502 seems to be "internal" VT. Used for Lightboost (3d vision 2).
Scaler will report 1280x1440
So make custom resolution in pixel clock range will always work

1920x1200, 1920x1440, 2560x1440, as long as pixel clock can fit in max DVI TDMS range (up to 450 MHz) or max displayport range (480 MHz) usually resolution will work.

But scaler will artifact at >460 MHz pixel clock.
2560x1440@115hz (454 MHz) will work (ONLY on displayport. DVI is too much for TDMS)
HT: 2641, VT: 1497.
2560x1440 @ 116hz-120hz will have artifact.

[urut]

Why are you so annoyed? With this "sweet mother of god"?

I do this test, with phase 100 and duty 006 (on 1920x1080 144hz GTF preset [osd shows 120hz])

At top and center image isn't blurry but i've got inverse ghosting, and in bottom of screen is a crosstalk.

What's the point to doin this test?

[Falkentyne]

Why are you so annoyed? With this "sweet mother of god"?

I do this test, with phase 100 and duty 006 (on 1920x1080 144hz GTF preset [osd shows 120hz])

At top and center image isn't blurry but i've got inverse ghosting, and in bottom of screen is a crosstalk.

What's the point to doin this test?

.......Who said I'm annoyed?
it means I'm surprised it worked.
"SWEET MOTHER OF GOD" is an American term for shock or surprise.

It's like saying "WOW I CANT BELIEVE WHAT I'M SEEING"
or "WHAT IS THIS I DONT EVEN..."

You did say English is not your first language, right?

Relax, please.

I'm surprised it worked because the pixel clock......451 mhz...
The whole point of "LCD Reduced" timings for 144hz is to lower the pixel clock.
Too bad firmware will not allow >145hz.
even your timing........146-150hz will black screen, right?

[urut]

Sorry then, my bad. Im not so good in english i missunderstood this Sorry again dude.

BUT WHAT A FACK? 150hz WORKING?

http://scr.hu/2ykh/eis9q

I DON'T KNOW IS A DRIVER BUG OR SOMETHING

BUT TESTUFO http://scr.hu/2ykh/6r5fr SHOW THIS WORKING WTF?!?!?!/


The highest i can create is 183hz, when i create 184 and higher i can't choose them.

http://scr.hu/2ykh/a3rxj


WTF IS ACTUALLY GOING ON?


http://scr.hu/2ykh/83jbt <--- screen of 183hz on testufo (highest i can got)

Please tell me its driver bug, wtf is goin on

[Falkentyne]

Sorry then, my bad. Im not so good in english i missunderstood this Sorry again dude.

BUT WHAT A FACK? 150hz WORKING?

http://scr.hu/2ykh/eis9q

I DON'T KNOW IS A DRIVER BUG OR SOMETHING

BUT TESTUFO http://scr.hu/2ykh/6r5fr SHOW THIS WORKING WTF?!?!?!/


The highest i can create is 183hz, when i create 184 and higher i can't choose them.

http://scr.hu/2ykh/a3rxj


WTF IS ACTUALLY GOING ON?


http://scr.hu/2ykh/83jbt <--- screen of 183hz on testufo (highest i can got)

Please tell me its driver bug, wtf is goin on

(!) Please PM chief blur buster!
I'm going to send a PM to toastyX also

GOOD JOB.
You used a firmware bug to avoid the refresh rate lock.

I'm going to try this.
Don't try blur reduction at those refresh rates, I don't think it will work properly.

[Falkentyne]

Can you tell me the exact values you are using?
I go "out of range" if I try. and your box is covering up some of the values.

I cant go higher than 145hz
I need:
Front porch (pixels/lines)
Sync width (pixels/lines)
HT/VT

(Also can you tell me the 183hz ones)?

Because I can't create your values. kHz and hz are both inaccurate and not the same as yours if I try to enter kHz and hz myself, I get different sync with...

[urut]

http://scr.hu/2ykh/gkpqj <--- 183hz ones

Tbh all of 144 + hz got the same timing. I dunno wtf

I dunno, testufo saids its 183hz (i put the screen before) but to be honest i didn't feel its a smoother

[Falkentyne]

Im going to switch to DVI port.
Displayport wont work.
Even your 144hz timing is "out of range" on mine.
I'll report back. None of your timings are working on mine (im using XL2720Z but scaler is identical, same timings should work).