session: deprecate options for spec. stream types #3893
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having multiple session options and CLI arguments for different stream
types which are already covered by generic options/arguments is not only
redundant, but also confusing.
A distinction between different stream types does only make sense when
multiple different stream types are available and the user needs to
explicitly set different values for each of them, but since it's not
always clear which stream type is returned when a stream is selected
via the "best" stream name synonym for example, this makes it even more
confusing. And it's redundant as well, since only one stream can be
selected anyway.
{dash,hds,hls}-segment-attempts
in favor of
stream-segment-attempts
{dash,hds,hls}-segment-threads
in favor of
stream-segment-threads
{dash,hds,hls}-segment-timeout
in favor of
stream-segment-timeout
{dash,hds,hls,rtmp,http-stream}-timeout
in favor of
stream-timeout
(dash/http-stream were never used)HTTPStream
and usestream-timeout
instead ofhttp-timeout
hls-segment-stream-data
should be removed as well and just set toTrue
. In a separate PR.