Scheduling recording over network

[lif]

When using networked setup and scheduling recording to "real" PVR machine, it:

1) "thinks" a long time after submitting recording and finally gives error as there has been time-out connecting to recording service. But in fact it has submitted show for recording, as it shows up in master PVR's scheduled list. So, why this timeout?

2) won't wake master pvr up from standby/hibernate. show is listed as scheduled recording, but won't wake up. Unless the show is scheduled to future and there has been scheduled another recording physically from the master pvr machine console to start before it. So, it seems like recording service can't set new wake-up times when recording has been scheduled from remote "fat client".

[sub]

When using networked setup and scheduling recording to "real" PVR machine, it:

I dont know what you mean by "networked setup", so my answer below could be wrong for you specific setup.

1) "thinks" a long time after submitting recording and finally gives error as there has been time-out connecting to recording service. But in fact it has submitted show for recording, as it shows up in master PVR's scheduled list. So, why this timeout?

In a normal setup this is usually caused by a software firewall product stopping communication between the front end and the recording service. Or more likely this networked setup you've cobbled together isnt setup correctly for communication between the client and recording service.

2) won't wake master pvr up from standby/hibernate. show is listed as scheduled recording, but won't wake up. Unless the show is scheduled to future and there has been scheduled another recording physically from the master pvr machine console to start before it. So, it seems like recording service can't set new wake-up times when recording has been scheduled from remote "fat client".

This is because the recording service was never told that their were new recording that it needed to load. See error above.

[lif]

The "networked setup" means that one dedicated computer is running GBPVR with tuner and other ones (for example my laptop) are running GBPVR without tuners. In "client" config.xml recording service is pointed to "master's" service (tcp) and both "master" and "client" are pointing to the same UNC paths. No firewalls are enabled on either machine. Communication between master pvr recording service and client's gbpvr app must work, as client could read shows and tv guide from master's recording service and also submit new recordings, but can't get feedback from master's recording service that new recording was submitted ok (deletion works, deleting gives feedback to client).

Secondly, when "master" recording service receives new recording to be scheduled and also this new recording is visible on both machines gbpvr app, so why won't "master" recording service re-check if it has set wake up time to the most recent scheduled recording?

[sub]

I dont really know. GB-PVR doesnt include any direct support for networked client, so I'm not aware of what issues you may encounter when you try to trick GB-PVR into running this way.

In "client" config.xml recording service is pointed to "master's" service (tcp)

My guess is you got something wrong here, or you have a firewall getting in the way.

Communication between master pvr recording service and client's gbpvr app must work, as client could read shows and tv guide from master's recording service and also submit new recordings, but can't get feedback from master's recording service that new recording was submitted ok (deletion works, deleting gives feedback to client).

No, these do not indicate there is communication between the recording service and cient app. The client reads show listings directly from the database, it does not ask the recording service for this information. Like wise when scheduling and deleting recordings, it updates the database itself, then tells to the recording service to reload it's schedule. This last step is the only thing that communicates with the recording service, and is the thing that doesnt seem to be happening in your setup.

Secondly, when "master" recording service receives new recording to be scheduled and also this new recording is visible on both machines gbpvr app, so why won't "master" recording service re-check if it has set wake up time to the most recent scheduled recording?

As I said, the recording service doesnt store the recording, this is done by the client. When the recording service receives notification that it's schedule has to be reloaded, it'll check at that time whether any new recordings need 'a wake up call'. Your client is not telling the recording service to reload its schedule, so these wake up calls are never scheduled.

[lif]

Ok, thanks! Now I got the picture. So in my case I need to figure out how to trick the recording service to refresh itself.