9c27cfcda7
The dokka javadoc generation tool complains when parameter names don't match between a method and its override. This change updates occurrences where there is currently a mismatch. Notable renamings that might be controversial: - `onPlaybackStateChanged(int state)` to `onPlaybackStateChanged(int playbackState)` affected a lot of lines but seems more consistent with other '-Changed' methods. - `handleMessage(int messageType, Object payload)` to `handleMessage(int messageType, Object message)` - `ExtractorInput` and `DataSource` inherit `DataReader` which had `read(byte[] target, ...`, while data sources normally called the first parameter `buffer`. I have standardized these all to use `buffer` even though it looks out of place in the `ExtractorInput` interface (which has more `read` methods with `target`). PiperOrigin-RevId: 387290360
ExoPlayer RTMP extension
The RTMP extension is a DataSource implementation for playing RTMP streams using LibRtmp Client for Android.
License note
Please note that whilst the code in this repository is licensed under Apache 2.0, using this extension requires depending on LibRtmp Client for Android, which is licensed separately.
Getting the extension
The easiest way to use the extension is to add it as a gradle dependency:
implementation 'com.google.android.exoplayer:extension-rtmp:2.X.X'
where 2.X.X is the version, which must match the version of the ExoPlayer
library being used.
Alternatively, you can clone the ExoPlayer repository and depend on the module locally. Instructions for doing this can be found in ExoPlayer's top level README.
Using the extension
ExoPlayer requests data through DataSource instances. These instances are
obtained from instances of DataSource.Factory, which are instantiated and
injected from application code.
DefaultDataSource will automatically use the RTMP extension whenever it's
available. Hence if your application is using DefaultDataSource or
DefaultDataSourceFactory, adding support for RTMP streams is as simple as
adding a dependency to the RTMP extension as described above. No changes to your
application code are required. Alternatively, if you know that your application
doesn't need to handle any other protocols, you can update any
DataSource.Factory instantiations in your application code to use
RtmpDataSource.Factory directly.
Links
- Javadoc: Classes matching
com.google.android.exoplayer2.ext.rtmp.*belong to this module.