Any idea on how to share streams when using TS and HLS types simultaneously #458
Replies: 2 comments 1 reply
-
|
@Olivier6767 sorry I did not see this question. Sharing with HLS is not possible, The reason is that the client decides which stream he requests. HLS is made for selecting from a bunch of different qualities based on current bandwith capacity. This can differe from client to client. The second reason is that HLS streams are valud for a short time like for example 6 seconds. This means after 6 seconds the client disconnects and wait until his buffer has a little capacity left to make another request based on the current bandwidth. Sharing with ts works if you enable it, you need to enable stream sharing. However in you case you have 2 different targets. Sharing between two targets is currently not possible. I will add this as a feature request,
This could be a new feature request. |
Beta Was this translation helpful? Give feedback.
-
|
Sharing between targets is in the release |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using an Xtream provider as input, and I a have a limit of 2 simultaneous connections.
My provider's stream formats are:
TS:
http://<DOMAIN>/<USER>/<PASSWORD/<STREAM_ID>HLS:
http://<DOMAIN>/live/<USER>/<PASSWORD/<STREAM_ID>.m3u8I'm using player applications that work well with TS streams.
I'm also using a Web Player that only works with HLS streams.
For TS streams, I've configured an input of type XTREAM with the following options:
For HLS streams, I've configured an input of type XTREAM with the following options:
I've also configured 2 targets, each with a filter to select the channels of the corresponding input.
In the api-proxy.yml, I've configured 2 users, each pointing to one of the targets.
This setup works, but the channels are not shared between the 2 users. Even if watching the same channel, TP makes 2 connections to the provider.
Is there any way to get this done?
Would it be possible have an option where the setting
xtream_live_stream_use_prefixwould not forcefully add or remove the 'live' prefix, but keep what the client sends in the STREAM_URL ?Beta Was this translation helpful? Give feedback.
All reactions