enerdude

> Testbuilds: https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/1/artifacts Thanks, will test and let you know

Ok seems to work fine. What I tried: #EXTINF:-1,Example HLS stream #KODIPROP:inputstream=inputstream.ffmpegdirect #KODIPROP:mimetype=application/vnd.apple.mpegurl #KODIPROP:inputstream.ffmpegdirect.manifest_type=hls #KODIPROP:inputstream.ffmpegdirect.http_proxy_host=127.0.0.1 #KODIPROP:inputstream.ffmpegdirect.http_proxy_port=8081 https://example.com/index.m3u8 using latest Kodi 22 nightly build using the above ffmpegdirect you compiled. I...

> Nope, it should work wth the `|` already. No it does not, tried it again. It adds a header to the request like this: http_proxy: http://127.0.0.1:8081 where 127.0.0.1:8081 is...

> Ok, can you try these testbuilds and see if it works via a `|`? > > https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/3/artifacts Ok should I test like this? http://www.somewhere.com/playlist.m3u8|http_proxy=http://127.0.0.1:8080

> So it doesn’t use the proxy at all and just adds a header instead? > > what’s wrong with using the kodiprops? I guess nothing. I was also wondering...what...

> Ok should I test like this? > > [http://www.somewhere.com/playlist.m3u8|http_proxy=http://127.0.0.1:8080](http://www.somewhere.com/playlist.m3u8%7Chttp_proxy=http://127.0.0.1:8080) I tested this way as well as changing it to httpproxy but both are still added as headers. Like I...

> https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/6/artifacts I'm getting a blank page without download links

Ok so different results depending on #KODIPROPS: With this: #EXTINF:-1,Video test (test Kodi 22 pipe) #KODIPROP:inputstream=inputstream.ffmpegdirect #KODIPROP:mimetype=application/vnd.apple.mpegurl #KODIPROP:inputstream.ffmpegdirect.manifest_type=hls https://example.com/index.m3u8|http_proxy=http://127.0.0.1:8081&Referer=https://example.xyz proxy works fine but when I stop the stream it makes...

In between my analysis of the proxy setting I saw lots of "ping" requests e.g. https://jenkins.kodi.tv/sse-gateway/ping with a Referer of https://jenkins.kodi.tv/blue/organizations/jenkins/xbmc%2Finputstream.ffmpegdirect/detail/PR-310/5/artifacts/ I guess these background requests is normal for testing...

> only the first example you gave is valid for ffmpegdirect. At a minimum those 3 props must be set for any ffmpegdirect call Ok but why does Kodi usually...