ui size

[Hairy]

I'd be really quite interested in investigating this further as well.

Attached is a dev grid I'm using with the new CS. It's a 1440x1080, 4:3, square pixel, 100% grid. It's a background.jpg, so you can use in the mainmenu folder.

The current layout of the CS we're working on, can (just about) accommodate the 10% vertical overscan, but the 14% horizontal is a little over twice the current allowance.

[pBS]

got it setup as background, would you like a count of lines for visible area?
doesn't even seem to be centered on mine..
[maybe the offset i'm using]

i'll reset to 'normal' config settings and retry and post what i count..
[tho i wish it was numbered ]

[Hairy]

Yeah sorry about that. On my LCD it's handy enough to see the darker lines every 10%. It's designed for putting together skins (that's why, each the background and the grid are the colours they are).

I've tweaked it so it should be much more useful (preview attached). Please give it another go.

[Hairy]

Sorry if these are silly questions but:

NMT is a popcorn hour (one device right?)
Can you select different output resolutions?

on my panasonic 42pz85 plasma it also doesn't fit correctly for example the date and time in the top of the screen. Yesterday i got gbpvr working on my friends popcorn and his sony lcd and on this device it also doesn't fit correctly.

The popcorn gui fit's correctly on both our screens (1080p, 1920,1080)

Does anyone know if the NMT is applying the overscan only if a lower resolution output (than 1080) is selected?

Cheers

[mvallevand]

Hairy, The NMT is a generic name for the Networked Media Tank firmware that runs on machines by over 10 manufactures now. PCH (Popcorn Hour) is a brand and a subsidiary of the company Syabas that makes the NMT. I have two different model of PCH just to confuse things. From a design perspective I write for the NMT but only test on the PCH.

Resolution is tricky. mvpmcx2 supports NTSC, PAL, 480p, 576p, 720p, 1080i and 1080p connections, (the NMT supports many more), but the screen OSD surface resolution is actually custom. For SD I default to 640x576 and for HD I selected 1280x720. You could however output 1920x1080 on top of an NTSC monitor if you wanted but it remains NTSC resolution.

I have uploaded a PCH jpeg photo showing the typical problem area on the Blue skin with your background (my config.xml settings are 1280,720,0,0). Most of the TV Guide text and the left margin are well into the 5% area by default. I have a little overscan but I don't worry about it. The whole screen is here http://mvallevand.googlepages.com/IMG_0089.JPG

Martin

[Hairy]

Cheers mvallevand,

Being new to all this stuff it can be a complicated beast. With the latest version of CS-SD we're working on. I resized all my graphics to a square 4:3 resolution (720x540) so what I saw in photoshop should be what users see when output devices do their resizing ( I hope :o). The ovescan bit is just something you can't test for. I positioned the layout with a slight emphasis on the horizontal (to try and create the illusion of width on a 4:3 display), and left a 3% horizontal and a 5% vertical overscan border (on the important bits).

I'm interested in the range of overscan people are getting, to see if those numbers need to be more generous (and to see if that works aesthetically), and also for the HD version we hope to get done. I was working off the assumption that devices barely overscanned HD res stuff (as it appears from your screen shot - looks like roughly a 2% overscan border). Also the res of the graphics for that HD version, I was leaning towards full 1080, but perhaps 720 might be a better compomise.

I just thought I'd pounce on the chance to find out a little more

[Fatman_do]

These screen shots are great. Helps put things in perspective. It would appear 5% in your case is more than adequate. I looks like there is little horizontal overscan, more so vertically. At least based on what I am seeing. I'll load up your test screen Hairy on my 4:3 crt and see how things look.

[Fatman_do]

Bah! Nevermind me. I forgot I have my graphics card set to tune out overscan. I forgot this untill I saw the entire test pattern.

[mvallevand]

Hairy, don't use my screen shot overscan as typical HD, it was made on a $150 (US) tv/monitor that I use for development, I'm sure that for 10x that many people get better panels.

Martin.

[tcmy95]

Here are my settings for the NMT, as you can see the y offset doesn't add upto 720 but with my TV it is ok if you go down in increments of 4. My yn offset totals 712 but it is not a problem and looks great. It might be worth a try?

<MVPWidth>1240</MVPWidth>
<MVPHeight>704</MVPHeight>
<MVPOffsetX>20</MVPOffsetX>
<MVPOffsetY>8</MVPOffsetY>