-
Notifications
You must be signed in to change notification settings - Fork 6k
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
getMetrics usage for MediaCodecAdapter #9766
Labels
Comments
hi christosts, Any update on the usage? |
We will add getMetric() on MediaCodecAdapter - I will post an update once the commit is submitted. |
christosts
added a commit
that referenced
this issue
Dec 15, 2021
Before the introduction of the MediaCodecAdapter, users could get access directly to the MediaCodec instance from MediaCodecRenderer.getCodec() and then retrieve the codec metrics. This change exposes MediaCodec.getMetrics() on the MediaCodecAdapter. Issue: #9766 #minor-release PiperOrigin-RevId: 416343023
Please see the commit linked above - the API will be available on the next release |
thank you |
tonihei
pushed a commit
to androidx/media
that referenced
this issue
Jan 5, 2022
Before the introduction of the MediaCodecAdapter, users could get access directly to the MediaCodec instance from MediaCodecRenderer.getCodec() and then retrieve the codec metrics. This change exposes MediaCodec.getMetrics() on the MediaCodecAdapter. Issue: google/ExoPlayer#9766 #minor-release PiperOrigin-RevId: 416343023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
is the api getMetrics() supported with the new MediaCodecAdapter in exoplayer library 2.15.1 or newer
I have been using the getMetrics() api to retrieve information like Encoder/Decoder/Ht/Width and other information for the codec created. But in the new library, we migrated to using MediaCodecAdapter instead of MediaCodec. I do not see the getMetrics api supported for this? Is this something that will be added in future versions or is there a different approach for usage of this api.
The text was updated successfully, but these errors were encountered: