Problems after Power Off MVP when Using Net Radio w/o Pressing Stop First (96.12)

[TuckerTFT]

OBSERVATION (v96.12): If you are listening to Net Radio via the MVP and then power it off without first pressing the STOP key on the remote (to stop the playing of the Net Radio stream), the next time you power on the MVP and try to play a Net Radio station or a Video, no playback will occur and you need to restart the Media MVP Server

[sub]

Are you manually running an MVP server? You should be running it using the autostart setting in the config app.

[TuckerTFT]

Can you enlighten me on what difference this will make?

I manually ran it all throughout my usage of 95.14 and did not experience the issue that I described at the start of this thread.

The reason I run it manually is that when it faults it seems the only way to restart it without interrupting the recording service (by a restart through the config app) is a manual start ... right?

[sub]

You should be running it using the autostart setting in the config app. Run this way, it'll restart the MVP server each time you press the MVP standby/power button, or each time it encounters a fault. This ensures the fault doesnt linger on.

The behaviour you described in your initial post has always been possible when you run it manually. I've seen it since the very first release of GB-PVR, but not bothered correcting it because things work much smoother when the MVP server is restarted after every fault or standby.

The specific problem you mentioned with Net Radio does not occur if you use gbmvp.bin instead of dongle.bin, since it shuts down much cleaner than the Hauppauge software.

[TuckerTFT]

Thanks, SUB. I am a bit concerned about using gbmvp.bin. I have the MVP patched version of GB-PVR (i.e., mvp-related-patch.zip) as I, like so many others, was experiencing frequent reboots of the MVP when watching recorded video with 96.12.

Like all the others, the patch fixed my reboot issue, BUT I did not switch to gbmvp.bin because there were so many problem reports regarding it with respect to the patched version.

Do you have yet another patch that resolves the gbmvp.bin issues?

[sub]

BUT I did not switch to gbmvp.bin because there were so many problem reports regarding it with respect to the patched version.

Do you have yet another patch that resolves the gbmvp.bin issues?

Its not as polished as dongle.bin yet, but I've not seen any reports of problems relating to using gbmvp.bin with the patch.

[TuckerTFT]

Ok ... I'll give it a try.

BTW, I am now starting the MVP Server per your recommendation (via the setting in the Config app) and I do already notice that the recovery is better.

However, what do you suggest I do if I encounter a problem where the MVP reboots and stays in the mode of "Contacting Servers ..."? I certainly don't want the recording service to restart in the middle of a recording.

In such cases I suppose that I could "End Process" on "GBPVR.exe" using Windows Task Manager and then just do a manual restart of the MVP Server.

However, I'm suspecting that in order to start the Server in the same mode that it starts via the Config app's setting you run GPPVR.exe. with some "switch" or "parameter" that allows it to start in the background / silent mode.

If I'm on the right rack on this, would you mind sharing with me what the command line would be to get it restarted that way so that I don't need to bring up the Config app and click "OK" within it, causing the recording service to restart as well?

Thanks.

[sub]

However, what do you suggest I do if I encounter a problem where the MVP reboots and stays in the mode of "Contacting Servers ..."? I certainly don't want the recording service to restart in the middle of a recording.

In that situation, GB-PVR will restart the MVP server in the background, so you shouldnt need to do anything.

However, I'm suspecting that in order to start the Server in the same mode that it starts via the Config app's setting you run GPPVR.exe. with some "switch" or "parameter" that allows it to start in the background / silent mode.

If I'm on the right rack on this, would you mind sharing with me what the command line would be to get it restarted that way so that I don't need to bring up the Config app and click "OK" within it, causing the recording service to restart as well?

-exitondisconnect is the parameter, but this will just cause the MVP server to exit (ie, not restart). Its the recording service that restarts it again.