-
Notifications
You must be signed in to change notification settings - Fork 30
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
Allowing Configurable Simulcast Resolutions #156
Comments
We are currently enabling simulcast via SDP mangling in the sdk which doesn't support adjusting the resolutions. We have plans to move to enabling simulcast via the transceivers api but it is a low priority for now |
Understood, thanks for your response! |
Closing this issue, this should be handled server-side and reported to https://support.dolby.io/hc/en-au |
let's keep it open it is a good feature to add to the sdk. |
revisiting this to add a rooms feature for millicast. the send encodings on the transeiver worked for me without the need for munging. I don't use the SDK but my own peer library. But hard to automate such config it looks like this. instead of resolutions the others are scaled down by a factor. trying to figure out how the scalability mode works with this. https://electroteque.org/plugins/videojs/rtcstreaming/demos/millicast-simulcast/ |
Is your feature request related to a problem? Please describe.
By default while using the Publisher Simulcast feature, the client attempts to stream:
Instead of prioritizing multiple low quality videos, in some cases it would be more efficient to simulcast one high quality video and one low quality (for clients that have poor network or hardware conditions). For example:
Describe the solution you'd like
I would like to supply a configuration object during the Publish connect for simulcast instead of a boolean. This object could contain an array or resolutions to be targeted, with the SDKs current implementation as default (1920x1080, 960x540, 480x270).
The text was updated successfully, but these errors were encountered: