2022-04-18, 08:29
Hello Phunkyfish
believe me or not, but it took now in total 16(!) month until kodi19 became available als LibreElec for the Pi 3, so even if we did our first trials with the beta 19 on Android Firestick already in the end of 2019, I had to wait until now to switch my SAT-IP Receiver from http:// to rtsp:// for my "main" raspi 3 TV..
When doing that, I made two observations:
the satip:// protocol seems not to have made it into the final release - when I send a satip:// URL to play via jsonRPC Player.Open(), I get
CreateLoader - unsupported protocol(satip) in satip://192.168.1.113/?freq=1
but that's no problem, as rtsp:// is working.
But that brings me to observation 2, which was also a problem in Kodi 18 with http:// URLs, but I've hoped that kodi 19 with rtsp:// will fix it:
When I'm using the simple IPTC client, I can move through the channels with the cursors keys nearly instandly from one channel to the next, it just takes some seconds for the receiver to switch.
But when I try to switch remotely during watching a channel by sending a Player.Stop() / Player.Open(NewURL) sequence, the new URL always fails. I always have to wait around a minute (60 secs) before I can sent a new URL after stopping the old one.
So I guess that this 60 secs could be a prototol timeout in my satip server, but which does not appear with the simple IPTV client. So when remembering our initial investigation about the implemention of rtsp/satip, there was a protocol command TEARDOWN which the client shall send to terminate a running stream.
So I assume that the simple iptv client correcty sends the TEARDOWN command before switching a channel, while my remote Player.Stop() command simply cuts the rtsp control tcip link, which it interpreted by my satip server as a network failure and so the server waits for 60 secs for the tcp connection to come back.
So my questions would be:
Please give me some advice about how to proceed best ;-)
And of course thanks for your great work - your player and the iptv client is doing a perfect job here all day
believe me or not, but it took now in total 16(!) month until kodi19 became available als LibreElec for the Pi 3, so even if we did our first trials with the beta 19 on Android Firestick already in the end of 2019, I had to wait until now to switch my SAT-IP Receiver from http:// to rtsp:// for my "main" raspi 3 TV..
When doing that, I made two observations:
the satip:// protocol seems not to have made it into the final release - when I send a satip:// URL to play via jsonRPC Player.Open(), I get
CreateLoader - unsupported protocol(satip) in satip://192.168.1.113/?freq=1
but that's no problem, as rtsp:// is working.
But that brings me to observation 2, which was also a problem in Kodi 18 with http:// URLs, but I've hoped that kodi 19 with rtsp:// will fix it:
When I'm using the simple IPTC client, I can move through the channels with the cursors keys nearly instandly from one channel to the next, it just takes some seconds for the receiver to switch.
But when I try to switch remotely during watching a channel by sending a Player.Stop() / Player.Open(NewURL) sequence, the new URL always fails. I always have to wait around a minute (60 secs) before I can sent a new URL after stopping the old one.
So I guess that this 60 secs could be a prototol timeout in my satip server, but which does not appear with the simple IPTV client. So when remembering our initial investigation about the implemention of rtsp/satip, there was a protocol command TEARDOWN which the client shall send to terminate a running stream.
So I assume that the simple iptv client correcty sends the TEARDOWN command before switching a channel, while my remote Player.Stop() command simply cuts the rtsp control tcip link, which it interpreted by my satip server as a network failure and so the server waits for 60 secs for the tcp connection to come back.
So my questions would be:
- Should I raise a ticket for this (Where is the best place?)
or
- does a simple workaraund exist and would I just have to use another jsonRPC sequence to make it work?
Please give me some advice about how to proceed best ;-)
And of course thanks for your great work - your player and the iptv client is doing a perfect job here all day
