Feature #4769
Add custom pipe-handler to IPTV networks
0%
Description
Woulb be nice if you could add a line in the IPTV and/or IPTV Automatic Network configuration, how a Mux-URL should be parsed, i.e.
Handler: ffmpeg -re -v error -i "%1" -vn -sn -acodec aac -b:a 224k -mpegts_service_type digital_radio -f mpegts pipe:1
(where %1 would be the mux-url as manually specified in the MUX or auto-playlist)
This would allow to directly use radio-playlists (which currently can only be handeled manually with lots of manual pipe:// muxes, related to https://tvheadend.org/issues/4768), other non-mpegts-playlists, or urls that can be played with streamlink...
Thanks,
/hp
History
#1
Updated by Jaroslav Kysela over 1 year ago
Updated by - Category changed from Muxers to IPTV
#2
Updated by Jaroslav Kysela over 1 year ago
- Target version set to 4.4
This would allow to directly use radio-playlists (which currently can only be handeled manually with lots of manual pipe:// muxes, related to https://tvheadend.org/issues/4768), other non-mpegts-playlists, or urls that can be played with streamlink...
Have you tried to turn on 'Use A/V library' in the network settings? But I got the idea..
#3
Updated by Andreas Fornberg over 1 year ago
Updated by This option would be nice to have.
#4
Updated by Hanspeter Müller over 1 year ago
Updated by Jaroslav Kysela wrote:
This would allow to directly use radio-playlists (which currently can only be handeled manually with lots of manual pipe:// muxes, related to https://tvheadend.org/issues/4768), other non-mpegts-playlists, or urls that can be played with streamlink...
Have you tried to turn on 'Use A/V library' in the network settings? But I got the idea..
Yeah, i have, it returns
iptv: libav: Could not open input 'http://stream.klassikradio.de/movie/mp3-192/www.klassikradio.de/': Invalid data found when processing input
My script currently does
ffmpeg -re -v error -i "$1" -vn -sn -acodec aac -b:a 224k -mpegts_service_type digital_radio -f mpegts pipe:1
and works fine...
but BTW, i've tried it with a pipe:// link, and got an error like "could not connect to URL pipe://.......", it looks like the "Use A/V lib" directly connects out, is this intentional/by design, that it only works on http-links? Or could you change that it instead is "chained" into the normal flow and could be used with all URL-Types that tvh can handle?
Combined with this FR it would be very usefull (i dont like to call ffmpeg inside my own scripts when tvh could do that iself, would probably be faster and more stable with one less binary started on every start)...
/hp