-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Wrong index returned for AbrController.getQualityForBitrate #841
Comments
@AkamaiDASH, looks like this code is a part of your implementation of fragment abandonment: |
lol... it's foggy @KozhinM . I think it was to handle something on the opposite end when the bitrate sent in is lower the the lowest listed bitrate but I can not remember. I look for some email and test it. let me get to a place where i can test but looking at it and from the description @davidgarry it seems wrong and a bug. I'll follow up in a bit. |
@AkamaiDASH, do you have some news about this issue ? |
Seems like a valid bug but no have not looked yet and most likely will not for a bit. We are in the middle of a huge refactor so I am not in my normal state to look closely. Maybe just fix the one line you pointed out the notes in your code branch and we will fix in the next release. It would be very helpful if you could add a detailed issue to the issue tracker as well. |
This is certainly a bug, simple fix committed on our branch as above, don't see the point creating a pull request while the refactor is ongoing, but let me know. |
This change did not make it up to 2.0 so I need to add bbc@6639326 |
Fixed and directly pushed into dev without a PR. |
HI everybody,
I have the following bitrates list :
When I call the method MediaPlayer.setQualityFor('video', 5), the process call the method getQualityForBitrate(mediaInfo, 2500), and it returns 4 instead of 5, due to the line :
return Math.max(i-1, 0);
In the block code below :
So, I can't set the quality to 2500. Is there a reason to send the previous index when bitrates are equals ?
Regards,
The text was updated successfully, but these errors were encountered: