Kodi sometimes cannot play channels

[mvallevand]

The cable company may have given you the device, that doesn't mean it is powerful enough to run Embruary or add several addons. BTW when I visited Greece a couple of years ago and got a SIM card at Cosmote I was impressed with prices and selection of devices compared to what we could get in here. The provider doesn't give us any choice.

I did try the test with 120 minutes earlier and couldn't duplicate it. These logs are a bit better since Kodi is see the error right away it is not a timeout issue now. Also do you have this problem on a PC running Embruary?

Sub how soon do you expect a lease after the stream starts?

Martin

[aderlopas]

The cable company may have given you the device, that doesn't mean it is powerful enough to run Embruary or add several addons.  BTW when I visited Greece a couple of years ago and got a SIM card at Cosmote I was impressed with prices and selection of devices compared to what we could get in here.  The provider doesn't give us any choice.

I did try the test with 120 minutes earlier and couldn't duplicate it.  These logs are a bit better since Kodi is see the error right away it is not a timeout issue now.  Also do you have this problem on a PC running Embruary?

Sub how soon do you expect a lease after the stream starts?

Martin

Hi Martin, 

The provider is indeed Cosmote but they give together with the service (for free) that one. Of course if you pay more you can get a better one...

Kodi on Windows works fine, no issues with Embuary skin and timeshifting with 120 minutes.

[mvallevand]

Live TV with 120 minutes of timeshifting well as can be expected on CWGTV Android 10 with Embruary here, the UI is too sluggish for me. Maybe consider removing your advancedsettings cache settings they don't look right for Matrix anyway.

Basically without additional feedback from sub I consider this closed from the addon's perspective.

Martin

[aderlopas]

Live TV with 120 minutes of timeshifting well as can be expected on CWGTV Android 10 with Embruary here, the UI is too sluggish for me.  Maybe consider removing your advancedsettings cache settings they don't look right for Matrix anyway.

Basically without additional feedback from sub I consider this closed from the addon's perspective.

Martin

Thanks Martin, I'll remove most of the advancedsettings and see what happens

[sub]

I see the below error in kod.log:

2021-11-04 20:54:08.803 T:8648    ERROR <general>: Open - Unhandled exception
2021-11-04 20:54:08.803 T:8648    ERROR <general>: Open - Error opening http://192.168.178.77:8866/live?channelo...timeout=10
2021-11-04 20:54:08.804 T:8648    ERROR <general>: AddOnLog: pvr.nextpvr: Could not open streaming file

Martin, does that "|connection-timeout=10" get included on the URL that comes to NextPVR, or just something used on the Kodi side, and stripped before sending to NextPVR?

[sub]

What I don't understand is why the below happens...

2021-11-04 20:54:07.762 [DEBUG][34] stopped live stream for timeshift
2021-11-04 20:54:07.762 [VERBOSE][34] RollingFile.Close()
2021-11-04 20:54:07.763 [VERBOSE][34] RollingFile.Close()

I don't think this in itself was causing any issues, but the attached should correct this double close.

[sub]

Sub how soon do you expect a lease after the stream starts?

It expires 15 seconds after starting the stream. I typically try to renew the stream like every 5 seconds or so, just to be sure.

[mvallevand]

No that curl extension will be processed by libcurl and tells it to wait up to 10 seconds for the connection (not for streaming). It goes back to 2018 before I started on this in earnest and is used on the basic call too.

For the lease I don't issue one until after streaming starts which is why I asked, I think I renew ever 7 seconds after that.

Martin

[sub]

There is a problem in the verbose log that sub might need to look at since I don't think this sequence should happen.

2021-11-01 12:59:28.759 [VERBOSE][8] RollingFile.Close()

2021-11-01 12:59:28.768 [DEBUG][88] Got request [192.168.178.43]: /service (channel.stream.stop)

In general this is sequence looks fine. LiveTV buffering starts with channel.stream.start, and continues happening all the time. The RollingFile messages you see in these logs are really the client connecting to opening the file (read-only, share write). The "RollingFile.Close()" message is just saying that client request is closing. The "/service (channel.stream.stop" log message is telling the server to stop the LiveTV buffering to stop (stop device etc)

[sub]

For the lease I don't issue one until after streaming starts which is why I asked, I think I renew ever 7 seconds after that.

Yep, that'll be fine.