video freezes on external network

[chris4824]

everything works fine locally. I can use kodi which I do usually or Nextpvr locally to watch tv. The issue is only externally and the tests above was on wifi on both ends with the bitrate turned all the way down. I am wanting to get externally working cause I would like to be able to stream since I'm away alot. I notice in the web log also right before the unexpected error

Code:

[DEBUG][25]    Lease expired. Stopping transcode

Not sure why though.

Thanks sub

[sub]

Can you reproduce then post the web.log and nrecord.log?

[chris4824]

Can you reproduce then post the web.log and nrecord.log?

here are all the logs. this is with the android client. not around browser to reproduce with it. played for alittle while longer this time

[ATTACH=CONFIG]45556[/ATTACH]

Thanks sub

[chris4824]

what are these other ports in the nrecord log 8968 and 7969? should they be fowarded as well?

[sub]

what are these other ports in the nrecord log 8968 and 7969? should they be fowarded as well?

They don't need to forwarded. They're just for communication between NextPVR.exe and NRecord.exe.

[sub]

Whilst you're watching live tv, the browser or android app is regularly making a request in the background like http://ipaddress:8866/services/service?m...code.lease, which tells the recording service that you're still actively trying to watch the stream. If these requests stop arriving, it assumes the user has stopped watching the stream, and it frees up the tuner.

In your case, those calls have stopped arriving. It's not clear to me why though. So, after 10 seconds or so of not receiving one, it eventually decides you no longer need the device and the stream is stopped.

I wonder if maybe something like a caching proxy from your internet provider has stopped passing the requests on, because it can reply with the cached version.

[sub]

You might need to use Chrome, an press F12 to get the developer tools, go to the network tab, and you should see these regular channel.transcode.lease calls, and see what happens to them around the time of problem.

[chris4824]

But does that also applies to the web browser since it continues to feel up with ts files in web/temp folder and also continue the ts files in buffer folder and the tuner is not freed up like it does with the Android client. Only the Android client frees up the tuner. The web browser has the same issues and error messages except for freeing up the tuner and stopping recording.

Hope I explained that right.

[mvallevand]

Could it be a lock problem reading the m3u8 when ffmpeg is renaming the tmp file?

Martin

[sub]

The logic does apply to the web browser too. I'm just commenting on what I'm seeing in that specific log though, so for this particular run for the Android. - if you're seeing something slightly different with the browser, I'd need to see the logs from the browser attempt to be able to comment.