"Komag" wrote:
(Interestingly, on this computer monitor, I found a setting for the HDMI input to act either as "Video" or "PC" - when I put it on "Video" it slightly zooms in the screen, cutting off the edges a little bit, creating overscan! Of course I set that junk back to "PC" where it will remain forever - where it was before.)
Yes, you got it - that's exactly what such settings do, switch overscan mode on/off.
Back on subject...
So in-game there is no overscan happening at all. Is it possible there is some overscan happening only on the Roku home page? Maybe now you want to spill the beans how you measured 290x218? 😄
I don't
want to - but fine, let me be laughing stock: i just measured the posters as well as the dimensions and calculated roughly the dimensions. No, there is no way i got anywhere near exact results... wait, this bizarre - i found in my desk pile the envelope i scribbled on and i actually had got numbers close to yours! With a friggin' tape measure!!
13.6cm/88.4cm*1920 = ~295
10.3cm/49.6cm*1080 = ~224
So anyway, i looked at these numbers and said to myself "well duh,
obviously that's 290x218 - there is no way they will deviate by only a few pixels, that is a no-no" - and so i rounded to the "right" values, proud that my jury-rigged methodology gave results so close (2-3%) to reality...
Maybe there is some crapification of side-loaded icon image files that doesn't happen the same way with private/public channels.
That's actually easy to test - why don't you? Create a private channel for your app, upload, "publish" and install, observe.
Maybe they get squished, prodded, translated to jpg, enlarged, pushed into a box and shrunk down again, and compressed to boot.
Bad JPEG compression would have had ringing, just like the other example.
Hmmm. Here is an insane theory... what if the home menu UI is actually rendered in 720p, even on 1080p screens? That means the poster first gets shrunk by ~1.5 (incl. some interpolation smearing) - and then blown up by ~1.5 (some extra smearing).