Fixed
Status Update
Comments
sh...@gmail.com <sh...@gmail.com> #2
Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.
le...@google.com <le...@google.com>
ap...@google.com <ap...@google.com> #3
Great! Thanks a lot, I'll look for the live updates soon!
le...@google.com <le...@google.com>
pr...@google.com <pr...@google.com> #4
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.camera:camera-core:1.5.0-alpha05
androidx.camera:camera-video:1.5.0-alpha05
Description
As described in the post , application may want to know the quality that a QualitySelector will result in with specific use case combination/configuration.
Normally for specific feature, the use case combination won't change, which means a QualitySelector will always result in the same quality when the use cases are bound. So instead of a QualitySelector instance, it could be helpful to provide the actual selected quality through VideoCapture.