MediaSourceFactory for different content types combined with the dynamic stream links

[androidx]

MediaSourceFactory for different content types combined with the dynamic stream links

[icbaker]

However, this approach is not viable for us, since we're fetching the stream links dynamically (more on that here). So the url in MediaItem is not yet a valid one (it contains just information to fetch the link, smth like app://play?media_id=1). The actual url is fetched using ResolvingDataSource.

Previously we were sending an additional field in our media responses from the backend that contained the available transport methods (HLS, DASH etc). Based on that, we were creating a correspondent MediaSourceFactory on the fly (that MediaSourceFactory was created with ResolvingDataSource). However, this seems to be a sort of hack that we'd like to avoid to make our app more scalable (not to mention that this does not fit into media3 architecture at all)

Possibly obvious question: Given the original 'dynamic' URL do you know whether it will resolve to a DASH or HLS URL? If you do know that in advance then you can just use MediaItem.Builder#setMimeType and everything should just work (this will override any inference done from the URL ending).

Otherwise it sounds like you're looking for a 'do everything' MediaSource. We don't currently have one of those - though there is a draft DefaultMediaSource in a commit linked from google/ExoPlayer#3165 (comment) which you may find useful as inspiration (I haven't compared it in detail to what you've posted).

[NikSatyr]

Thanks for a quick reply.

Regarding dynamic URL: yes, we could include stream type there & then set up mime type, but that's exactly what we'd like to avoid :)

As for the draft commit you provided – this looks kinda promising. I'll take a deeper dive & get back to you

[NikSatyr]

I've dug into the example you provided and it's pretty much the same with what I've come up with. Thanks!