Open muganda opened 4 years ago
We don't currently support this type of UTCTiming
element (why there needs to be 4 different ways of doing this is really beyond me!).
In order for us to test any support we do add for it, could you please provide a test stream as requested in the issue template? Thanks!
Hey @muganda. We need more information to resolve this issue but there hasn't been an update in 14 days. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
In the end I asked my streaming service provider to change something about the format. All is well now.
Thanks for the update! I will mark this a low priority enhancement. In practice this means we'll probably ignore it until at least the point when someone else asks for it and is able to provide test content.
@ojw28 We would be grateful if you could add support for urn:mpeg:dash:utc:http-head:2014
.
We have prepared a test content: http://r.dcs.redcdn.pl/livedash/o2/atendesoftware/live/live.livx/live.mpd?indexMode&dummyfile
Hi @tonihei, I'd appreciate an update on the current status of this issue
No update I'm afraid. Feel free to look into DashMediaSource to see how other timing schemes are handled and maybe you can provide a pull request to add support for this scheme if it's more urgent?
[REQUIRED] Searched documentation and issues
I have looked at the previously reported issues on ExoPlayer and on stackoverflow as well.
[REQUIRED] Question
I am working with live streams from a streaming provider in DASH format. The manifest file includes UTCTiming schemeIdUri="urn:mpeg:dash:utc:http-head:2014".
A full bug report captured from the device
Link to test content