2014-12-27, 10:41 AM
sub Wrote: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