Closed AviVahl closed 7 years ago
I had this same problem but being new to DASH I did not know how to debug it. All I could do (since it had been working earlier) was to make sure everything else was still working ... leading me to investigate if anyone else had this error. My question is how were you able to get the debug info contained in your attached file dashif.org-1482609685455.txt. I looked in my (Chrome) browser Console and did not see anything? Did you use the debug version (dash.all.debug.js which has an earlier date of 2007-06-12 18:02:31)?
@cbrady60 the demo page has debug logging enabled: http://dashif.org/reference/players/javascript/v2.4.0/samples/dash-if-reference-player/index.html
So you can open your browser's dev tools, switch to the console tab, right click, and save as...
@AviVahl yep great. Thanks
@AviVahl do you happen to know of a way to access to the previous version which for me worked, or another working version somewhere? Sorry, but I am blocked.
Here are the player archives to test with http://dashif.org/reference/players/javascript/
The cdn code is all versioned if you want that and tagged in github E.g. v2.3 inplace of "latest" in the path
I see the failure the mpd looks fine besides this large update period for live it should be around 30 seconds or less I would think you have it at 595 hours but this is not the issue I do not think minimumUpdatePeriod="PT595H"
Conformance tool says mpd checks out but fails in rep 1 http://dashif.org/conformance.html
Error from tool:
@AkamaiDASH Let me know if I am jumping into @AviVahl issue and if I should go somewhere else to ask my questions. I am not the original writer of this issue. So I am using the information for "Quick start for Users" where I create a .html file and point to http://cdn.dashjs.org/latest/dash.all.min.js which used to work prior to 12/20. I tried looking at http://cdn.dashjs.org/v2.3/dash.all.min.js (replacing "latest" with v2.3, V2.3, v2.30 etc.) with the result that the file was not found. Sounds like you are saying the issue may not be with this latest version of dash.all.min.js (it is very possible I may be doing something wrong but it worked about a week ago and I think I have checked everything else), but how can I get the previous version of dash.all.min.js?
@cbrady60 http://cdn.dashjs.org/v2.3.0/dash.all.min.js
@AviVahl It looks from the logs like the timing in the mp4 wrapper is incorrect compared to what is advertised in the MPD. See the baseMediaDecodeTime - this is some way off from the calculated live edge. Note that http://shaka-player-demo.appspot.com/demo/ doesn't play the stream either.
@bbcrddave thank you very much.
FYI I was able to successfully play video using http://cdn.dashjs.org/v2.3.0/dash.all.min.js with method of "Quick start for Users" (for us newbies) on Chrome Version 55.0.2883.87 m (64-bit). I have not had success (everything else remaining the same) playing using http://cdn.dashjs.org/latest/dash.all.min.js
We are seeing the same issue with our live streams and dash.js 2.4.0. We've been using 2.3.0 (and perhaps 2.2.0) a few months now without any issues. How can I verify the mp4 timing?
This is one of our streams that is playing in 2.3.0 but not in 2.4.0: https://svt01-a.akamaized.net/u/svt01.mpd
@carlanton your problem is probably different since it works in v2.3, whereas the OPs stream does not. Probably worth opening a new issue since this is a regression.
@carlanton Ill take a look at this today to see what is going on. Thanks for reporting.
Appreciate the analysis of the root cause. Forwarded the info to our backend team.
@bbcrddave @AkamaiDASH Sorry, I missed that. I've created a new issue here: #1729
Closing this one then. Thanks again! 👍
Environment
Steps to reproduce
Observed behaviour
Dash.js infinitely requests for chunks, but never fills buffer.
Console output
dashif.org-1482609685455.txt
Additional information
Same stream plays with bitmovin's player: http://bitmovin.com/hls-mpeg-dash-test-player/