NextPVR Forums

Full Version: Http Streaming from NextPVR
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I am currently playing with using Serviio to play a live stream from NextPVR for transcoding live TV from an original HdHomerun Dual ATSC tuner.
ex....http://192.168.0.105:8866/live?channel=27

I need the transcoding for 2 tv's in the house still running old school Xbox's. It works like a champ, but does not seem to support using both tuners at once by way of http streaming. It does seem to work using both tuners if one tuner is using the http stream and the other is being used by the NextPVR window on the PC. Am I missing a setting or is tuner availibility limited to only one tuner using the http streaming method?
When it receives the second request, it assumes it's for the existing session changing channels. Identify it as a separate stream using the "client" parameter.

http://192.168.0.105:8866/live?channel=27&client=1

and

http://192.168.0.105:8866/live?channel=27&client=2
just wondering aloud sub, couldn't you automatically separate requests from different clients using the last byte of the source IP address, assuming no "client" parameter has been specified?
There can be multiple clients from the same address. For example, MB3, which runs a server on one machine, which transcodes video and serves it up to it's clients.

Also, we've found we can't rely on connection ending to mean a resource is no longer required. Some clients request the same url several times as part of starting playback, sometimes closing each connection before requesting the new one, or sometimes closing the previous connection after requesting the new one.
sub Wrote:There can be multiple clients from the same address. For example, MB3, which runs a server on one machine, which transcodes video and serves it up to it's clients.
right, I understand that, "formal" clients would be properly programmed to provide the &client= paramter. I was just suggesting it might make things easier (and produce fewer support requests) for users who are manually setting up random playback clients by various methods (like the OP in this thread), if NPVR could handle it automatically by IP address when no &client= parameter is provided. Obviously that wouldn't help the multiple clients from the same address scenario, they'll still have to be done correctly.
The OP is streaming from the Serviio UPnP server the client will end up being other IPs true but NextPVR couldn't tell that. Sub's approach is safest based on what I have seen.

Martin
Yeah i put it in for plex transcoding (it always looks like it's from the same location) and it worked well.
may well be a case where getting the user to do it right in the first place is better than working around them doing it the easy way...
sub Wrote:When it receives the second request, it assumes it's for the existing session changing channels. Identify it as a separate stream using the "client" parameter.

http://192.168.0.105:8866/live?channel=27&client=1

and

http://192.168.0.105:8866/live?channel=27&client=2

Thanks....will give it a shot tonight.