Main > Main Forum
Phoenix 26" Monitor
ckas:
Hi DJO_Maverick - hailing from Australia here!
First of all - thank you so much for your super in depth review of this display. Wow - such a huge help for anyone considering it! Thank you!
I have been looking at this monitor also and am thinking about putting it into a 26" cab since CRT stopped working.
Any chance you can tell us the actual "exact" display pixel area in mm (width x height)? Can't seem to find this info anywhere on the resellers websites! Would be good to know how it will fit with existing bezel.
Also - I don't suppose you ever confirmed the actual panel resolution in the end - sounds like there is a mismatch between driver params and screen params as others have mentioned.
A really good sharp photo with a good camera of the display with a measuring tape over it will likely tell us the actual resolution of the display if we can count how many pixels are showing per say 10 or 20mm of tape. It will certainly tell us something about the rough resolution and then we can infer it is a likely resolution close to that once we know the exact pixel area sizes from earlier (if you can be bothered setting up the close up photo!!).
My plan was to make a really authentic looking experience using HLSL settings, including barrelling and other distortions to try to replicate my old CRT. From all your reporting it sounds like any high resolution effects will just be washed away with the poor scaling and resolution matching between the driver and the display and simply turn into a moire-fest!?
Thanks for taking the time!
DJO_Maverick:
I don't know if I'd call it super in depth, but no problem.
Still no official answer on the resolution today, but yeah, there's definitely a mismatch between the screen and controller firmware it seems.
--- Quote from: ckas on July 31, 2023, 10:24:02 am ---Any chance you can tell us the actual "exact" display pixel area in mm (width x height)? Can't seem to find this info anywhere on the resellers websites! Would be good to know how it will fit with existing bezel.
...
A really good sharp photo with a good camera of the display with a measuring tape over it will likely tell us the actual resolution of the display if we can count how many pixels are showing per say 10 or 20mm of tape. It will certainly tell us something about the rough resolution and then we can infer it is a likely resolution close to that once we know the exact pixel area sizes from earlier (if you can be bothered setting up the close up photo!!).
--- End quote ---
I'll try to do that tomorrow evening. Not sure if my cell camera is adequate for pixel counting, we'll see. I'd attempted to do that once before with a ruler and that's what led me to the 1024x768 estimate, but I'm doubting that more now. 1600x1200 is clearly resolving more detail to the shadow mask sim, even with the scaling errors.
--- Quote from: ckas on July 31, 2023, 10:24:02 am ---My plan was to make a really authentic looking experience using HLSL settings, including barrelling and other distortions to try to replicate my old CRT. From all your reporting it sounds like any high resolution effects will just be washed away with the poor scaling and resolution matching between the driver and the display and simply turn into a moire-fest!?
--- End quote ---
Same here, that's why the uncontrollable scaling has been a real problem; it does, in fact, turn HLSL into a moire-fest. At least they're aware of the scaling issue and claim to be working on an update.
DJO_Maverick:
--- Quote from: ckas on July 31, 2023, 10:24:02 am ---Any chance you can tell us the actual "exact" display pixel area in mm (width x height)? Can't seem to find this info anywhere on the resellers websites! Would be good to know how it will fit with existing bezel.
...
A really good sharp photo with a good camera of the display with a measuring tape over it will likely tell us the actual resolution of the display if we can count how many pixels are showing per say 10 or 20mm of tape. It will certainly tell us something about the rough resolution and then we can infer it is a likely resolution close to that once we know the exact pixel area sizes from earlier (if you can be bothered setting up the close up photo!!).
--- End quote ---
You'll have to settle for Imperial units or convert, only ruler I've got handy. ;)
Visible area is 20 3/4in x 15 9/16in. About 25 3/4in on the diagonal.
This is the best I can do for pixel close-ups today.
ckas:
Awesome!
Ok - I count roughly 54-55 pixels per inch. This results in 20.75 x 54 = 1120 pixels and 15.5625 x 54 = 840 pixels. This would make the monitor 1120x840 (which is an unusual but not completely implausible resolution - there are monitors with this!). Perhaps a more likely (due to measurement error) is XGA+ 1152x864 pixels (a standard but very uncommon resolution). Perhaps try to send some resolutions inside this range in ratio 4:3 to see if any render without scaling?
Feels like we are getting close - thanks again for all your hard work!
DJO_Maverick:
Tried that suite of resolutions again, no luck. Still stretching. I also count more like ~50 per inch. That would basically be spot on to 1024x768.
Went back and stared at that some more... I'm convinced now, more than ever, that it really is 1024x768. I think it was tricking my eyes at 1600x1200 by doing some pretty good subpixel rendering. Anything with 768 vertical has perfectly even lines. I also forgot to turn off autostretch in my prior testing... with it off, x768 generates perfectly even scanlines at integer scale. Nothing else has.
Interestingly, however, that still generates some slight uneven stretching on the x axis. Not really noticeable outside of a test pattern/ArcadeOSD, but it's there. That may come from the apparent mismatch between the controller firmware (what it thinks the AR/res are) and the actual panel resolution.
I think it's time for me to come to peace with the fact that it is, almost certainly, merely a 1024x768 panel (or it certainly only has 768 vertical lines and some oddball X resolution). That keeps lines even for HLSL, even though it (of course) means a lot less resolution than desired to do a really good simulation. I may fiddle with creating some x768 super resolutions for it next to see how that looks, since the sub-pixel rendering seems good.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version