Project

General

Profile

Bug #2998

Bug #2999: Do not start streaming on HTTP HEAD request

Resolution metadata missing

Added by Mr. Blond about 6 years ago. Updated about 6 years ago.

Status:
Invalid
Priority:
Normal
Category:
Streaming
Target version:
-
Start date:
2015-07-06
Due date:
% Done:

0%

Estimated time:
Found in version:
HTS Tvheadend 4.1-167~g5cc3717
Affected Versions:

Description

I use a m3u playlist with TVH streams to watch TV on some Kodi devices. I use a m3u file, so I do not have to enable the complete LiveTV functionality in Kodi.

When I open an item from this m3u file, e.g.
#EXTINF:-1,4 - RTL 4
http://192.168.1.97:9981/stream/channelid/693426109?ticket=60CEC06F628CE5D8E5BC9B1E91173F46DBA2C251&profile=pass

It takes a long time to open the stream, after about 4 seconds it does open and plays fine. In the TVH log I can see that it tries to open the stream multiple times and closes all but one.
When I load this .m3u file in VLC and start the same channel it starts within a second and I can see in the TVH log that it only subscribes once. When I open this stream from the LiveTV section in Kodi (on the same Kodi installation) the stream starts immediately with only one subscription.

I filed this issue in the Kodi forum, see
http://forum.kodi.tv/showthread.php?tid=231271

There it was pointed out that the stream that starts is broken and is missing metadata (e.g. resolution info). Therefore I am posting the issue here.

Debug logs from both TVHeadend and Kodi are attached.


Files

History

#1

Updated by Jaroslav Kysela about 6 years ago

  • Status changed from New to Invalid

Try to use the matroska muxer. The 'pass' profile is pass-through - what's received from the DVB receiver, it's passed to the client. It seems that kodi does not like it.

The metadata statements are not relevant for MPEG-TS. The clients must detect/parse the metadata in the MPEG-TS stream.

#2

Updated by Sam Stenvall about 6 years ago

@perexg shouldn't the video sent be valid anyway, regardless of which profile is used? If you look at the Kodi log ffmpeg can't handle the stream properly at all which is why it takes a long time to start.

#3

Updated by Mr. Blond about 6 years ago

Jaroslav Kysela wrote:

Try to use the matroska muxer. The 'pass' profile is pass-through - what's received from the DVB receiver, it's passed to the client. It seems that kodi does not like it.

The metadata statements are not relevant for MPEG-TS. The clients must detect/parse the metadata in the MPEG-TS stream.

Thanks guys, I changed the profile to matroska and now it loads as fast in Kodi as in VLC. However, I still see 3 subscriptions when I start in Kodi (and two immediate unsubscriptions). The do not occur in VLC. So there is still something wrong I guess.

See attached Kodi and TVH log.

#4

Updated by Jaroslav Kysela about 6 years ago

  • Parent task set to #2999

I think that TVH wrongly sends data after HEAD requests (only mime type should be returned). I'll check...

Sam Moosavi: The client is responsible to wait for the video/audio start in the case of MPEG-TS . Looking to logs:

DEBUG: ffmpeg[11395A000]: [mpegts] max_analyze_duration 500000 reached at 504000 microseconds

Do you see the issue ? I saw the video/audio difference up to 1.5 seconds in DVB streams also the key frames might use this time period. FFMPEG just does not handle this correctly with the default settings. It should be fixed in the kodi (set this "probe" interval to 2 seconds or so)... The 1/2 of a second is not enough.

Also available in: Atom PDF