Aspect Formula

[jtokach]

Hi, I'm frustrated. Taking deep breaths...

I never understood the trial and error system of trying to figure out the x,y values for positioning and offsets. They make no sense and never did even on the MVP. This was also evident using the MVP Position plugin.

Why is it that when you change the X or Y (seemingly beyond some unknown point) the offsets go berzerk? All of the time spent dialing in the offsets is then shot and you need to start over. Repeat indefintely. This time I can't seem to get it right. When the menuing appears proper and I launch a video, the video is way out of whack.

Please, sub/martin, what's the formula?

Jim

[mvallevand]

Well I already told you what I recommend here, http://forums.nextpvr.com/showthread.php...post403609

Blame GBPVR/NPVR users for this nightmare accepting that the default looks like crap. For some reason you want to get every pixel out of your monitors. Proper screen design is to include overscan in the design and not worry about the edges.

Also if you are trying to get a good 4:3 look on PAL with Default, you might as well forget it.

I don't understand the comment about video, that will show based on your configured choice, and it can't be adjusted out of whack.

Martin

[sub]

Why is it that when you change the X or Y (seemingly beyond some unknown point) the offsets go berzerk? All of the time spent dialing in the offsets is then shot and you need to start over. Repeat indefintely. This time I can't seem to get it right. When the menuing appears proper and I launch a video, the video is way out of whack.

The offset x/y and width/height settings make no difference video playback on the MVP/NMT. All it changes is where the menus are shown on the screen.

If you set the offsets to 0,0 and width and height to the size of the screen, then the NPVR screens fill the entire frame buffer sent to the MVP/NMT. If you're instead set the offsets to 40,40 and the width and height to 80 pixels less than the size of the screen, then the screens NPVR sends to the MVP/NMT will have black border of 40 pixels on each side, with the actual interesting bits of the screen using the slightly smaller space in the middle. None of this makes any difference to where the video is shown on the screen - it's only about the menus.

[jtokach]

I figured out the video, the damn zoom on the PCH was set wrong... doh.

Yes, I'm using the divisible by 4. But I just don't understand why I can't simply set the OSD to 1280 x 720 with 0x0 offset, to match my resolution? Well, that's not the crux of the matter. When changes are made, as described above, there really seems to be no method to the madness in setting the resolution and offset.

All things considered though, this is miles ahead of the GBPVR NMT implementation. I'm just in whiner mode from the recent upgrade. =)

[jtokach]

The offset x/y and width/height settings make no difference video playback on the MVP/NMT. All it changes is where the menus are shown on the screen.

If you set the offsets to 0,0 and width and height to the size of the screen, then the NPVR screens fill the entire frame buffer sent to the MVP/NMT. If you're instead set the offsets to 40,40 and the width and height to 80 pixels less than the size of the screen, then the screens NPVR sends to the MVP/NMT will have black border of 40 pixels on each side, with the actual interesting bits of the screen using the slightly smaller space in the middle. None of this makes any difference to where the video is shown on the screen - it's only about the menus.

Didn't catch your post in time before I posted. But if I understand, I should be setting it to 1280x720 and then substracting the offsets from there, right?

[mvallevand]

Yes that is the forumula

1280 = width + (2 * offset) can also be

width = 1280 - (2*offset)

Martin

[jtokach]

Martin, that formula didn't work. What did work for me was width= hRes - (1*offset). From there I calculated the vertical value based on the resolution ratio. NPVR does NOT like negative offsets. Here's a vbscript to do the calculation that worked for me:

Code:

' Save as res.vbs
' Modify your resolution and offsets
' From the command line, cscript.exe res.vbs

Option Explicit
Dim hResolution, vResolution
Dim hOffset, vOffset
Dim width, height

' Set your TV resolution
hResolution = 1280
vResolution = 720

' Set your offsets
hOffset = 64
vOffset = 0

If hOffset mod 4 <> 0 Then wscript.echo "hOffset is not divisable by 4"
If vOffset mod 4 <> 0 Then wscript.echo "vOffset is not divisable by 4"

width = hResolution - hOffset

'new height = (original height / original width) * new width
height = (vResolution / hResolution) * width

wscript.echo "width (x)  = " & width
wscript.echo "offset (x) = " & hOffset

height = height - vOffset
wscript.echo "height (y) = " & height
wscript.echo "offset (y) = " & vOffset

'wscript.echo "new res    = " & width & "x" & height

[jtokach]

I feel like I found my "sleep number". ;-)

[mvallevand]

Unless sub is using the ratio that you use somehow, that script doesn't make sense, since its wrapping the frame buffer after the first line giving an effective offset of 32 but I'm glad you found a solution that works. I'm surprised that this doesn't cut off the clock with a y offset of 0.

I suspect you would do just as well by using 1216,680, 32, 20

Martin