UnityPlugin-AVProVideo
UnityPlugin-AVProVideo copied to clipboard
RenderHeads
How to implement a video quality selector for HLS videos
I'd like to implement a feature to allow the user to select a desired video quality, like youtube does (see example) From the documentation is not obvious what are the functions to use to achieve it with AvPro.
- Given any HLS media url, how do I query the available stream information (resolution, framerate, bitrate)?
- How do I force AvPro to select a specific rendition, preventing it from automatically switching to lower/higher quality?
- How to tell AvPro reset the preference, and automatically detect the best rendition?
So I guess it's not possible to achieve this with the current AvPro features?
So I guess it's not possible to achieve this with the current AvPro features?
Not as things stand.
EDIT: Unless you change up your HLS manifest. Have each stream on it's own as well as an adaptive version.
It is likely that this feature would only be fully available on Android if implemented. Windows might be possible in a limited form, and apple platforms are a 'maybe'.
It is likely that this feature would only be fully available on Android if implemented. Windows might be possible in a limited form, and apple platforms are a 'maybe'.
One reason why we would like this feature it's because on Apple platform the HLS videos always seem to start from an arbitrary rendition, even if the preferred resolution is set to be 1080p. This happens on a fast wifi connection, and it's not really guaranteed that the video player will switch to the highest rendition. It looks bad when watching 320p videos on a fullscreen desktop
my post has been closed, Please help me confirm my response again (https://github.com/RenderHeads/UnityPlugin-AVProVideo/issues/1247)
I desperately need this, please assist me, thank you so much!!
my post has been closed, Please help me confirm my response again (#1247)
I desperately need this, please assist me, thank you so much!!
Is there an answer to this question
Will it be implemented in version 3.0? This is a very important feature for me.