New LG and Samsung NextPVR Web Smart TV App available for beta testing.

[fred250]

Good to know. Let me know what you find, and I'll adjust NextPVR to make it behave the same way in this scenario.

@sub
I finally got time to run wireshark on it and I'm confident that I've found the cause.

For growing files, the NextPVR streamer (/stream) report what seems to be a fake content-length and content-range that happens to be larger than the actual file size.
The Samsung F-player makes three requests to the streamer trying to determine duration and when it tries to take a sample towards the end of the file there is no data because were out of range.
The player gets stuck in this third stage.

There is also the small error that I have reported before where the header content-range is wrong according to specifications (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html section 14.16 Content-Range)
Maybe the NMT needs it this way?

Content-Range: bytes 0-50000000000/50000000000

ought to be
Content-Range: bytes 0-49999999999/50000000000

Not that it seems to be a problem but /stream doesn't seem to recognize the mime= option, is that intentional?


/Fred

[martint123]

Not a problem for you Fred -

My 40F5500 started playing movie trailers spontaneously. After much checking and many "factory resets" it looks like it may be a Samsung problem!
https://www.avforums.com/threads/samsung...s.1927455/

[mvallevand]

@sub
I finally got time to run wireshark on it and I'm confident that I've found the cause.

For growing files, the NextPVR streamer (/stream) report what seems to be a fake content-length and content-range that happens to be larger than the actual file size.
The Samsung F-player makes three requests to the streamer trying to determine duration and when it tries to take a sample towards the end of the file there is no data because were out of range.
The player gets stuck in this third stage.

There is also the small error that I have reported before where the header content-range is wrong according to specifications (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html section 14.16 Content-Range)
Maybe the NMT needs it this way?

Content-Range: bytes 0-50000000000/50000000000

ought to be
Content-Range: bytes 0-49999999999/50000000000

Not that it seems to be a problem but /stream doesn't seem to recognize the mime= option, is that intentional?


/Fred

All of those are sub's NMT mode streaming. I've reported the one byte issue for years, but sub was afraid that it would break the NMT. Did you try adding &mode=http recently which turns on more standard http streaming that XBMC needed? I know initially you had problems with that.

Martin

[fred250]

All of those are sub's NMT mode streaming. I've reported the one byte issue for years, but sub was afraid that it would break the NMT. Did you try adding &mode=http recently which turns on more standard http streaming that XBMC needed? I know initially you had problems with that.

Martin

I've been using mode=http for quite a while now. Don't recall any initial problems, but your memory is usually more accurate than mine
Anyway I had to add it at some point but can't remember if it was to please the LG or any of the Samsung players.

/Fred

[sub]

Ok. I'm away for a couple of days, but I'll look into this when I get back.

[mvallevand]

I've been using mode=http for quite a while now. Don't recall any initial problems, but your memory is usually more accurate than mine
Anyway I had to add it at some point but can't remember if it was to please the LG or any of the Samsung players.

Ok you got me thinking. I think for some reason you didn't want to use the preferred method /live?recording= ### for recording for some reason and you went with NMT mode. That one definitely gives back a changing content length for growing files.

Martin

[fred250]

Ok you got me thinking. I think for some reason you didn't want to use the preferred method /live?recording= ### for recording for some reason and you went with NMT mode. That one definitely gives back a changing content length for growing files.

Martin

Yeah, two reasons.
1: with /live incorrect duration and no skipping on the LG.
2: /live isn't (haven't checked recently) capable of streaming by filename as needed in the Videos plugin.

/Fred

[fred250]

@martin and sub

Some wiresharkin'

/live doesn't seem to handle ranges correctly – thats probably why the LG player can't calculate duration and also decided server is not range-request capable (skipping is ignored).
Both content-range and Content-Length seem to be incorrect.

These are the correct headers as far as I know.

Content-Range: bytes 4001-4500/1248620800
Content-Length: 500

Code:

GET /live?recording=855&mode=http&mime=video/MP2T&client=SMARTTV:1389635707887 HTTP/1.1
Host: 192.168.0.60:8866
Range: bytes=4001-4500
User-Agent: GStreamer souphttpsrc (compatible; LG NetCast.TV-2012) libsoup/2.34.2

HTTP/1.1 200 OK
Server: NextPVR
Connection: Close
Content-Range: bytes 4001-1248620800/1248620800
Content-Length: 499
Content-Type: video/MP2T

If these things were fixed and a filename option was added then I may drop the legacy /stream in favor of the more recent /live.

/Fred

[mvallevand]

Yeah you don't even need wireshark, web.log shows the inconsistencies for /stream mode I don't think you need mode or mime for /live it is supposed to be valid.

Here's request for the first 500 bytes and it does send 500 bytes but the headers are messed up indeed.

Code:

2014-12-27 16:55:34.407    [DEBUG][21]    partial file: bytes=0-499
2014-12-27 16:55:34.408    [DEBUG][21]    Reponse header:
HTTP/1.1 206 Partial Content
Server: N-PVR
Accept-Ranges: bytes
Content-Range: bytes 0-57278464/57278464
Content-Length: 499
Content-Type: application/octet-stream
Connection: close


2014-12-27 16:55:34.408    [DEBUG][21]    RollingFile.Seek(0)
2014-12-27 16:55:34.408    [DEBUG][21]    Sent: 500 bytes

Martin

[trummel]

Just had significant other approval to replace the old Sony TV for the bedroom. I would love to use this app instead of an external box as the NPVR client. Can anyone advise which current 32" TV would be pretty sure to work? I was leaning towards the LG's, but the current crop all seem to be WebOS. Does that work now? I'm very naïve about smart TV's as have never felt the need to buy one until now as have always had an NPVR client attached to do the smart bit.