remote control delays, mvp crashes

[shuot]

I'm assuming you do get the GBPVR main screen so you should unplug your mvp and then send your logs if you still have problems.

Here is some causes

- old versions of gbpvr or hauppauge software
- udp port 16869 by firewall
- network errors causing dongle not to load.


Martin

Hi Martin !

I've explicitely unblocked the 16869 port from Windows XP firewall.

But it didn't changed the version number. I got these version numbers from
the "scan" screen from the MVP.

I've attached my logs, you can see it.

About the GBPVR version, it is v0.99.12.

This problem is very annoying.

Bye!

[mvallevand]

Hi Martin !

I've explicitely unblocked the 16869 port from Windows XP firewall.

But it didn't changed the version number. I got these version numbers from
the "scan" screen from the MVP.

I've attached my logs, you can see it.

About the GBPVR version, it is v0.99.12.

This problem is very annoying.

Bye!

Based on those logs you are loading the dongle properly.

To verify after loading the dongle you have to
- power off your mvp
- disconnect your gbpvr server from the network or power it down
- power up your mvp and check the version again.

Martin

[shuot]

Based on those logs you are loading the dongle properly.

To verify after loading the dongle you have to
- power off your mvp
- disconnect your gbpvr server from the network or power it down
- power up your mvp and check the version again.

Martin

Hi I tried this, and the version number is still 1.1.38.

See attached picture.

So what can we conclude ?

So far:

1- The dongle.bin is loading properly, as showed in the logs.

That means no network issues should happen.

2- Using your last sequence, the version displayed on my MVP is still 1.1.38.

. . . is it possible that I don't have the proper dongle.bin file ?

In order to validate this, I put an MD5 computation of my dongle.bin
file in attachment.

Can you validate this ?

Thanks!

Bye!

[User]

Sorry to butt in but let me take a stab at it. I agree your dongle is loading properly. The screen shot you have there shows that dongle.bin is loaded. I get that same screen myself. What happens is that right after the dongle loads it does not immediately detect the server. Look at the bottom of the screen it says you can hit OK to rescan, this is what I have to do here. Usually if you hit OK after the first scan it will detect the network on the second try, then you select the server (if theres only one it will already be highlighted) and hit OK again within 5 seconds and it will set it as the default server. Should be smooth sailing at that point. I read some of the thread above and it looks like you are just not hitting the OK button on the remote to try to scan again, and this is what I have to do most times when I reload the dongle. If I am off base then I did not read enough above, hope it helps.

[shuot]

Sorry to butt in but let me take a stab at it. I agree your dongle is loading properly. The screen shot you have there shows that dongle.bin is loaded. I get that same screen myself. What happens is that right after the dongle loads it does not immediately detect the server. Look at the bottom of the screen it says you can hit OK to rescan, this is what I have to do here. Usually if you hit OK after the first scan it will detect the network on the second try, then you select the server (if theres only one it will already be highlighted) and hit OK again within 5 seconds and it will set it as the default server. Should be smooth sailing at that point. I read some of the thread above and it looks like you are just not hitting the OK button on the remote to try to scan again, and this is what I have to do most times when I reload the dongle. If I am off base then I did not read enough above, hope it helps.

User,
the point was to get into this screen in order to validate that
the (proper version of the) dongle.bin has been loaded.

Usually, I don't get this screen at all.

Bye!

[pirosity]

I'm having the same problem as well with my MVP. Just bought the thing yesterday and everything looked great however half-way through a 2-hour recording the symptoms mentioned earlier in this thread started occuring (stuttering playback, remote control delays, GBPVR crashes, stuff like that).

The MVP (H3 rev) is a wired version connected to my wireless router and my PC running GBPVR (3GHz with 1.5GHz ram) is wireless 802.11g to the router. If the media server is not running I get the same screen that shuot posted (1.1.38/1.1.38 in bottom right corner). Also, I find that I have to manually start the media MVP server on the PC running latest 0.99.12 GBPVR (yes I do have the config setting on the MVP tab for the number of auto-start servers set to 1).

I know you guys are already trying to help Shuot with this and I'm patiently monitoring this thread, however I thought maybe my logs might be of some assistance. BTW, in the log file "MVP-gbpvr.exe-1" it mentions "Received MVP TFTP request: dongle.bin.ver" so I think maybe the MVP is getting the dongle...

[mvallevand]

User,
the point was to get into this screen in order to validate that
the (proper version of the) dongle.bin has been loaded.

Usually, I don't get this screen at all.

Just because you get that screen I'm not saying you aren't loading the new dongle, but I have attached what I am see on the option pane (1.1.54 is the latest Hauppauge offering the I use to baseline mvpmc). If you aren't sure, I would suggest trying to see if the mvpmc dongle loads.

Note that some people have had problems with the 1.1.52 dongle that is in with 99.12, so you might what to copy the dongle.bin from one of the beta Hauppauge installs.

Martin

[pirosity]

BTW, Shuot have you tried the MVPMC yet? I tried the Alpha build last night and it seems to work pretty good for me so far.

edit: actually, I'm not sure if MVPMC was the fix since I had to go back to the old dongle due to MVPMC crashes. I think it may be working now because I had also used an optimization registry entry from the Hauppauge website (http://hauppauge.lightpath.net/software/...ation.reg). Either way, my MVP hasn't had the same stuttering issues since yesterday so hopefully that fixed the problem.

[shuot]

BTW, Shuot have you tried the MVPMC yet? I tried the Alpha build last night and it seems to work pretty good for me so far.

edit: actually, I'm not sure if MVPMC was the fix since I had to go back to the old dongle due to MVPMC crashes. I think it may be working now because I had also used an optimization registry entry from the Hauppauge website (http://hauppauge.lightpath.net/software/...ation.reg). Either way, my MVP hasn't had the same stuttering issues since yesterday so hopefully that fixed the problem.

Hi!

No, I haven't tried it. Actually, using it means loosing GBPVR interface,
control and access. So, it's very uninteresting.

I'd rather like to have my problem fixed ! :-)

Thanks!

Bye!

[shuot]

Just because you get that screen I'm not saying you aren't loading the new dongle, but I have attached what I am see on the option pane (1.1.54 is the latest Hauppauge offering the I use to baseline mvpmc).

Mavellan, how can I get in the same setup screen as you ?

If you aren't sure, I would suggest trying to see if the mvpmc dongle loads.

. . . a pretty good idea ! It could confirm if dongle loading works
or not in my setup. I'll try this.

Note that some people have had problems with the 1.1.52 dongle that is in with 99.12, so you might what to copy the dongle.bin from one of the beta Hauppauge installs.
Martin

. . . thanks, I'll also try this.

Bye!