Codec initialization may fail in creation, configuration or when start()ing the codec. If codec initialization fails, there may be other codecs available that could handle the same format, but currently ExoPlayer can only try to use the first listed codec for the input format and gives up if it fails to initialize. This change implements support for optionally falling back to alternative decoders if initialization fails. MediaCodecSelector can now return a list of decoders to try in priority order, and use the Format when choosing a codec. With the default implementation, the codecs and order come from MediaCodecList, and matches the order used internally by MediaCodec.createDecoderByType (which implements the same kind of fallback though only to the creation step, without configuring/starting the codec). This feature is useful for apps that want to play several videos concurrently on devices that have software decoders (like OMX.google.h264.decoder), as the new behavior allows new codecs to be created when no hardware-accelerated decoders are available. The list of available codecs is queried when initializing the codec after a format change that requires a new codec to be instantiated. When a decoder fails to initialize it is removed from the list of available decoders and won't be tried again until the next format change (or until the renderer is disabled). Note: this change does not affect the renderer capabilities API, as when checking format support we don't know which codec will be used. Issue: #273 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=203242285 |
||
|---|---|---|
| demos | ||
| extensions | ||
| gradle/wrapper | ||
| library | ||
| playbacktests | ||
| testutils | ||
| testutils_robolectric | ||
| .gitignore | ||
| .hgignore | ||
| build.gradle | ||
| constants.gradle | ||
| CONTRIBUTING.md | ||
| core_settings.gradle | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| ISSUE_TEMPLATE | ||
| javadoc_combined.gradle | ||
| javadoc_library.gradle | ||
| javadoc_util.gradle | ||
| LICENSE | ||
| publish.gradle | ||
| README.md | ||
| RELEASENOTES.md | ||
| settings.gradle | ||
ExoPlayer
ExoPlayer is an application level media player for Android. It provides an alternative to Android’s MediaPlayer API for playing audio and video both locally and over the Internet. ExoPlayer supports features not currently supported by Android’s MediaPlayer API, including DASH and SmoothStreaming adaptive playbacks. Unlike the MediaPlayer API, ExoPlayer is easy to customize and extend, and can be updated through Play Store application updates.
Documentation
- The developer guide provides a wealth of information.
- The class reference documents ExoPlayer classes.
- The release notes document the major changes in each release.
- Follow our developer blog to keep up to date with the latest ExoPlayer developments!
Using ExoPlayer
ExoPlayer modules can be obtained from JCenter. It's also possible to clone the repository and depend on the modules locally.
From JCenter
The easiest way to get started using ExoPlayer is to add it as a gradle
dependency. You need to make sure you have the JCenter and Google repositories
included in the build.gradle file in the root of your project:
repositories {
jcenter()
google()
}
Next add a dependency in the build.gradle file of your app module. The
following will add a dependency to the full library:
implementation 'com.google.android.exoplayer:exoplayer:2.X.X'
where 2.X.X is your preferred version. Alternatively, you can depend on only
the library modules that you actually need. For example the following will add
dependencies on the Core, DASH and UI library modules, as might be required for
an app that plays DASH content:
implementation 'com.google.android.exoplayer:exoplayer-core:2.X.X'
implementation 'com.google.android.exoplayer:exoplayer-dash:2.X.X'
implementation 'com.google.android.exoplayer:exoplayer-ui:2.X.X'
The available library modules are listed below. Adding a dependency to the full library is equivalent to adding dependencies on all of the library modules individually.
exoplayer-core: Core functionality (required).exoplayer-dash: Support for DASH content.exoplayer-hls: Support for HLS content.exoplayer-smoothstreaming: Support for SmoothStreaming content.exoplayer-ui: UI components and resources for use with ExoPlayer.
In addition to library modules, ExoPlayer has multiple extension modules that depend on external libraries to provide additional functionality. Some extensions are available from JCenter, whereas others must be built manually. Browse the extensions directory and their individual READMEs for details.
More information on the library and extension modules that are available from JCenter can be found on Bintray.
Locally
Cloning the repository and depending on the modules locally is required when using some ExoPlayer extension modules. It's also a suitable approach if you want to make local changes to ExoPlayer, or if you want to use a development branch.
First, clone the repository into a local directory and checkout the desired branch:
git clone https://github.com/google/ExoPlayer.git
git checkout release-v2
Next, add the following to your project's settings.gradle file, replacing
path/to/exoplayer with the path to your local copy:
gradle.ext.exoplayerRoot = 'path/to/exoplayer'
gradle.ext.exoplayerModulePrefix = 'exoplayer-'
apply from: new File(gradle.ext.exoplayerRoot, 'core_settings.gradle')
You should now see the ExoPlayer modules appear as part of your project. You can depend on them as you would on any other local module, for example:
implementation project(':exoplayer-library-core')
implementation project(':exoplayer-library-dash')
implementation project(':exoplayer-library-ui')
Developing ExoPlayer
Project branches
- Development work happens on the
dev-v2branch. Pull requests should normally be made to this branch. - The
release-v2branch holds the most recent release.
Using Android Studio
To develop ExoPlayer using Android Studio, simply open the ExoPlayer project in the root directory of the repository.