ui size

[pBS]

having problems resizing ui.. getting very odd results with the config.xml adjustments..
confused as to which settings do what exactly..

i have a 1080i *only* 4:3 component tv [ok it does 480i/p too, but that's it,no 720 anything]

i'm using -m 1080i and everything's overscanned about 10% [too much]
can't even see the "TV Guide" title on guide screen...

adding -display 1920x1080 i get better results, but still overscanned...
currently i have what looks like a square pixel image [sides cut off on 4:3 tv! basically 1:1 aspect] but i can finally see whole ui using:

<MVPWidth>1320</MVPWidth>
<MVPHeight>900</MVPHeight>
<MVPOffsetX>0</MVPOffsetX>
<MVPOffsetY>0</MVPOffsetY>

whenever i set display to use 720 i get blank screen...

resizing in config.xml i get weird results, as if something's auto-resizing to fit screen...[plus delays as if that's what's happening]

do the aspect ratio settings in gbpvr do anything to pch ui aspect?
[main system uses 16:9 monitor, pch is on 4:3]

[mvallevand]

I can't answer your questions but I can tell you

- mvpmcx2 needs to have the same total dimensions as you have in config.xml or you will corrupt the frame buffer and get unexpected result.

- I wouldn't recommend going beyond 1280x720 instead try increasing the offset and decreasing the width.

- I don't think the problem is really with the aspect ratio. The skins themselves not always being overscan friendly. Consider modifying the skin and not config.xml

- Consider the Syabas guidelines for HD design are as follows

1. Only 1100 x 656 pixel area out of 1280 x 720 pixel width will be
shown. Design however should be done for the entire 1280 x 720
pixel area to complement the Plasma screen.
2. The left and right portion of the 1280 width will be cropped by TV.
3. The width of 1100 is visible area, the others will be in overscan area
and majority will be cropped.
4. The height of 656 is visible area, the differences will be in overscan
area.

Martin

[pBS]

thanx, that clears up a lot...i think i may be able to get it wider now...

trying to stay away from skin modification if possible so i can use community skin..

- I wouldn't recommend going beyond 1280x720 instead try increasing the offset and decreasing the width.

i think i'll see what i can do going this route...
thanx again, can be really hard finding some of this info...

[Fatman_do]

These overscan values are something we might be able to accommodate. If I did my math right it is W=86% and H=91%. Those number do take up alot of the width. 7% per side, 5% up/down. May not make it into the next release, but if you pester me, we might get something wrangled for PCH use.

[mvallevand]

Fatman_do, that could be very beneficial, but it probably needs to be researched. I don't think those Syabas recommendation's are PCH specific, I think those are based on being able to work on the largest range of TV monitors, even if many panels now have near zero overscan. I'm not a skin designer at all, and I am not sure if the needs of the many outweigh the needs of the few.

Of course it does mean I have to have a deeper look at the Community Skin!

Martin

[Fatman_do]

It shouldn't be much of an issue.

Many of the positions of the CommunitySkin are controlled from the baseskin.xml file. It could be a 5 minute change. Locations in PVRX2.exe are controlled by % values, so this makes it easier to affect change. I can create a background image with an overscan zone that maybe PBS and I can "Dial in" that will get us in the neighborhood before going into everything.

[pBS]

yea, i figured just a separate main template with overscan might also be beneficial for mvp users...
i was just gonna make a skin template myself adjusted for this freaky situation..

but before you do that, i almost got it working right with some freaky values, as either the pch or my tv are doing some scaling, i just have to figure out why/when it does it...
[seems like it jumps to next res. after i pass a certain point in dimensions]

anyways for now, i have a fully visible screen, it's just got small bars on sides, so i can live with that if need be.. looks totally square[1:1] on my 4:3 tv....

is there any way i can tell what actual resolution the ui is displayed in with telnet?
i think the output mode is getting changed by pch depending on size...

even -edtv is overscanned or i'd use that..
would the mvp positon plugin work with that setting?

[Wingleader]

Will have a look at this to, because 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)

[pBS]

the background image would be good tho, just to see how far it actually is off..
cuz it sure seems like around 20% overscan,about twice the standard ntsc 'tv-safe' zone...

[mvallevand]

What about viewing a jpg full screen in the picture viewer? There are test pattern jpg's around that might help.

Martin