Beiträge von sycolth
-
-
See here https://github.com/xteve-project/…play-the-stream
Threadfin is no longer involved, the client connects directly to the streaming server. -> That's the problem!Thanks, I know that with xteve involved and doing the streaming it works, but I was wondering if ffmpeg parameters can be passed to telerising to use its proxy feature instead of xteve.
-
then something else is wrong, telerising is on 192.168.0.200:5000, and if I browse to it and login I can open the web player and stream just fine.
But plex doesn't work, the logs from xteve say this:
Code2025/06/23 21:56:48 [Threadfin] Buffer: false [-] 2025/06/23 21:56:48 [Threadfin] Channel Name: ITAL1HD 2025/06/23 21:56:48 [Threadfin] Client User-Agent: Lavf/LIBAVFORMAT_VERSION 2025/06/23 21:56:48 [Threadfin] Streaming URL: http://192.168.0.200:5000/api/tby/live/344.m3u8 2025/06/23 21:56:48 [Threadfin] Streaming Info: URL was passed to the client. 2025/06/23 21:56:48 [Threadfin] Streaming Info: Threadfin is no longer involved, the client connects directly to the streaming server.
so I know the plex server is receiving the correct url, but it still fails with the message Could not tune channel. Please check your tuner or antenna.
One thing I had to do to make it work with liveproxy, was to pass extra parameters to ffmpeg.Can I do that in telerising and pass -copyts -f mpegts to ffmpeg, or is some other application doing the proxy?
-
Hi, I have a question about the proxy feature.
Should it work when using the m3u8 list, or is it only for the built in web player??
My current setup is:
Codedocker openvpn - docker telerising with --net over the vpn - docker liveproxy with --net over the vpn - xteve - plex
this is because i need the stream to be over the vpn.
Today I saw telerising has a proxy feature, so i enabled it, turned off liveproxy, reconfigured xteve and plex from scratch.
But streams fail to start.
Is there anyone with a similar setup that could help me figure it out?
Thanks