MVP restarting while watching video

[psycik]

Been experiencing a fairly annoying problem since I put down a heap of windows update fixes - at the point where I'm going to drop back to an image from before I put them down.

While watching a video (live tv or recording) the mvp will just reset. Thought it may have been related to comskip commercials, but after deleting the .txt file for the commercial marks and not touching the remote it still did it.

Seems to be network related

Code:

2007-09-13 01:07:54.515    VERBOSE    [6]    getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
2007-09-13 01:07:54.515    VERBOSE    [6]    MVP request processed
2007-09-13 01:07:54.515    VERBOSE    [6]    MVP waiting for data
2007-09-13 01:07:59.546    VERBOSE    [6]    MVP data read: 1   (8)
2007-09-13 01:07:59.546    VERBOSE    [6]    Responding to ping
2007-09-13 01:07:59.546    VERBOSE    [6]    getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
2007-09-13 01:07:59.546    VERBOSE    [6]    MVP request processed
2007-09-13 01:07:59.546    VERBOSE    [6]    MVP waiting for data
2007-09-13 01:07:59.953    VERBOSE    [6]    Unrequested needsRendering()...
2007-09-13 01:08:00.000    VERBOSE    [6]    Y/Y2 buffer: 5466 bytes
2007-09-13 01:08:00.031    VERBOSE    [6]    U/V buffer: 1035 bytes   (sent:5466)
2007-09-13 01:08:00.031    VERBOSE    [6]    U/V buffer: 1035 bytes@2
2007-09-13 01:08:00.031    VERBOSE    [6]    U/V buffer: 1035 bytes@3   (sent:1035)
2007-09-13 01:08:00.031    VERBOSE    [6]    incremental frame sent
2007-09-13 01:08:00.156    VERBOSE    [6]    MVP data read: 1   (3)
2007-09-13 01:08:00.156    VERBOSE    [6]    MVP request processed
2007-09-13 01:08:00.156    VERBOSE    [6]    MVP waiting for data
2007-09-13 01:08:05.156    VERBOSE    [6]    MVP data read: 1   (8)
2007-09-13 01:08:05.156    VERBOSE    [6]    Responding to ping
2007-09-13 01:08:05.156    VERBOSE    [6]    getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
2007-09-13 01:08:05.156    VERBOSE    [6]    MVP request processed
2007-09-13 01:08:05.156    VERBOSE    [6]    MVP waiting for data
2007-09-13 01:08:10.187    VERBOSE    [6]    MVP data read: 1   (8)
2007-09-13 01:08:10.187    VERBOSE    [6]    Responding to ping
2007-09-13 01:08:10.187    VERBOSE    [6]    getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
2007-09-13 01:08:10.187    VERBOSE    [6]    MVP request processed
2007-09-13 01:08:10.187    VERBOSE    [6]    MVP waiting for data
2007-09-13 01:08:10.593    VERBOSE    [6]    Unrequested needsRendering()...
2007-09-13 01:08:10.640    VERBOSE    [6]    Y/Y2 buffer: 5442 bytes
2007-09-13 01:08:10.687    VERBOSE    [6]    U/V buffer: 1018 bytes   (sent:5442)
2007-09-13 01:08:10.687    VERBOSE    [6]    U/V buffer: 1018 bytes@2
2007-09-13 01:08:10.687    VERBOSE    [6]    U/V buffer: 1018 bytes@3   (sent:1018)
2007-09-13 01:08:10.687    VERBOSE    [6]    incremental frame sent
2007-09-13 01:08:10.812    VERBOSE    [6]    MVP data read: 1   (3)
2007-09-13 01:08:10.812    VERBOSE    [6]    MVP request processed
2007-09-13 01:08:10.812    VERBOSE    [6]    MVP waiting for data
2007-09-13 01:08:21.234    VERBOSE    [3]    Received MVP Service Locator request
2007-09-13 01:08:21.234    VERBOSE    [3]    Parsing MVP Service Locator request
2007-09-13 01:08:21.250    VERBOSE    [6]    Unrequested needsRendering()...
2007-09-13 01:08:21.312    VERBOSE    [6]    Y/Y2 buffer: 5458 bytes
2007-09-13 01:08:21.328    ERROR    [6]    handleMVPConnection() exception: An existing connection was forcibly closed by the remote host
2007-09-13 01:08:21.328    VERBOSE    [6]       at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at GBPVRX2.MVP.x3ca133dee7547455.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
   at GBPVRX2.MVP.x3ca133dee7547455.xe75b6be209ce111f(Image x84901bd355736ef6)
   at GBPVRX2.MVP.x3ca133dee7547455.x3d75adb3418c5c9e()
   at GBPVRX2.MVP.x3ca133dee7547455.xd3faf5962405de4e()

Here's the error. Have been on 1.0.0.16 with the default dongle. Tried changing to .54 last night and that had no effect. Might try the mvpmc one as well - if none work then I need to kill the updates and see if it stablises.

Any ideas?

[mvallevand]

psycik, you actually don't provide enough data from the logs, because you don't show where the media socket stopped sending data, although you can tell it has crashed at 01:08:21.234 .

I would check to make sure that you have the minimize OSD for mvp checked, that you using the default blue mvp skin, go back to the 1.1.47 dongle, and that the gbpvr Simple Screen Saver is the one being used.

Martin

[psycik]

psycik, you actually don't provide enough data from the logs, because you don't show where the media socket stopped sending data, although you can tell it has crashed at 01:08:21.234 .

I would check to make sure that you have the minimize OSD for mvp checked, that you using the default blue mvp skin, go back to the 1.1.47 dongle, and that the gbpvr Simple Screen Saver is the one being used.

Martin

Ok, I'll try all those things and post a full set of logs when it next crashes. Is the .47 dongle the default one that come with gbpvr .16??

[mvallevand]

Yes 1.1.47 is the dongle with 1.0.16.

Martin

[sub]

The MVP server will typiclaly disconnect from the GB-PVR server if it doesnt get a response to a keypress within about 8 seconds. Does this same activity take a while on the PC?

The mvpmc dongle doesnt have this same limitation, so try that aswell.

[psycik]

Trouble is I wasn't actually "doing" anything, but watching the video - no key presses.

I will try the mvpmc as well...but the WAF is steadily decreasing (since it was doing it while I was away for the week), so I may re-image to see if it was a windows update thats done something to that machine.

I've been getting a couple of delayed write failures with other machines writing to a UNC share on the server - but they've been trying to upload large files.

[psycik]

Ok here is a full log. But what strikes me as odd, is I can't see it running a file.....

[sub]

Unfortunately there isnt anything obvious in the logs. It just looks like the MVP has disconnected for some unknown reason.

I'd definitely try the mvpmc dongle to see if it behaves different. At least with that we'd have a chance of working out why it is disconnecting.

[psycik]

Unfortunately there isnt anything obvious in the logs. It just looks like the MVP has disconnected for some unknown reason.

I'd definitely try the mvpmc dongle to see if it behaves different. At least with that we'd have a chance of working out why it is disconnecting.

Any preferable dongle?? I've downloaded the last stable (3.3) and the 0918 nightly build to try.

[mvallevand]

Any preferable dongle?? I've downloaded the last stable (3.3) and the 0918 nightly build to try.

I try to keep this page updated with my recommendations and occasionally adjust the dongle that sub's survival guide links to.

http://forums.nextpvr.com/showthread.php?t=25206

0.3.3 is not recommended at all, the nightly isn't too bad and I think for this test is sufficient. It does contain newer logic in a/v sync that myth users like but I haven't really positive feedback here.

Martin