No description
Find a file
andrewlewis c37f757854 Allow playback for ads buffered to end
`ImaAdsLoader` only loads ad media URLs once playback of the preceding ad (if
any) has started, and this behavior is likely to be similar for other ad loader
implementations due to limits on how long before an ad plays it is meant to be
loaded. This is problematic for very short ads followed by an ad because the ad
will load to the end but load control may not allow playback to start due to
the total buffered duration being low.

Fix this by allowing playback to start regardless of load control if we are
waiting for an ad media period to prepare.

An alternative fix would be to fake the ad progress in the `ImaAdsLoader` to
trigger loading the next ad, but this would only allow one ad to load ahead (so
the problem would remain for two short ads in a row followed by another ad).

Issue: #8492
PiperOrigin-RevId: 353600088
2021-01-25 15:36:39 +00:00
.github/ISSUE_TEMPLATE Make issue templates shorter 2020-12-14 10:14:03 +00:00
.idea Disable automatic imports for inner classes 2018-07-26 18:27:46 +01:00
demos Clarify how cookies are handled (or not) in the demo app 2021-01-11 18:04:53 +00:00
extensions Add contract test for CronetDataSource 2021-01-25 15:35:59 +00:00
gradle/wrapper Update Gradle plugins. 2020-05-01 19:48:32 +01:00
library Allow playback for ads buffered to end 2021-01-25 15:36:39 +00:00
playbacktests Re-add the v22 and v29 test targets 2021-01-13 00:04:06 +00:00
robolectricutils Use Clock to create Handler for delivering messages. 2021-01-22 16:21:44 +00:00
testdata Add WAV playback tests. 2021-01-22 16:20:44 +00:00
testutils Add contract test for CronetDataSource 2021-01-25 15:35:59 +00:00
.gitignore Add missing AV1 extension path to .gitignore 2020-01-30 19:31:15 +00:00
.hgignore Simplify the av1 extension build system 2020-08-01 12:55:36 +01:00
build.gradle Move Robolectric snapshot repository config to common_library_config 2020-12-14 10:18:53 +00:00
common_library_config.gradle Update Robolectric dependency from 4.5-SNAPSHOT to 4.5-alpha-3 2020-12-17 11:25:54 +00:00
constants.gradle Bump version to 2.12.3 2021-01-11 18:06:04 +00:00
CONTRIBUTING.md Clarify contribution branch 2018-11-23 17:41:06 +00:00
core_settings.gradle Publish transformer module 2021-01-22 17:13:47 +00:00
gradle.properties Upgrade gradle plugin to 3.6.0 2020-03-10 10:19:11 +00:00
gradlew Initial drop. 1.0.10. 2014-06-16 12:56:04 +01:00
gradlew.bat Cleanup following #884 2015-10-27 21:03:16 +00:00
javadoc_combined.gradle Add Guava dependency to ExoPlayer 2020-05-21 17:08:33 +01:00
javadoc_library.gradle Misc analysis fixes 2020-07-13 14:04:29 +01:00
javadoc_util.gradle Make javadoc links point to Android docs for java.* classes 2020-04-01 22:38:01 +01:00
LICENSE Initial drop. 1.0.10. 2014-06-16 12:56:04 +01:00
publish.gradle Add missing file header 2019-07-14 16:23:39 +01:00
README.md Add version to README 2020-08-26 16:40:23 +01:00
RELEASENOTES.md Allow playback for ads buffered to end 2021-01-25 15:36:39 +00:00
settings.gradle Add GL demo app 2020-02-11 17:08:53 +00:00

ExoPlayer

ExoPlayer is an application level media player for Android. It provides an alternative to Androids MediaPlayer API for playing audio and video both locally and over the Internet. ExoPlayer supports features not currently supported by Androids 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

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

1. Add repositories

The easiest way to get started using ExoPlayer is to add it as a gradle dependency. You need to make sure you have the Google and JCenter repositories included in the build.gradle file in the root of your project:

repositories {
    google()
    jcenter()
}

2. Add ExoPlayer module dependencies

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.

As an alternative to the full library, 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.

3. Turn on Java 8 support

If not enabled already, you also need to turn on Java 8 support in all build.gradle files depending on ExoPlayer, by adding the following to the android section:

compileOptions {
  targetCompatibility JavaVersion.VERSION_1_8
}

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
cd ExoPlayer
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-v2 branch. Pull requests should normally be made to this branch.
  • The release-v2 branch 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.