media/libraries/exoplayer
tonihei b1c954fa84 Use routed device in AudioCapabilities
From API 23, we may have a preferred device that is most likely used
as the output device.
From API 24, the AudioTrack tells us the actual routed device that is
used for output and we can listen to changes happening mid-playback.
From API 33, we can directly query the default device that will
be used for audio output for the current attributes.

If the routed device is known by any of the methods above, we can add
more targeted checks in methods like isBluetoothConnected to avoid
iterating over all devices that are not relevant.

The knowledge about the routed device will also be useful to check
advanced output capabilities in the future (e.g. for lossless
playback)

PiperOrigin-RevId: 600384923
2024-01-22 01:40:50 -08:00
..
src Use routed device in AudioCapabilities 2024-01-22 01:40:50 -08:00
build.gradle Replace Queue<Long> with a queue for long primitives 2023-08-24 09:14:44 +01:00
proguard-rules.txt Rename FfmpegVideoRenderer to ExperimentalFfmpegVideoRenderer 2023-10-06 01:50:54 -07:00
README.md Fix javadoc links in media README files 2023-03-30 17:26:40 +00:00

ExoPlayer module

This module provides ExoPlayer, the Player implementation for local media playback on Android.

Getting the module

The easiest way to get the module is to add it as a gradle dependency:

implementation 'androidx.media3:media3-exoplayer:1.X.X'

where 1.X.X is the version, which must match the version of the other media modules being used.

Alternatively, you can clone this GitHub project and depend on the module locally. Instructions for doing this can be found in the top level README.