Unable to play AC3 URL using ffmpeg extension even after compiling the ffmpeg extension successfully

[rishabh14augshukla]

Issue description

Unable to play AC3 URL using ffmpeg extension even after compiling the ffmpeg extension successfully.
I have successfully compiled the ffmpeg extension locally but when I am trying to play AC3 HLS URL. It is not calling FfmpegAudioRenderer.

Reproduction steps

I have followed all the instruction which is mentioned in the following link
https://github.com/google/ExoPlayer/tree/release-v2/extensions/ffmpeg
To setup ffmpeg extension locally and able to compile it locally successfully.

Also, set the extensionRendererMode parameter of the DefaultRenderersFactory constructor to EXTENSION_RENDERER_MODE_ON and EXTENSION_RENDERER_MODE_PREFER to give FfmpegAudioRenderer priority over MediaCodecAudioRenderer.

But still unable to hear the audio and able to play video.

Please let us know what we are missing here to play the AC3 URL or what we should suppose to do in terms of code changes.

Link to test content

https://www.hdpvrcapture.com/hdpvrcapture/samples/20090227_233850-H.264.m2ts.mp4

A full bug report captured from the device

We are only getting the toast message "Media includes audio track but none are playable by this device". We are not getting any error and exception.

Version of ExoPlayer being used

Using the latest version of the ExoPlayer v2.

Device(s) and version(s) of Android being used

Using the Samsung S7 and Nokia 8 devices they having the Android 8 and 9 version.

[ojw28]

That would normally indicate either that the extension is not being loaded correctly, or that FFmpeg was not compiled to include the AC3 decoder. Please:

• Attach or email (to dev.exoplayer@gmail.com) a full bug report captured using the ExoPlayer demo app shortly after an attempted playback. Such a bug report includes more useful information than you've provided.
• Please try attaching a debugger and adding logging and break points in FfmpegAudioRenderer.supportsFormatInternal. Establishing which return statement is executed will help to diagnose the problem.

@andrewlewis - Should we add some logging to FfmpegAudioRenderer.supportsFormatInternal (and similar methods in other renderers that are using bundled software codecs) to indicate what the problem is, to make debugging this type of issue simpler in future?

[ojw28]

@rishabh14augshukla - Did you try the suggestions above?

[andrewlewis]

Closing due to inactivity. The commits referenced above mean that we log more useful diagnostic information for some cases where the extension fails to initialize.