Limit on Live TV Streams.

[kcmcdona]

I have been running with two analog tuners in NPVR 2.5.9 R1. Using the client= parameter on the streaming URL, I have been able to successfully support two concurrent live streams from remote VLC clients. I recently added a third analog tuner, and its associated set top box. All of the tuners are working, with their corresponding infared blasters, etc. However, when I try to start more than two live tv streams, the third one fails. I know the third tuner will support live streaming, because I checked the box to allocate tuners in reverse order to live tv, and the new tuner works successfully, if it is not the third session attempted.

I have attached logs of this scenario. The only difference I note in the log of the third live tv session startup is that it is missing the message: "Live TV handle: 0x-----'. Then it appears in the log to start over in starting the stream, then fails because no tuner is available. This occurs at time: 9:00:48 or so.

I've looked for some parameter for a limit on live streams, but can't seem to find any. What am I missing?

Kelly McDonald

[sub]

The app doesn't impose any limit on this, and it should be possible to do what you're suggesting.

Does it help if you add a unique identifier to each by adding something like this to each VLC's url:

&client=VLC1
&client=VLC2
&client=VLC3

[kcmcdona]

I do have a unique client= parameter on each stream.

I tried to invoke three simultaneous recordings, and this works fine. It seems to be limited to simultaneous live streams.

Kelly

[kcmcdona]

In looking at the VLC logs, it appears that on the third stream, VLC receives a successful TCP connection, but then receives an http error:
'access_http error: error: HTTP/1.1 404 Not FoundServer: NextPVR'

It appears that VLC retries the connection several times, which probably accounts for the retries showing up in the NextPVR log, but the second time, no tuners are available, since I assume the tuner allocations are still being cleaned up.

I directed the VLC clients to another NexPvr server that utilizes HDHomeRun Prime as its tuner base, and it experienced the same symptoms. So that seems to rule out any analog tuner dependancy. It seems to be replicable across different NextPVR implementations. Kelly

[sub]

Can you post the logs showing the HDHomeRun attempt?

[kcmcdona]

Here they are. Kelly

[sub]

Unfortunately I'm not sure what to suggest on that one. I've had a good look at the logs, and can see an error messages in both that makes no sense whatsoever, but I'm not sure what it means.

I had a try at reproducing it here, albeit with digital devices, but wasn't able to see the problem happen here.

[kcmcdona]

The NextPvr server with hdhomerun tuners also has digital ATSC tuners. I tried the same test, but mixing the tuners for streaming, (1 ATSC, and 2 hdhomerun), and three live streams work fine. So, it seems that the problem manifests itself when more than two tuners streaming are of the same type. When tuner types are mixed, the problem doesn't manifest itself. I don't think it has to do with the tuner drivers, because when recording, all three can be active. Kelly