Bug: Server keeps recording when Client goes S3 standby

[Loomy]

I have a GBPVR client on the network watching live TV streamed over the network from a GBPVR server. When the client enters S3 standby mode, the server continues recording... in my case until the hard drive filled up and I restarted the recording service

Note: I enter standby with the standby command in EventGhost.

[sub]

Reproduce the problem, then zip and attach the server logs and I'll take a look.

It shouldnt be possible. If the server doesnt get a request from the client every thirty seconds to renew it's tuner lease, then it assumes the client is no longer there and stops the recording and frees the tuner.

[Loomy]

To reproduce: I started the client watching tv, sent it to S3, and it continues recording on the server for minutes afterwards as I type this. However I'm looking at the logs (default debug mode) and nothing new has been written to any log since starting the test?

Restarting the recording services seems to have written to the logs. From the log I see that I started livetv on the client at :18 and restarted the server recordingservice at :33. I put the client to sleep within a minute of starting recording. Please see attached!

[sub]

Can you enable log flushing in the config app, then reproduce and repost the logs?

[Loomy]

Client recording started at :49, I flipped a few channels (I mention this but it doesn't affect the outcome), sent it to S3 standby, waited 5 minutes and it was still recording, so I restarted the recordingservice from server at :54, then copied logs.

[sub]

According to the logs your client PC connection disappeared at 08:50:18. At 08:51:00 it decided it had been more than 30 seconds since the client renewed its lease on the capture device, so it stopped the recording.

So it from the logs it looks like it continue recording for 42 seconds after the client disappeared, then it stopped.

[Loomy]

Man no wonder you think it works, your debugging information is deceiving you

I just did it again and I'm sitting here looking at a green tray icon and a temporary video file that keeps growing and growing, minutes more than 40 seconds after the client went to S3. But wait, I've found more!

I lucked out and started recording at the end of a show, such that the recording rolled over to a new show. And I see in the tray status that it is recording to a new file name based on a new show -- but it actually isn't, because I see it still writing to the original file name!

So I'm watching The Ellen DeGeneres Show_2_20070926_16001700.mpg grow, and that is the only file present.

But the tray status says it is recording "Guiding Light blah blah blah.mpg" which I don't see anywhere.

I even see this in the log: 2007-09-26 16:01:27.635 VERBOSE target filename: C:\Guiding Light_2_20070926_16001700.mpg

But I'm afraid that file does not exist. So the GBPVR logging is definitely getting some thing(s) wrong here.

I've restarted the recording server to dump this test for you to the logs. Good luck solving THIS gremlin

[sub]

Bump the thread in a week. I'll be home by then and will try reproducing it.

[Loomy]

Bump the thread in a week. I'll be home by then and will try reproducing it.

Bump for you!

[Loomy]

Bump for you!

This is the last breath for me