![]() ![]() ![]() ![]() |
|
Looks like its the January release 2018.01-1
Thought maybe there had been a more recent update - but that is the latest - just checked.
Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler
Same here.
I wonder why I'm having an issue whereas you're not.
Would it be possible for you to enable debug logging then capture the kodi.log playing tvnz1 so I can compare your log to mine and maybe we can spot a difference?
As I said a few posts earlier, the stream does sometimes eventually start, but it can take a really long time and will often timeout.
I know my internet speed is fine, and OSMC has good connectivity.
Okay, I've backed up my SD card to a .img file then upgraded to the latest alpha Kodi Leia (18) nightly build.
This seems a lot more snappy, starting media over UNC is near instant so it seems there's been a lot of work.
Testing the TVNZ 1 & TVNZ 2 live streams is showing them as working, anecdotally a bit faster.
TVNZ Duke won't start before timeout (20s according to stopwatch) and I've increased the <playlisttimeout> in advancedsettings.xml to 45 seconds but timeout still seems to be 20 sec (default)
Progress.. I guess?
agrath:
@apsattv - thanks, so did you remove some channels from the top level listing (available channels) or streams from the individual TVNZ channels?
I think it's the later that causes the fault in this version of Kodi/OSMC.
I have just tested it and can confirm that this time, the stream did start, but it took nearly 2 minutes before it managed to do so.
I suspect this is just coincidence as for whether it starts or not is really down to how quickly Kodi can sample all the available HLS streams on the channel before selecting the one it's going to use.
In case anyone else is having the same issue,
I've attached a video link of my phone pointed at the TV showing a spinning progress bar for around 2 min, followed by the channel finally starting and a debug log from the same session.
If you review that log, you can see that I attempt to start the stream at 11:58:30 ("OpenLiveStream - opening live stream on channel 'TVNZ 1'") then there's a bunch of "opening ..." followed by "no longer receiving" as Kodi samples all the available streams.
Finally, "Open - avformat_find_stream_info starting" nearly 2 min later after all the streams have been checked, then bitrate/stream information about the selected stream, followed by playback actually starting.
I think there's probably not much you can do @apsattv because the count of the streams inside the m3u8 from TVNZ is where the problem is coming from?
Video: https://www.dropbox.com/s/1a18d2nkgkg4m9r/2018-03-03%2011.58.26.mov?dl=0
Log: https://www.dropbox.com/s/31wbh4isldxhosn/kodi-playback-livestream-20180303.log?dl=0
I'm not aware of any major outstanding live tv issues. I do know that some IPTV providers have been blocking the OSMC user agent. As a result, we recently masqueraded this. In the future, we'll add support for changing user agent to a number of common applications (VLC for example) via the GUI.
Can you put the log on https://paste.osmc.tv and confirm which device you're using?
Is it by any chance a UDP stream?
Sam
Hi Sam, thanks for checking the thread.
Here's the log moved to paste.osmc.tv
https://paste.osmc.tv/qaxepaqeki.vhdl
I am using an rpi2 (now with the latest leia alpha build 187) with osmc installed natively to SD card.
Doesn't look like UDP to me, after the m3u8 gets parsed this is the sort of stuff I see:
ffmpeg[4B8FF300]: [hls,applehttp] Opening 'crypto+https://tvnzioslive04-i.akamaihd.net/hls/live/267188/1924997895001/channel1/20180227T103733/masterR_11/00019/masterR_11_01407.ts' for reading
Leia is uncharted waters for now. I would recommend trying to reproduce on v17 first.
Yes, I agree. Alpha anything is! The log I attached is from v17 - I upgraded to 18 for testing purposes, backing up my SD card first so I could roll back if needed.
v18 seems better, but still takes over 20s to start the stream, from reading the log it looks like ffmpeg is trying all the streams inside the playlist for the channel before it selects one and finally starts.
We had a Vero user with a similar problem, but they were using UDP streams.
I added this improvement: https://github.com/osmc/osmc/commit/a9ad489d2a0e4184f11984a5cf77bfa31c1791ab but only for the Vero platform as it had only been verified on this device.
I'll ping gmc on our team who produces v18 nightlies and get him to include it for Pi as well.
Cheers
Sam
agrath:I found anything above Kodi 16.1 version was taking an age to start live streams so I am still stuck on that for now .
Yes, I agree. Alpha anything is! The log I attached is from v17 - I upgraded to 18 for testing purposes, backing up my SD card first so I could roll back if needed.
v18 seems better, but still takes over 20s to start the stream, from reading the log it looks like ffmpeg is trying all the streams inside the playlist for the channel before it selects one and finally starts.
Are you using the apsattv supplied streams or the Matt Husiman ones
Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler
robjg63:Hi , have just tried the Matt Husiman ones on Kodi 17.6 and have to say they are a lot quicker than the last versions I have tried . Unfortunately the BBC and ITV players still take an age to start live streams compared to Kodi 16.1 .
Are you using the apsattv supplied streams or the Matt Husiman ones
VPN might be complicating things if you are using one. If the patch is applicable for Leia we can include it.
Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler
|
![]() ![]() ![]() ![]() |