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 SmoothStreaming library module
Provides support for SmoothStreaming content.
Adding a dependency to this module is all that's required to enable playback of
SmoothStreaming MediaItems added to an ExoPlayer or SimpleExoPlayer in
their default configurations. Internally, DefaultMediaSourceFactory will
automatically detect the presence of the module and convert SmoothStreaming
MediaItems into SsMediaSource instances for playback.
Similarly, a DownloadManager in its default configuration will use
DefaultDownloaderFactory, which will automatically detect the presence of
the module and build SsDownloader instances to download SmoothStreaming
content.
For advanced playback use cases, applications can build SsMediaSource
instances and pass them directly to the player. For advanced download use cases,
SsDownloader can be used directly.
Links
- Developer Guide.
- Javadoc: Classes matching
com.google.android.exoplayer2.source.smoothstreaming.*belong to this module.