-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add control over multiple codec streaming to the device profile #9016
base: release-10.8.z
Are you sure you want to change the base?
Conversation
Changes in OpenAPI specification found. Expand to see details.What's Changed
|
d09900a
to
2fb9c91
Compare
}; | ||
|
||
return await _dynamicHlsHelper.GetMasterHlsPlaylist(TranscodingJobType.Hls, dynamicHlsRequestDto, true) | ||
return await _dynamicHlsHelper.GetMasterHlsPlaylist(TranscodingJobType.Hls, dynamicHlsRequestDto, true, true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The device profile is ignored here.
Using this flag we can disable unnecessary (for some clients) backward compatibility streams.
In fact, this block doesn't work.
All streams in the master playlist are bound to the same
PlaySessionId
.The server starts the transcoding process after receiving a request (middle bitrate or lower) from the device.
After sufficient buffering, the device requests a higher bitrate.
Since the
PlaySessionId
is the same, it seems that the transcoding job doesn't restart with the new parameters.Adaptive bitrate streaming probably doesn't work either.
Changes
Add the
EnableMultipleCodecStreaming
flag to the device profile to control multiple codec streamingIssues
jellyfin/jellyfin-tizen#163
#5576
jellyfin/jellyfin-webos#105
jellyfin/jellyfin-web#1190
jellyfin/jellyfin-webos#59