In ExoPlayer v2, the HlsMediaChunk class is responsible for constructing what extractor is required for a given format (createExtractor). This means that HLS handling is tightly coupled to what extractors are used.
Since applications are capable of creating their own extractors (e.g. their own TsExtractor) it would be useful to allow these to be passed into the HLS implementation to be used. This would require the HlsMediaSource accepting an extractor factory which could then be created by the application.
In ExoPlayer v2, the
HlsMediaChunkclass is responsible for constructing what extractor is required for a given format (createExtractor). This means that HLS handling is tightly coupled to what extractors are used.Since applications are capable of creating their own extractors (e.g. their own
TsExtractor) it would be useful to allow these to be passed into the HLS implementation to be used. This would require theHlsMediaSourceaccepting an extractor factory which could then be created by the application.