mirror of https://github.com/androidx/media.git synced 2025-04-30 06:46:50 +08:00

History

olly 035fab225d Rename skipToKeyframeBefore -> skipData and allow skipping to EOS

This change also ensures that format changes are read whilst the
renderer is enabled but without a codec. This is necessary to
ensure the drm session is updated (or replaced).

Updating the format is also needed so that the up-to-date format is
used in the case that the codec is initialized later due to the
surface being set. Previously, if an ABR change occurred between
the format being read and the surface being attached, we would
instantiate the codec and then immediately have to reconfigure it
when as a result of reading the up-to-date format. For a non-adaptive
codec this resulted in the codec being immediately released and
instantiated again!

Issue: #2582

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=151608096

2017-03-31 19:11:08 +01:00

src

Rename skipToKeyframeBefore -> skipData and allow skipping to EOS

2017-03-31 19:11:08 +01:00

build.gradle

Generate combined Javadoc

2017-03-22 19:11:28 +00:00

proguard-rules.txt

Fix gradle/proguard setup

2017-01-13 17:27:25 +00:00

README.md

extensions/vp9: Fix open source build scripts

2017-03-15 18:51:10 +00:00

README.md

ExoPlayer VP9 Extension

Description

The VP9 Extension is a Renderer implementation that helps you bundle libvpx (the VP9 decoding library) into your app and use it along with ExoPlayer to play VP9 video on Android devices.

Build Instructions

Checkout ExoPlayer along with Extensions:

git clone https://github.com/google/ExoPlayer.git

Set the following environment variables:

cd "<path to exoplayer checkout>"
EXOPLAYER_ROOT="$(pwd)"
VP9_EXT_PATH="${EXOPLAYER_ROOT}/extensions/vp9/src/main"

Download the Android NDK and set its location in an environment variable:

NDK_PATH="<path to Android NDK>"

Fetch libvpx and libyuv:

cd "${VP9_EXT_PATH}/jni" && \
git clone https://chromium.googlesource.com/webm/libvpx libvpx && \
git clone https://chromium.googlesource.com/libyuv/libyuv libyuv

Checkout the appropriate branches of libvpx and libyuv (the scripts and makefiles bundled in this repo are known to work only at these versions of the libraries - we will update this periodically as newer versions of libvpx/libyuv are released):

cd "${VP9_EXT_PATH}/jni/libvpx" && \
git checkout tags/v1.6.1 -b v1.6.1 && \
cd "${VP9_EXT_PATH}/jni/libyuv" && \
git checkout e2611a73

Run a script that generates necessary configuration files for libvpx:

cd ${VP9_EXT_PATH}/jni && \
./generate_libvpx_android_configs.sh "${NDK_PATH}"

Build the JNI native libraries from the command line:

cd "${VP9_EXT_PATH}"/jni && \
${NDK_PATH}/ndk-build APP_ABI=all -j4

In your project, you can add a dependency to the VP9 Extension by using a the following rule:

// in settings.gradle
include ':..:ExoPlayer:library'
include ':..:ExoPlayer:extension-vp9'

// in build.gradle
dependencies {
    compile project(':..:ExoPlayer:library')
    compile project(':..:ExoPlayer:extension-vp9')
}

Now, when you build your app, the VP9 extension will be built and the native libraries will be packaged along with the APK.

Notes

Every time there is a change to the libvpx checkout:
- Android config scripts should be re-generated by running generate_libvpx_android_configs.sh
- Clean and re-build the project.
If you want to use your own version of libvpx or libyuv, place it in ${VP9_EXT_PATH}/jni/libvpx or ${VP9_EXT_PATH}/jni/libyuv respectively. But please note that generate_libvpx_android_configs.sh and the makefiles need to be modified to work with arbitrary versions of libvpx and libyuv.