Strobe Utility crashing as soon as I open it

[Falkentyne]

Whitestar, what I meant was this.
When you have blur reduction already on,
Set AMA to high even though its already on high.
It will change the ghosting shift.
It's a hidden AMA Setting, basically. It's undocumented.

It was on V2 firmware too but it was useless on V2...it just INTENSIFIED GREATLY the inverse ghosting to extreme levels.
This was changed for the better on V4 and made very useful.

In some games, you can drastically improve the ghosting performance by using the hidden AMA setting along with a lower contrast (contrast 0=better than lightboost quality (on the 27"; might be the same or slightly worse on the 24"), but very washed out, 20=equal amount of normal ghosting as 'regular' blur reduction without the hidden AMA high, but at contrast 43).

Do you understand what I mean?
There are HIDDEN AMA settings.

If you toggle AMA or reactivate the high setting AFTER blur reduction is on (you have to actually select it again), it gives a different overdrive with shifted OD parameters (more to the left (eliminating more inverse ghosting while intensifying normal ghosting, which can be removed by lowering contrast).

Lowering contrast to 20 or 0 WITHOUT the new AMA setting just causes a very ugly 'white glowing translucent' ghosting pattern which looks really bad.

----------------------
And yes, about your persistence /duty results, that's how it works.
When you raise the strobe duty (increase brightness/raise persistence), it LOWERS THE position of the strobe crosstalk at the top, causing it to move lower. Similar to strobe phase, but not as extreme.

[whitestar]

I understand, but there is no change to the ghosting when I follow your AMA procedure.

Anyway, here is the firmware file. I followed your instructions in detail. It was a bit of a hassle, because I had to boot from my desktop computer. I took a picture at the end. This is what it looked like: http://i161.photobucket.com/albums/t216 ... FWdump.jpg. As you can see it found my monitor on bus 0. Does it look correct?

Here is the file: http://www.mediafire.com/download/m707c ... backup.bin

Good luck. Hope you get it to work.
If you can confirm it works, then I will open a new thread with the info. It may be a bit difficult to find the file in this thread.

[Falkentyne]

Wow awesome work
Checked out the dump, looks spot on.
2mb, and the end FF byted correctly.

Were my instructions clear about the dumping, or were there any other issues?

Interesting that the hidden AMA change didn't affect the ghosting.
There's also a hidden AMA under premium. On my 2720Z, changing AMA premium to "BBR+AMA premium (the default is BBR+Premium, when AMA is set to premium BEFORE enabling blur reduction), seems to make the ghosting at FW version 2 level (default premium is worse).

Might be a difference in the panels. the 24" panels already have less ghosting than the 27" versions, so maybe the calibration was already enough. We'll need masterotaku to do some testing.

Great work and thank you!

[whitestar]

Your instructions were spot on. Just one thing; I don't think the two i2cdetect commands are necessary, as those only seem to bring up a list of i2c buses. So those two commands can probably be left out. The i2cdump command was the one that allowed me to find the monitor.

And just a small note regarding the connection: I had my monitor connected to the DVI-D (port 2) on my GTX 670. But when connected like that Ubuntu could not find the monitor. I had to hook it up to the DVI-I port (port 1) and then Ubuntu found it.

[whitestar]

Btw, and slightly off-topic: I can't seem to use the VT1500 or VT1350 trick when at 60hz. With VT1500 I get Out of range and have to wait while it counts down to 0, and with VT1350 I just get a black screen and also have to apparently wait until it counts down to 0.

Any idea?

[Falkentyne]

Check masterotaku's thread on "my findings so far...." for the max VT for certain refresh rates. He also has decent 60 hz timings.
Vt 1500 won't work at 60 hz, and you don't need such a high VT at a low refresh rate. I think VT 1350 is too high also. Pretty sure the highest VT is 1260 unless you use his 60 hz timings.

Also make sure the strobe phase is set to 000. Flashing the firmware resets phase to 100. At 100 hz refresh rate, and VT 1500, you get a black screen if phase is higher than 059 with VT tweak. At 120hz, its 050. Strobe phase only works at 100 without VT tweaks.

[error-id10t]

Thanks very much for the dump, worked fine here now running V4.

[whitestar]

Check masterotaku's thread on "my findings so far...." for the max VT for certain refresh rates. He also has decent 60 hz timings.
Vt 1500 won't work at 60 hz, and you don't need such a high VT at a low refresh rate. I think VT 1350 is too high also. Pretty sure the highest VT is 1260 unless you use his 60 hz timings.

Also make sure the strobe phase is set to 000. Flashing the firmware resets phase to 100. At 100 hz refresh rate, and VT 1500, you get a black screen if phase is higher than 059 with VT tweak. At 120hz, its 050. Strobe phase only works at 100 without VT tweaks.

Yeah, IIRC I ended up using 1270 and that worked fine. 1275 was the max value, but then everything got really blurry, so the max usable value seems to be 1270.

Thanks very much for the dump, worked fine here now running V4.

You're welcome. Do you notice any changes, or is it just the same as V2?

[error-id10t]

I don't have a dGPU at the moment so I'm stuck at 60Hz and Blur Reduction is unusable for me at those rates.. I can't use it lower than 80-85hz. I just wanted to see if there was a difference between V3 and V4 at that level but it's the same.

It's more for future once I get another GPU it's all up to date, I don't see myself jumping to freesync/g-sync at the moment, this monitor does the job still just fine.

[Falkentyne]

Whitestar,
Just to make sure, your image looks better now than this one, right? (center of test image, not top or bottom; assuming strobe phase =000 and strobe duty 006 with a VT, and 100/120 hz preferred (60hz looks much worse IMO).



This was V2 firmware on a XL2411Z (AMA high).
(and on 2720Z also).
Now on V4, this is what ama premium looks like, and AMA high looks more pleasant.

Masterotaku will find out if there are hidden AMA settings. They exist on the 2720Z.
Hidden AMA high shifts the ghosting balance greatly from light inverse to aggressive normal (which can be mitigated by lowering contrast, so you get a no inverse and extremely low to normal light ghosting at 0-20 contrast).
Hidden AMA premium very -slightly- shifts the aggressive inverse ghosting to be slightly less aggressive. (it now looks like the default AMA high did on V2 firmware). Regular AMA premium on v4 is NOWHERE NEAR as butt ugly as regular AMA premium on V2 (which was atrocious). Premium is actually usable now on V4.