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

History

olly f758082d40 Big (and hopefully near-final) rename.

1. Rename "extensions" package to "decoder". It's used by both
   text and (should be used by) metadata, so it's no longer just
   for extensions.
2. Move Buffer objects move into the decoder package.
3. Rename SubtitleParser and MetadataParser to SubtitleDecoder
   and MetadataDecoder respectively, since they extend Decoder.
   Ditto for all subclasses.
4. Subtitle and Metadata decoders now throw their own exception
   types rather than ParserException.
5. Move MediaCodec classes into a mediacodec package, with the
   exception of the concrete audio and video renderers.
6. Create an audio package to hold the two audio renderer classes
   plus related util classes.
7. Create a video package to hold the one video renderer class
   plus related util classes.

After this change the following nice properties hold:

1. Want a video renderer? Look in the video package. Ditto for
   audio, text and metadata.
2. All TrackRenderer implementations use a decoder of some kind
   to decode buffers received from the source, so we have
   consistent terminology there.
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=127326805

2016-07-15 18:14:55 +01:00

src

Big (and hopefully near-final) rename.

2016-07-15 18:14:55 +01:00

build.gradle

Finalize v2 directory + package name

2016-07-08 12:12:09 +01:00

README.md

Rename TrackRenderer -> Renderer

2016-07-15 18:00:32 +01: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

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.