xbmc / xbmc/inputstream.ffmpegdirect
[Question] FFMPEG Flags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 101
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
I have a stream url that every once in a while disconnect and to be able to play it in mpv, I used this flags:
--stream-lavf-o-append=reconnect_on_http_error=4xx,5xx --stream-lavf-o-append=reconnect_delay_max=30 --stream-lavf-o-append=reconnect_streamed=yes --stream-lavf-o-append=reconnect_on_network_error=yes
I am trying to have this kind of setup in kodi. Is it possible to set these flags in kodiprops? I have seen this repo with the reconnect flags here https://github.com/kodi-pvr/pvr.iptvsimple?tab=readme-ov-file#http-header-fields-supported-by-kodi but I don't know how to set it properly. Below configurations are my hail mary attempt at trying to make it work
#KODIPROP:inputstream=inputstream.ffmpegdirect
#KODIPROP:mimetype=video/mp2t
#KODIPROP:reconnect_on_http_error=4xx,5xx
#KODIPROP:reconnect_delay_max=30
#KODIPROP:reconnect_streamed=yes
#KODIPROP:reconnect_on_network_error=yes
#EXTINF:-1, Channel 1
http://example.com
Can anyone provide a guide on how to do it properly or answer if it is not possible?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking how inputstream.ffmpegdirect handles the KODIPROP entries shown in the issue, then compare that behavior with the supported HTTP header fields documented in the linked pvr.iptvsimple guide. Confirm whether these FFmpeg reconnect options are exposed through Kodi properties; document the correct configuration if they are, or clearly state that the setup is unsupported.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100