-
Notifications
You must be signed in to change notification settings - Fork 4
No playback integration layer live streams #2
Comments
The issue is most likely, as you explain, that you do not have the "Akamai" token. The AkamaiTokenDataProvider as a media player dataprovider should be used instead of the IlDataProvider directly. Do you have a link to the repository of this application? In the mean time, you can have a look at the ssrdemo module in the Android IL Repository https://github.com/SRGSSR/srg-media-player-android-play which uses this data provider. |
Currently you can reproduce the problem with your ildemo Android Module: If you run the demo and start VIDEO:LIVE example the exception will be displayed How can we resolve this bug? Our customer is disappointed about this issue. |
The paste bin link above seems invalid, can you correct it (or past its content here) ? |
OK, here comes the urn: |
In the IL Demo we have two ways to play IL Streams: with the token or Let us know you have further questions Le ven. 28 oct. 2016 à 15:44, Alexander Knauf notifications@github.com a
|
Ok, thanks works for me in the demo. Then we might change the way we load il streams from api. Actually, we cant differentiate between tokenized and normal li streams from backend. |
Differentiating is not (that) important. On Play SRF we always tokenize URLs as the server does not tell us whether this is required and Akamai does not seem to mind using a token when this is not required. |
OK, we discussed if this a possible way to do. Quick but not as intended I guess? Is this token/not token Stream Issue in scope of the next player version? Thanks |
No, I am not sure the token necessary information is even available at the Le mer. 2 nov. 2016 à 09:44, Alexander Knauf notifications@github.com a
|
New Issue Checklist
Issue Description
Steps to reproduce the behaviour
Complete stacktrace output
Configuration Files
Please copy the complete content of your build.gradle and any other configuration files you use below:
build.gradle:
Environment
Device(s) name(s):Any
Android version(s):Any
The text was updated successfully, but these errors were encountered: