loliball/media
1
0
Fork 0
mirror of https://github.com/androidx/media.git synced 2025-04-29 22:36:54 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
media/libraries/decoder_iamf
History
tonihei 766dbd497e Add util to obtain AudioManager 
AudioManager internally assumes the thread is was created on can be
used as a callback thread. Since the AudioManager is only created
once in the lifetime of an app, we need to make sure its obtained
on a thread that stays alive.

#cherrypick

PiperOrigin-RevId: 732072255
(cherry picked from commit 2088697a19ac85feb26ba2521a70647803246571)
2025-03-03 16:27:28 +00:00
..
src
Add util to obtain AudioManager
2025-03-03 16:27:28 +00:00
build.gradle
Switch most intra-lib deps from implementation to api
2025-02-12 11:29:50 -08:00
proguard-rules.txt
Make minor improvements for IAMF decoder module
2024-10-24 04:46:13 -07:00
README.md
Simplify IAMF extension build process
2024-10-10 09:32:25 -07:00

README.md

IAMF decoder module

The IAMF module provides LibiamfAudioRenderer, which uses the libiamf native library to decode IAMF audio.

License note

Please note that whilst the code in this repository is licensed under Apache 2.0, using this module also requires building and including one or more external libraries as described below. These are licensed separately.

Build instructions (Linux, macOS)

To use the module you need to clone this GitHub project and depend on its modules locally. Instructions for doing this can be found in the top level README.

In addition, it's necessary to fetch libiamf as follows:

  • Set the following environment variables:
cd "<path to project checkout>"
IAMF_MODULE_PATH="$(pwd)/libraries/decoder_iamf/src/main"
  • Fetch libiamf:
cd "${IAMF_MODULE_PATH}/jni" && \
git clone https://github.com/AOMediaCodec/libiamf.git

Having followed these steps, gradle will build the module automatically when run on the command line or via Android Studio, using CMake and Ninja to configure and build libiamf and the module's JNI wrapper library.

Build instructions (Windows)

We do not provide support for building this module on Windows, however it should be possible to follow the Linux instructions in Windows PowerShell.

Using the module with ExoPlayer

Once you've followed the instructions above to check out, build and depend on the module, the next step is to tell ExoPlayer to use LibiamfAudioRenderer. How you do this depends on which player API you're using:

  • If you're passing a DefaultRenderersFactory to ExoPlayer.Builder, you can enable using the module by setting the extensionRendererMode parameter of the DefaultRenderersFactory constructor to EXTENSION_RENDERER_MODE_ON. This will use LibiamfAudioRenderer for playback if MediaCodecAudioRenderer doesn't support the input format. Pass EXTENSION_RENDERER_MODE_PREFER to give LibiamfAudioRenderer priority over MediaCodecAudioRenderer.
  • If you've subclassed DefaultRenderersFactory, add a LibiamfAudioRenderer to the output list in buildAudioRenderers. ExoPlayer will use the first Renderer in the list that supports the input media format.
  • If you've implemented your own RenderersFactory, return a LibiamfAudioRenderer instance from createRenderers. ExoPlayer will use the first Renderer in the returned array that supports the input media format.
  • If you're using ExoPlayer.Builder, pass a LibiamfAudioRenderer in the array of Renderers. ExoPlayer will use the first Renderer in the list that supports the input media format.

Note: These instructions assume you're using DefaultTrackSelector. If you have a custom track selector the choice of Renderer is up to your implementation, so you need to make sure you are passing a LibiamfAudioRenderer to the player, then implement your own logic to use the renderer for a given track.

Links