{"action":"created","issue":{"url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js/issues/1553","repository_url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js","labels_url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js/issues/1553/labels{/name}","comments_url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js/issues/1553/comments","events_url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js/issues/1553/events","html_url":"https://github.com/Dash-Industry-Forum/dash.js/issues/1553","id":173433031,"number":1553,"title":"Axinom v7 encrypted test vectors fail to play","user":{"login":"sandersaares","id":9914262,"avatar_url":"https://avatars.githubusercontent.com/u/9914262?v=3","gravatar_id":"","url":"https://api.github.com/users/sandersaares","html_url":"https://github.com/sandersaares","followers_url":"https://api.github.com/users/sandersaares/followers","following_url":"https://api.github.com/users/sandersaares/following{/other_user}","gists_url":"https://api.github.com/users/sandersaares/gists{/gist_id}","starred_url":"https://api.github.com/users/sandersaares/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sandersaares/subscriptions","organizations_url":"https://api.github.com/users/sandersaares/orgs","repos_url":"https://api.github.com/users/sandersaares/repos","events_url":"https://api.github.com/users/sandersaares/events{/privacy}","received_events_url":"https://api.github.com/users/sandersaares/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-08-26T11:35:08Z","updated_at":"2016-09-05T06:03:35Z","closed_at":null,"body":"We have updated the Axinom test vector suite, which contains what I believe are valid encrypted DASH videos. However, they do not appear to play with dash.js (2.3 development branch latest state). \r\n\r\nFull information about test vectors: https://github.com/Axinom/dash-test-vectors\r\n\r\nDash.js with v7 test vectors in sample player: https://github.com/Axinom/dash.js/tree/axinom-test-data-v7\r\n\r\nFrom the above sample player, see Axinom test data menu. The clear videos start playback successfully. All the encrypted videos fail to start playback.\r\n\r\nMPDs pass validation without issues. There are various minor warnings/errors about segment contents but nothing that jumps out at me as critical.\r\n\r\nMajor encryption-relevant change from v6 encrypted test vectors: no `pssh` in initialization segments, to better conform to DASH-IF IOP 3.3 and CMAF.\r\n\r\nBrowsers tested:\r\n\r\n* Chrome 52\r\n* Edge 38\r\n\r\nBehavior is not consistent - different runs can produce slightly different behavior, though restarting browser seems to produce predictable results (presumably some relevant CDM state is reset?).\r\n\r\nCommon \"stop point\" where things break (roughly correlated in time) appears to be processing of the initialization segment.\r\n\r\nSometimes a license acquisition occurs (response from server is successful and all goes well, apparently). Sometimes no license acquisition occurs!\r\n\r\nBrowser logs from playing the first movie in the menu:\r\n\r\n* [Chrome52.txt](https://github.com/Dash-Industry-Forum/dash.js/files/439140/Chrome52.txt)\r\n* [Edge38.txt](https://github.com/Dash-Industry-Forum/dash.js/files/439148/Edge38.txt)\r\n\r\nEdit: removed Firefox 44. I am informed that Firefox 44 is out of date. Firefox told me no updates were available and I naively thought that meant I had latest version..."},"comment":{"url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js/issues/comments/244664934","html_url":"https://github.com/Dash-Industry-Forum/dash.js/issues/1553#issuecomment-244664934","issue_url":"https://api.github.com/repos/Dash-Industry-Forum/dash.js/issues/1553","id":244664934,"user":{"login":"sandersaares","id":9914262,"avatar_url":"https://avatars.githubusercontent.com/u/9914262?v=3","gravatar_id":"","url":"https://api.github.com/users/sandersaares","html_url":"https://github.com/sandersaares","followers_url":"https://api.github.com/users/sandersaares/followers","following_url":"https://api.github.com/users/sandersaares/following{/other_user}","gists_url":"https://api.github.com/users/sandersaares/gists{/gist_id}","starred_url":"https://api.github.com/users/sandersaares/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sandersaares/subscriptions","organizations_url":"https://api.github.com/users/sandersaares/orgs","repos_url":"https://api.github.com/users/sandersaares/repos","events_url":"https://api.github.com/users/sandersaares/events{/privacy}","received_events_url":"https://api.github.com/users/sandersaares/received_events","type":"User","site_admin":false},"created_at":"2016-09-05T06:03:35Z","updated_at":"2016-09-05T06:03:35Z","body":"I have reported these issues to browser vendors but as they have a very \"EME/MSE\" world view, it is difficult to communicate the problem. Would it be possible for a dash.js developer familiar with EME/MSE to take a look at the communication between dash.js and the browser here, to verify that it looks \"sane\"? I will also try but my knowledge of dash.js internals is effectively zero."}}
{"actor":{"display_login":"sandersaares"}}