You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A user would like to have the feature to set the HLS list size and HLS segment duration for each stream individually.
Currently, these can be configured Applications wise and therefore it is Application specific but the user would like to have this feature per stream basis.
Describe alternatives you've considered
I recommended using different applications to categories the streams with similar settings as a workaround solution but as per the user's use case, they need different seek back time for each stream.
The text was updated successfully, but these errors were encountered:
Mohit-3196
changed the title
Feature to set the HLS List size and Segment duration per stream basis.
Feature to set the HLS List size and Segment duration per stream basis Programmatically
Nov 2, 2023
This is coming from an AWS Marketplace cluster user.
They want to have an option in which they can control the seek back time for each stream and provide different timelines to their customers.
They expect to have 100 publishers per meeting and 200 meetings per day with 100 to 10K HLS viewers and use c5.24xlarge instances in their autoscaling cluster.
Is your feature request related to a problem? Please describe.
A user would like to have the feature to set the HLS list size and HLS segment duration for each stream individually.
Currently, these can be configured Applications wise and therefore it is Application specific but the user would like to have this feature per stream basis.
Describe alternatives you've considered
I recommended using different applications to categories the streams with similar settings as a workaround solution but as per the user's use case, they need different seek back time for each stream.
The text was updated successfully, but these errors were encountered: