[Jeronimo17]

Hi, is it possible to ignore the content-length header or activate some option for it? as is done with Curl with --ignore-content-length or --http-continuous in VLC, because I think Kodi uses Curl.

My server sends a false Content-Length header: 2624204796, when it reaches that download the stream stops, this happens on the PC if I don't add the headers I think that on Kodi it cuts me off for that too

Thank you

[phunkyfish]

What type of http stream is it?

[Jeronimo17]

What type of http stream is it?

M3u list of http url ... .ts that I created from a sat receiver

[Jeronimo17]

[Jeronimo17]

I understand that there is no way to do it right now, right? Either with the PVR or directly on Kodi.

I have tried creating a server with nc in linux with the false header of Content-Length and pure Kodi and also IPTV Simple Client cuts according to this data, I have read that it is common for this data to be wrong also in video internet servers


Thank you

PS: Can't edit the posts?

[phunkyfish]

I don’t think there is a way to do this currently. Why not contact your sat ip provider and ask them about a fix?

I have never seen this issue raised before.

[Jeronimo17]

Why not contact your sat ip provider and ask them about a fix?

It's myself , I don't have a provider, it's a Freesat V8 at my parents' house connected by ssh tunnel between 2 routers, It is a problem with the satellite receiver, I have known the fault for a long time, it happens in the same local network.

But it is a common failure in streaming http servers, there should be an option at least in advanced settings, to add the option that Curl already incorporates

https://stackoverflow.com/questions/1292...gth-header


https://forum.kodi.tv/showthread.php?tid=199625
https://forum.kodi.tv/showthread.php?tid=293628
It also happens to me like here if I open the m3u with pure Kodi, it only works with <buffermode>3</buffermode> (deactivated) or better with IPTV Simple Client that ignores the above

How can I request the new feature?

Thank you so much

[emveepee]

This was always a problem with http streaming and PVR until v18 when GetStreamTimes solved it for pvr.nextpvr and others.  pvr.iptvsimple uses the basic inputstream though so it will continue to have the problem.

I suspect if you try with Matrix and use inputstream.ffmpegdirect URL's  pvr.iptvsimple will work.  If not another PVR backend like pvr.nextpvr with IPTV support will work.

Martin

[phunkyfish]

My next suggestion was to try ffmpegdirect. But you need to specify the mime type for TS streams.

Like this:

Code:

#KODIPROP:inputstream=inputstream.ffmpegdirect
#KODIPROP:mimetype=video/mp2t
#KODIPROP:inputstream.ffmpegdirect.is_realtime_stream=true
#EXTINF:-1,MyChannel
http://127.0.0.1:3002/mystream.ts

You can also the open_mode property to either ffmpeg or curl, e.g.

Code:

#KODIPROP:inputstream.ffmpegdirect.open_mode=ffmpeg

[Jeronimo17]

This was always a problem with http streaming and PVR until v18 when GetStreamTimes solved it for pvr.nextpvr and others.  pvr.iptvsimple uses the basic inputstream though so it will continue to have the problem.

I suspect if you try with Matrix and use inputstream.ffmpegdirect URL's  pvr.iptvsimple will work.  If not another PVR backend like pvr.nextpvr with IPTV support will work.

Martin

Pvr.nextpvr I don't see the option to enter M3U, the only one that supports M3U is IPTV Simple Client? I have tried all Inputstream.ffmpegdirect does not have the option to ignore the header, it keeps happening.

[emveepee]

Did you setup the m3u file will all the correct properties for pvr.iptvsimple it might require debug logs?

And sorry I wasn't clearer pvr.nextpvr will require a backend so if you are using Android as the client that might be difficult.

Martin

[Jeronimo17]

[emveepee]

What I meant is did you add all the required #KODIPROP values in the m3u?

Martin

[Jeronimo17]

What I meant is did you add all the required #KODIPROP values in the m3u?

Martin

Well, I don't know the KODIPROP values, does the --ignore-content-length exist?

[phunkyfish]

It be easier if you provide the M3U entry that you used to test it with inputstream.ffmpeg.