2023-05-07, 07:31 PM
Sub after channel.stream.start either fails or has a client based-timeout should the client be issuing a channel.stream.stop in either or both cases?
Martin
Martin
2023-05-07, 07:31 PM
Sub after channel.stream.start either fails or has a client based-timeout should the client be issuing a channel.stream.stop in either or both cases?
Martin
2023-05-07, 08:50 PM
No, I don't think you need to make any stop call if you get a failure from channel.stream.start
2023-05-07, 09:40 PM
Ok thanks. What about the scenario, that fla experienced where NextPVR can't return failure because the client closes the socket on a timeout after a tuning delay. https://forums.nextpvr.com/showthread.ph...#pid581364 This snippet https://pastebin.com/NvGWL1j3 shows the gist removing a lot of spam from 3 clients connecting.
- Kodi is issuing a channel.stream.stop thread 48 on timeout before channel.stream.start thread 59 is finished. Kodi is unware of this. - fla tried to open Live TV again so we get a second channel.stream.start on thread 58 also before the channel.stream.start on thread 59 is finished. - I would expect that the ok return on thread 59 at 08:48:16.256 would fail because Kodi had disconnected and NextPVR should not continue one to started live tv. The purpose behind this is I am trying to figure out the best way to implement WOL on live TV for Kodi reminders and don't want to introduce problems. Martin |
|