Stuck at Menu

[Raymond]

OK I wasn't ready to quit yet so I did an ethereal packet trace to see if that would yield any clues. There is traffic both directions when I hit a cursor key on the remote sitting at the main menu. Some of the packet sizes indicates a fair amount of binary data. There are two or three packets ~1KB from the PC to the MVP after a button press.

I don't know what this means but I thought it might be helpful to some one out there....

[sub]

zip and attach your gbpvr.exe.log and I'll take a look.

[Raymond]

zip and attach your gbpvr.exe.log and I'll take a look.

It is attached. I sent three logs since the most recent one didn't actually have any MVP stuff in it....

Thanks for looking into this.
Raymond

[sub]

I dont know why its doing it, but your MVP is sending duff data.

When you press keys on your MVP remote, you'd normally get messages like this in your log:

5/11/2006 7:41:41 a.m..391 VERBOSE [8] User pressed: 44
5/11/2006 7:42:02 a.m..032 VERBOSE [8] User pressed: 19
5/11/2006 7:42:24 a.m..110 VERBOSE [8] User pressed: 30
...

In your logs you get:

11/4/2006 12:37:09 PM.500 VERBOSE [12] User pressed: 0
11/4/2006 12:37:10 PM.437 VERBOSE [12] User pressed: 0
11/4/2006 12:37:11 PM.031 VERBOSE [12] User pressed: 0
11/4/2006 12:37:12 PM.437 VERBOSE [12] User pressed: 0
...

"0" is an invalid key, so GB-PVR just ignores it.

[Raymond]

I dont know why its doing it, but your MVP is sending duff data.

When you press keys on your MVP remote, you'd normally get messages like this in your log:

5/11/2006 7:41:41 a.m..391 VERBOSE [8] User pressed: 44
5/11/2006 7:42:02 a.m..032 VERBOSE [8] User pressed: 19
5/11/2006 7:42:24 a.m..110 VERBOSE [8] User pressed: 30
...

In your logs you get:

11/4/2006 12:37:09 PM.500 VERBOSE [12] User pressed: 0
11/4/2006 12:37:10 PM.437 VERBOSE [12] User pressed: 0
11/4/2006 12:37:11 PM.031 VERBOSE [12] User pressed: 0
11/4/2006 12:37:12 PM.437 VERBOSE [12] User pressed: 0
...

"0" is an invalid key, so GB-PVR just ignores it.

Well great. I did read on their web site that they have added support for a new remote. I don't think I have the new remote as they described it having two buttons for the volume up and down. Mine has one that rocks back and forth. I supposed they have changed how they send the key codes. I'm assuming this means I'm SOL for a while. I guess I will install their software and use that. At least I can watch the prerecorded stuff.

Thanks. If there is anything else I can do for you let me know.
Raymond

[mvallevand]

Well great. I did read on their web site that they have added support for a new remote. I don't think I have the new remote as they described it having two buttons for the volume up and down. Mine has one that rocks back and forth. I supposed they have changed how they send the key codes. I'm assuming this means I'm SOL for a while. I guess I will install their software and use that. At least I can watch the prerecorded stuff.

Thanks. If there is anything else I can do for you let me know.
Raymond

Based on your strange log and the fact that you can use ethereal if you could find the eight byte packet that the mvp is sending to gbpvr that begins with 04 that would give an idea of what is being send. That should show if the remote has changed.

Martin

[Raymond]

Based on your strange log and the fact that you can use ethereal if you could find the eight byte packet that the mvp is sending to gbpvr that begins with 04 that would give an idea of what is being send. That should show if the remote has changed.

Martin

I'm assuming you mean eight bytes of data in the packet and not an 8 byte packet.

From the MVP to the PC, the data was:
04 00 00 00 00 00 00 13

I don't recall now if that was for cursor right or cursor down but I believe it was one of the two.

[sub]

Can you see if the attached patch helps?

I'm pretty sure the patch will be binary compatible with the rest of the release, but backup the original file in case you have problems.

[Raymond]

Can you see if the attached patch helps?

I'm pretty sure the patch will be binary compatible with the rest of the release, but backup the original file in case you have problems.

Wow, you scored first try. This seems to have taken care of the problem completely.

Is this something you can incorporate into the next release so it won't be lost?

Thanks,
Raymond

[mvallevand]

I'm assuming you mean eight bytes of data in the packet and not an 8 byte packet.

From the MVP to the PC, the data was:
04 00 00 00 00 00 00 13

I don't recall now if that was for cursor right or cursor down but I believe it was one of the two.

Sorry I did mean 8 bytes of data packet, I've been staring at these streams for so long, I ignore all the rest.

The strange thing here is, that you are seeing true VNC protocol for sending keystroke data and not the typical Hauppauge way and I'm really surprised to see this with the current dongle. I don't know why this isn't a problem for a lot more people.

Martin