Live TV Freezes are still here with the NPVR Client V2.6.2

[Reddwarf]

My workround for the client hang problem is to start a recording, and then start playing it a few seconds later. I've not (yet!) seen a hang if I do that.

That's exactly how I do it, in fact there are indications that it happens here too, I'm using Martin's NetworkRecorder which acts as a client watching live tv, and sometimes those recordings are cut short, thou not nearly as often as before.

[mvallevand]

NetworkRecorder doesn't use the client protocol being discussed here. In RedDwarf's case it it uses the /live?channel http page of the web server.

Martin

[Reddwarf]

NetworkRecorder doesn't use the client protocol being discussed here. In RedDwarf's case it it uses the /live?channel http page of the web server.

Martin

So that's not the same protocol?

[mvallevand]

As I wrote, they are different.

Martin

[sub]

This patch wont fix it, but it adds more logging. Can you repost those logs with this patch installed on the server? ie stream.log, reader.log and nrecord.log.

[mvallevand]

Here you go I just updated to 1080i for testing and my logs are much bigger so here stream.log is a cut

Martin

[sub]

Thanks. Unfortunately you don't seem to have encountered the exact same problem as jpsa and msmith8228, so the extra logging didn't really help.

I was hoping to get one of those "recv2 got 0 bytes after timeout" messages.

Any chance you could try again and repost the logs?

[mvallevand]

I did get that but it was in the mpeg payload and then it never corrected back.

Martin

[sub]

No, it doesn't look like the same problem from the server side, even though the effect was kind of similar from the client side. The client timed out waiting for data the server got held up be for some unknown reason (in a different place than I've seen in logs before). I'm looking at the code based on those logs to try to find what might have happened in this case, but it'd still be beneficial to have another go at the logs.

[mvallevand]

Here you go, this is one of the header read 0 that fail like Jaggy's and others with the unable to switch log. I confirmed on the server that drive space was going down.

Martin