New alpha dongle Dec. 04

[jksmurf]

OK, I think I have logs for you.

I did the Putty keystrokes, then played aorund with button presses for about 2 to 3 mins then watched ER (about 45 mins), pausing & rewinding on occasion. There were a couple of instances where the remote didn't respond, or not instantly or not until a second press.

The putty log has a few "ping stuck" and "broken pipe" messages but apart from that doesn't look too bad?

I got this error in MVP-PVRX2.exe.log. Wonder if it's because I used Xrecord and skinning is not OK?

Code:

2007-12-13 19:17:28.611 INFO [6] Reading path Converter3
2007-12-13 19:17:28.611 ERROR [6] Unable to find node: /settings/Custom/ConverterElement[@name="converter3"]
2007-12-13 19:18:51.310 ERROR [6] Unable to find node: /settings/Custom/ConverterElement[@name="converter3"]
2007-12-13 19:18:51.310 ERROR [6] Unable to find node: /settings/Custom/ConverterElement[@name="converter3"]
2007-12-13 19:20:07.359 ERROR [6] Unable to find node: /settings/Custom/ConverterElement[@name="converter3"]
2007-12-13 19:20:07.359 ERROR [6] Unable to find node: /settings/Custom/ConverterElement[@name="converter3"]
2007-12-13 20:10:14.453 WARNING [6] requested skin file not found: C:\Program Files\devnz\gbpvr\skin2\blue\Video Library\mmc.xml
2007-12-13 20:10:14.683 ERROR [6] Could not load file or assembly 'file:///C:\Program Files\devnz\gbpvr\Interop.IWshRuntimeLibrary.dll' or one of its dependencies. The system cannot find the file specified.
2007-12-13 20:10:14.824 ERROR [6]    at GBPVRX2.x2be64c56dcebf65e.x329d6ba583621f49(Boolean x19ea53fbdff360c7)
   at GBPVRX2.x2be64c56dcebf65e.PopulateListWidget()
   at GBPVRX2.BaseButtonListUiTask.initialise()
   at GBPVRX2.x2be64c56dcebf65e.initialise()
   at GBPVRX2.BaseButtonListUiTask.Activate()
   at GBPVRX2.MenuTask.xd2a3a83a17aec615.OnKeyDown(KeyEventArgs e)
   at GBPVRX2.MVP.x3ca133dee7547455.x3d75adb3418c5c9e()
2007-12-13 20:10:37.005 WARNING [6] requested skin file not found: C:\Program Files\devnz\gbpvr\skin2\blue\Recordings\mmc.xml

This was probably a killall mvpmc effect

Code:

2007-12-13 19:11:35.152 VERBOSE [12] About to load listings for: TVB Pearl
2007-12-13 19:11:35.233 ERROR [6] MVP Exception: An existing connection was forcibly closed by the remote host
2007-12-13 19:11:35.243 ERROR [6]    at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 size, SocketFlags socketFlags)
   at GBPVRX2.MVP.x3ca133dee7547455.xe1a1ccdd0f419e78()
   at GBPVRX2.MVP.x3ca133dee7547455.x3d75adb3418c5c9e()
2007-12-13 19:11:35.243 VERBOSE [6] getValue() loading new key/value into cache: /settings/Culture

This one is VERY ugly, but it's from JULY... :-)

Code:

2007-07-06 11:01:20.525 ERROR [14] Unexpected error in MVP async handler: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
   at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
   at GBPVR.xbb1566157f5f8b1f.x458c85690540575e()
2007-07-06 11:01:20.685 ERROR [14] Unexpected error in MVP async handler: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
   at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
   at GBPVR.xbb1566157f5f8b1f.x458c85690540575e()
2007-07-06 11:01:20.785 ERROR [14] Unexpected error in MVP async handler: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
   at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
   at GBPVR.xbb1566157f5f8b1f.x458c85690540575e()
2007-07-06 11:01:21.015 ERROR [14] Unexpected error in MVP async handler: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
   at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
   at GBPVR.xbb1566157f5f8b1f.x458c85690540575e()
2007-07-06 11:01:21.326 ERROR [14] MVP Timer Refresh error: An existing connection was forcibly closed by the remote host
2007-07-06 11:01:21.336 ERROR [14]    at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.Socket.Send(Byte[] buffer)
   at GBPVR.xbb1566157f5f8b1f.xcca58d4608994dd8(Point x557cda7ca079f710, Rectangle x19534874af95b268, Bitmap x84901bd355736ef6, Boolean x484012b92f24af4e)
   at GBPVR.xbb1566157f5f8b1f.xe75b6be209ce111f(Image x84901bd355736ef6)
   at GBPVR.xbb1566157f5f8b1f.xb1cbc922a07ef39b(Object xdf2e3583f942db7b, EventArgs xc4f45905cb1fc7ba)

k.

[mvallevand]

k, thanks I will have look latter. Was there a specific problem in these logs though were you completely lost access?

You do seem to be missing this file http://forums.gbpvr.com/showpost.php?p=2...stcount=36

The problem of missing a few keystrokes though is by design. While mvpmc is waiting for the return of heartbeat signal I don't allow keystrokes to be send, the stuck message. This is to avoid the situation that you had where you hit five keystrokes in one second. If I had queued those gbpvr would have had to deal with 2 channel ups and 3 channels downs which would have been very odd. I explained the pipe error in an earlier message.

Martin

[Sheik Yerbouti]

It worked, I've got a client log and a moment where the the mvp didn't respond to my remote! The time was aprox. 20:32. I hope you can make something of this, Martin.

[mvallevand]

It worked, I've got a client log and a moment where the the mvp didn't respond to my remote! The time was aprox. 20:32. I hope you can make something of this, Martin.

Thanks Sheik, I see the issue, and will look further. Can you let me know if your problem is usually a temporary issue or the if the remote is dieing and you need to kill everything with the green button power off.

Sub, in the server side log, when the problem occurred I noticed a message on the rfb stream that I don't recognize, DisplayStillInUse. What is this message?

Martin

[jksmurf]

k, thanks I will have look latter. Was there a specific problem in these logs though were you completely lost access?

No, no complete loss of access, just a delay sometimes, you press a key Left or Right or Up or Down mostly and , it wasn't as bad during this session as sometimes, where it acts like a dead remote.

You do seem to be missing this file http://forums.gbpvr.com/showpost.php?p=2...stcount=36

Good catch!

The problem of missing a few keystrokes though is by design. While mvpmc is waiting for the return of heartbeat signal I don't allow keystrokes to be send, the stuck message. This is to avoid the situation that you had where you hit five keystrokes in one second. If I had queued those gbpvr would have had to deal with 2 channel ups and 3 channels downs which would have been very odd. I explained the pipe error in an earlier message. Martin

OK.
k.

[Sheik Yerbouti]

Thanks Sheik, I see the issue, and will look further. Can you let me know if your problem is usually a temporary issue or the if the remote is dieing and you need to kill everything with the green button power off.
Martin

Thanks for your effort, Martin!
It's temporary. Eventually the mvp starts responding again, but sometimes I think it's taking too long, so I power off.

[mvallevand]

No, no complete loss of access, just a delay sometimes, you press a key Left or Right or Up or Down mostly and , it wasn't as bad during this session as sometimes, where it acts like a dead remote.

What I really now need to see now from everyone is what happens after the Go Ok is hit. Every client log has shown mvpmc doing things in exactly the order I expect and with no unusual socket errors.

I did notice that for each time that Sheik described a pause there was a DisplayStillInUse message so if sub elaborates on this there might be a clue.

Also could everyone confirm the date on their mvpmc file as being the 9th I checked the site again and it does some to be the Dec 9th version, I haven't seen this version Note if you use the /etc/mvpmc/mvpmc you don't need to reload the dongle the killall restart is fine even from the share.

Martin

[jksmurf]

What I really now need to see now from everyone is what happens after the Go Ok is hit. Every client log has shown mvpmc doing things in exactly the order I expect and with no unusual socket errors.

Wow, good dongle! OK, will do :-)

Also could everyone confirm the date on their mvpmc file as being the 9th I checked the site again and it does seem to be the Dec 9th version, I haven't seen this version.

I did d/l the file again after you noted in another thread that it doesn;t seem to have been updated. I believe the Sunday, 9 December 2007, 11:12:30 p.m. datestamp is correct.

Note if you use the /etc/mvpmc/mvpmc you don't need to reload the dongle the killall restart is fine even from the share. Martin

:confused:

k.

[mvallevand]

When I run from a share I see

Version a646f958fe2cbd9a8fba59cb31491d1c6a5a6477 with 52 local changes
Sun Dec 9 22:16:48 EST 2007

The third point was if you are running from a share there is no reason to unplug your mpv to go from the 4th to 9th version.

Martin

[leaded1]

I have had the dead remote issue in the past, and have been following this thread. I haven't had much time to play with it, but I was getting an unresponsive remote yesterday ( Dec 4th dongle) and the "Go" "OK" sequence seemed to get everything back to normal again.
-Edit-
Tried again today with the December 9th dongle. Got unresponsive remote after 10-15 minutes in one recorded TV show. The commands (several pauses presses, one skip back) did not execute before the end of the recording (~ 5-10 minutes). The video exited to the Play/Delete/Close pop-up at the end of the recording, with the remote still not responding. Pressed Go OK and and the remote responded. (pop-up closed and I could navigate the recordings list)

Hope this is helpful