-
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
MediaCodecAudioRender always wins over FfmpegAudioRenderer #2269
Comments
BTW, is it expected that decoders:
returns No issues with audio playback on NVidia shield. Should I create separate issue for it? |
By default, exoplayer will prefer to use native rather than extension renderers. You can pass a extensionRendererMode paramater to ExoPlayerFactory.newSimpleInstance() with a value of SimpleExoPlayer.EXTENSION_RENDERER_MODE_PREFER to have ExoPlayer prefer the extension.. |
This is expected behavior if both renderers are supported equally. For example both FORMAT_HANDLED or both FORMAT_EXCEEDS_CAPABILITIES But in described situation we compare "fully supported" vs "lacking proper support" where "lacking proper support" wins |
I think there's a one line bug (we're forgetting to mask the value here) that causes this. We'll push a fix shortly. Thanks! |
@ojw28 , thank you What about MediaCodecInfo.getMaxInputChannelCount() == 1 from nvidia/mediatek MediaCodec? is it expected behavior? |
I doubt it, particularly if you're seeing it work successfully with more channels. I suggest you report the issue directly to nVidia. |
With Nvidia it works with 2 channels pretty well. |
Issue: #2269 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=143433012
NVidia shield:
device decoder declares that it supports 1 channel only (btw, Philips, QM16XE_U, QM163E with OMX.MTK.AUDIO.DECODER.DSPMP1 does the same)
Please check
RendererCapabilities.supportsFormat
:MediaCodecAudioRender
returnsADAPTIVE_NOT_SEAMLESS | formatSupport
whileFfmpegAudioRenderer
returns justformatSupport
.It means that
FORMAT_EXCEEDS_CAPABILITIES
wins overFORMAT_HANDLED
which looks wrongThe text was updated successfully, but these errors were encountered: