Recent content by jka

Unfortunately the new thingy produces the exact same issues as the one before it. I already mentioned several time here, for example at => https://hardforum.com/threads/24-widescreen-crt-fw900-from-ebay-arrived-comments.952788/page-459#post-1045055441 If you are curious, I am attaching the...

I think it does not matter when the USB port is powered and stable enough. But I had my fair share of physically busted USB ports that would disconnect all the time => probably not something you want happening when writing to the monitor memory, but I think the memory should have some safety...

Thank you, close up photos front and back would be much appreciated, especially when without markings. Any chance you still remember if you hooked up the 5V connection or not?

I was browsing some analog photography and I spotted this sort of a recurring effect on grass or trees or concrete etc. It looks very eye-pleasing: https://i.redd.it/nkg8pa6ssuu61.jpg https://i.redd.it/tldkoflhkqg51.jpg https://i.redd.it/0vpnoqpx9zd61.jpg https://i.redd.it/y09tozx0gfv51.jpg...

Thanks for the quick reply. It took me a while to sift through the thread but I found who it was now ... Definitely recommend doing WPB every 6 months at least. Paging doctor jbltecnicspro ... Could you please kindly let me know the exact model of the USB thingy you had for F520 and which...

Enhanced Interrogator Sorry, I can't remember now, was it perhaps you who has F520 and can perform WPB without any issues like errors or washed out colors after WPB? If yes, could you please kindly let me know the exact model of the USB thingy you have and which connections do you connect? (I...

Also known as IMAGE RESTORATION on Trinitrons. If you perform it on Trinitrons, you can go undo it by loading the previous DAT file to memory. But on Diamondtrons you would need to change the settings back manually. And it won't tell you which settings it changed. So you need to have them all...

Have you tried to have all this at the same time BEFORE turning it ON: - lower contrast and brightness in OSD to zero - use white color background then turning it ON and also open the OSD menu as soon possible (even though you can't see it because it's still all black during the initial boot...

It could have something to do with aging capacitors or something like that. It looks as if some voltage needs to stabilize there first then it works just fine. It's only during cold startup after hours (=overnight) of being turned off. Yeah, it's all bonkers. Not just the blacks. It's all a bit...

The "without LUT" picture is also "before WPB", should have made it more clear. If I do WPB then black is like dark gray, everything is washed away and little blurry. Not sure about the whitepoint precision there, didn't even look. Black level seems the same, true black. Gamma curve is flat on...

without LUT: with LUT (2.2G): notes: this is on default DAT, with lowered OSD brightness (from 50 to 38) to reach true black. But it is not in prime mode, it is in 2336x1314@99Hz (don't ask lol). I am sure it could be better if the WPB procedure would work on this one but so far I was...

No idea about that, I just wanted to combine the game and calibration LUTs together (because you can only have 1 of them active), using some extrapolation/approximation. If you look at the below snippets from actual LUT data, it should be a simple task: DEFAULT ... 250 64000 64000...

Thanks, I will give it a go soon and post the results. But now that I have a nice LUT I keep running into conflicts with games using their own LUTs, I am thinking of making a simple tool to combine in-game LUT with my LUT. Not sure if it will produce nice results at all, but I am somewhat...

Correct, picture is washed out, black is gray and guns seem to be in overdrive so everything is a bit blurry. Whitepoint is far from correct (even though I hit the chromacity targets perfectly during WPB). Just a small bug, worked around by loading the dat file in twice and finalizing it twice...

It is as if the WPB formulations behind the scene are wrong, something like some important variable value being incorrect and I have no control over it with the exposed variables in the procedure. I have tried faking higher/lower G2, higher/lower luminance target in that 6.5 nits step, and more...