Hi,
In Figure 2-1 of "Interface Specification for MSDC Release 3.2" document, A "Media Player" is shown with an integrated "Dash Client Data Source". Is this "Media Player" the default "MediaPlayer" distributed as part of the Android SDK, or a special or adapted Media Player that is integrated with a Qualcomm DASH Client?
If the Qualcomm DASH Client is needed to use the LTE Broadacst SDK, how can we get access to the Qualcomm DASH Client?
Thanks for any help.
Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
Hello,
In order to play streaming services, there needs to be a DASH client installed on the device. Qualcomm provides a DASH client as part of the chipset software package to the device manufacturers. It is the decision of the device manufacturer to include Qualcomm's DASH client in their device or not. Qualcomm's DASH client is not available as part of the SDK or as a separate package. Alternatively, the application can use a 3rd party DASH client.
Thanks,
Elmira
Hello Elmira
Thanks for your reply.
If the Android device has the Qualcomm DASH Client integrated, I suppose the interface between the DASH Client and the Qualcomm MSDC (Multicast Service Device CLient) is done by the device vendor.
Any guidance available on using third party DASH Client, such as ExoPlayer with MSDC? Because the Qualcomm MSDC serves effectively as a HTTP cache in these cases, how to redirect the DASH Client's HTTP requests of media segments to MSDC rather than an external HTTP server? Is this achieved by some kind of converion in MPD file?
The Qualcomm SDK test stub doesn't seem to use MPD. It bascially passes a media file i.e. a MP4 file in place of MPD URL. Dose the test stub actually bypass the DASH Client?
Hello,
Qualcomm DASH player uses the same API as Android mediaplayer. You can find some sample code in the API documentation.
After receiving the serviceListUpdate notification, "ServiceInfo" object has the information about the MPD URL which points to the MSDC HTTP server. So you just need to pass the MPD URL to the DASH client.
The Stub Tool is designed to allow applications be tested on the devices that do not have the DASH client. However if you have a DASH client, you can configure the proper MPD URL in the Stub config instead of the mp4 location.
Thanks,
Elmira
Hello Elmira
Thanks again for your help.
So if the device has a Qualcomm DASH Client available, we can just use the Android SDK MediaPlayer API as the SDK interface specification defined.
However if a thrid party DASH Client has to be used somehow, the mpdUri in "ServiceInfo" will point to where on local storage the service MPD file is stored. For those media segments specified inside the MPD file, does the MSDC client adaptes the MPD file when it is received, and set the media segments URIs to local storage folder where they are stored (cached)? Or maybe this is a question about integration between Qualcomm MSDC Client and a LTE BM-SC server? Does Qualcomm MSDC Client require any specific BM-SC server to work?
Hello,
The MSDC middleware updates the MPD so the DASH client retrieves the segments using the URL that points to the middleware.
The magic happens in the MSDC middleware and DASH client does not need to do anything special.
Thanks,
Elmira
Hello Elmira
Many thanks for your help. So the MSDC could work with third party DASH Client. Presumably when MPD is changed, the App get notified through mpdUpdated callback.
Thank you again for your help.