Problems with 1080i

[wtg]

I'm trying to get my PCH and gbpvr running in 1080i mode but not without much success.

I have the following line in startmeup:
/etc/mvpmc/mvpmcx2 -m 1080 &

And this in config.xml:

Code:

<MAC-0006DC421F7B>
      <MVPClientType>PCH</MVPClientType>
      <MVPWidth>1920</MVPWidth>
      <MVPHeight>1080</MVPHeight>
      <MVPOffsetX>0</MVPOffsetX>
      <MVPOffsetY>0</MVPOffsetY>
      <MVPSendIncrementalUpdates>true</MVPSendIncrementalUpdates>
      <MVPTranscodeTS>false</MVPTranscodeTS>
      <MVPTranscodeAVI>false</MVPTranscodeAVI>
      <MVPTranscodeWMV>false</MVPTranscodeWMV>
      <MVPTranscodeMKV>false</MVPTranscodeMKV>
    </MAC-0006DC421F7B>

However, when I start gbpvr it seems to display only about a 1/3 of the screen perhaps. My TV tells me its running in 1920x540 resolution but that doesn't seem accurate related to the width because the visible menu is displaying in the right 1/3rd of the screen like it's zoomed in to the upper left. When I select the Guide, I see the first 5 channels and about 1/2 of the sixth, and only the first hour of programming, slightly more.

I'm unable to playback a recording also, it tries but doesn't quite make it, crashing out of gbpvr and back to the NMT menu.

I run at 1080i and playback within the NMT software fine.

Thoughts?

[sub]

Can you post your logs after the PCH starts up so I can see if its correctly identifying as a PCH?

[mvallevand]

The default for -m 1080 is still a 1280x720 resolution. If you must use the much higher and slower resolution which really won't have that much of an implact on OSD quality you need to add --display 1920x1080.

Note that this setting has no impact on the video playing quality.

Martin

[wtg]

Can you post your logs after the PCH starts up so I can see if its correctly identifying as a PCH?

Thanks sub... attached. The time of interest is around 5:45pm.

[sub]

All ok there. Its definitely identifying as a PCH.

I'd have to go with Martin's suggestion about trying the UI at 1280x720 though. It performs much better at this resolution, and looks pretty much identical to 1920x1080. The video can still run at 1080 though.

[wtg]

The default for -m 1080 is still a 1280x720 resolution. If you must use the much higher and slower resolution which really won't have that much of an implact on OSD quality you need to add --display 1920x1080.

Note that this setting has no impact on the video playing quality.

Martin

Ok, I made the change and it's a big improvement. The main screen looks fine, though the Guide and other screens are definitely a bit truncated, almost like it's zoomed in a bit. For instance on the Recordings screen, only the bottom half of the word "Recordings" in the upper left of the screen is visible.

I'll fall back to 720 and see how that works. Like you've suggested, it's not like there's a difference in how it'll look, I just wanted to try it out at 1080, and it certainly should work.

Thanks for the help,
Tim

[sub]

Ok, I made the change and it's a big improvement. The main screen looks fine, though the Guide and other screens are definitely a bit truncated, almost like it's zoomed in a bit. For instance on the Recordings screen, only the bottom half of the word "Recordings" in the upper left of the screen is visible.

Its actually farily common for a bit too much overscan. You can try tweaking the <MVPWidth> <MVPOffsetX> etc to make sure the picture fits on your screen.

[wtg]

Thanks for all the help.

I ran into one problem with going back to 720 mode that hopefully others can avoid. Since you guys mentioned there was no advantage to using 1080i for the gbpvr menus, I figured I'd set things back. I set the size and width appropriately in config.xml, and then I changed the startmeup to go into 720 mode. Mistake.

Turns out the only way I can get into gbpvr is if I use the -m 1080 line in startmeup, perhaps because I have the PCH in 1080i mode natively. In any event, with -m 720 the PCH just locked up hard - black screen. I had to power-off to reset it, and there was no clue in the MVP logs. After many frustrating resets it finally occurred to me what the problem might be and re-enabling 1080 fixed it.

Thanks again for all the help.
Tim