- Applications should generally use DefaultMediaSourceFactory, or their own custom implementation if they need one. Having the media2 extension implement its own version directly doesn't seem that useful. - Remove support for CallbackMediaItem. This type of MediaItem doesn't go cross-process, and it seems like there would never be a use case where an app would need to generate one locally. If an app needs to provide data from a custom source, it should hook into ExoPlayer's way of doing this (i.e., use a UriMediaItem with a custom scheme, and inject a custom DataSource that can handle this scheme). PiperOrigin-RevId: 326914465
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| av1 | Loading commit data... | |
| cast | Loading commit data... | |
| cronet | Loading commit data... | |
| ffmpeg | Loading commit data... | |
| flac | Loading commit data... | |
| gvr | Loading commit data... | |
| ima | Loading commit data... | |
| jobdispatcher | Loading commit data... | |
| leanback | Loading commit data... | |
| media2 | Loading commit data... | |
| mediasession | Loading commit data... | |
| okhttp | Loading commit data... | |
| opus | Loading commit data... | |
| rtmp | Loading commit data... | |
| vp9 | Loading commit data... | |
| workmanager | Loading commit data... | |
| README.md | Loading commit data... |