v0.96.8 (21 February)

[sub]

The onbord video doesn't support VMR9 but it does support VMR7. But when I start video playback (mpeg2) and "home" back to the menu, my video inset is stuck to the upper left corner:

Yes, this is a bug. I found and fixed it yesterday when I was looking at another VMR7 bug.

[A_Brass]

Yes, this is a bug. I found and fixed it yesterday when I was looking at another VMR7 bug.

Great, so I should look for it to be working in a Maint release?

Sounds good.

How's the wife? Any new baby yet?

[sub]

nah all i have to do to get the "bug" is start a video, switch back to the menu and then switch to fullscreen and its no full fullscreen.

i am using VMR9 (non custom render), this happens on all videos i think so no decoder issue.

To try to reproduce it, I've started GB-PVR in Window mode, using VMR9, and I've set:

<OverScanBorderX1>100</OverScanBorderX1>
<OverScanBorderY1>0</OverScanBorderY1>
<OverScanBorderX2>0</OverScanBorderX2>
<OverScanBorderY2>0</OverScanBorderY2>

This gives me a nice obvious black border on the left.

I go into the video library and start playing an existing MPEG2 file. Then press 'home' to switch to inset mode, then press 'alt-enter' to switch to fullscreen mode. Big black bar on the left.

Is that pretty much what you're doing?

[sub]

Great, so I should look for it to be working in a Maint release?

Yes, but only if some more serious bugs are raised.

How's the wife? Any new baby yet?

Everything is going well. We're still three of four weeks away. I wanted to have the release well out of the way.

[bhays]

Are there plans to update and release gbmvp.bin independent of complete gbpvr releases? I am dieing to use it full time, but it's crashing with the four square thing on my two mvp's. Does this seem to be related to the revision number of the mvp's?

[reven]

To try to reproduce it, I've started GB-PVR in Window mode, using VMR9, and I've set:

<OverScanBorderX1>100</OverScanBorderX1>
<OverScanBorderY1>0</OverScanBorderY1>
<OverScanBorderX2>0</OverScanBorderX2>
<OverScanBorderY2>0</OverScanBorderY2>

This gives me a nice obvious black border on the left.

I go into the video library and start playing an existing MPEG2 file. Then press 'home' to switch to inset mode, then press 'alt-enter' to switch to fullscreen mode. Big black bar on the left.

Is that pretty much what you're doing?

nah i mean, in fullscreen window mode.

1) start a video
2) push the home key, so inset is shown
3) push home key again so video is in fullscreen (i meant that fullscreen)

and then the video has the border around it.

[sub]

Are there plans to update and release gbmvp.bin independent of complete gbpvr releases?

Maybe. Its depends if the changes I end up making also depend on changes in the other GB-PVR code.

I am dieing to use it full time, but it's crashing with the four square thing on my two mvp's. Does this seem to be related to the revision number of the mvp's?

The four squares are sort of a connection status. First one indicates the server discovery broadcast has been sent. Second one indicates the control socket has connected. Third one indicates the media socket has been connected. Fourth indicates the communication established.

Do you see the user interface come up before crashing back to this four squares? The better information you can give me on when it crashes, the more likely I can come up with a fix.

[bungle]

Out of technical curiousity, what exactly is gbmvp.bin? Did you write a new firmware from scratch? I know when I was playing with mvp media center the mvp ran a little BusyBox Linux. Does the .bin always run on top of that? Pretty impressive feat, I should think.

[sub]

nah i mean, in fullscreen window mode.

1) start a video
2) push the home key, so inset is shown
3) push home key again so video is in fullscreen (i meant that fullscreen)

and then the video has the border around it.

Ok, this is fixed for the next build.

[sub]

Yes, it is a dongle I've written on busybox linux. It is virtually from scratch, but does reuse libav from the mvpmc project, which is covered by LGPL. I'll be adding some license notes about it in the 'third party' directory for the next build.