{"action":"created","issue":{"url":"https://api.github.com/repos/jaruba/wcjs-player/issues/75","repository_url":"https://api.github.com/repos/jaruba/wcjs-player","labels_url":"https://api.github.com/repos/jaruba/wcjs-player/issues/75/labels{/name}","comments_url":"https://api.github.com/repos/jaruba/wcjs-player/issues/75/comments","events_url":"https://api.github.com/repos/jaruba/wcjs-player/issues/75/events","html_url":"https://github.com/jaruba/wcjs-player/issues/75","id":182705640,"number":75,"title":"Player does not emit playing event after buffering event","user":{"login":"dragantl","id":17302599,"avatar_url":"https://avatars.githubusercontent.com/u/17302599?v=3","gravatar_id":"","url":"https://api.github.com/users/dragantl","html_url":"https://github.com/dragantl","followers_url":"https://api.github.com/users/dragantl/followers","following_url":"https://api.github.com/users/dragantl/following{/other_user}","gists_url":"https://api.github.com/users/dragantl/gists{/gist_id}","starred_url":"https://api.github.com/users/dragantl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dragantl/subscriptions","organizations_url":"https://api.github.com/users/dragantl/orgs","repos_url":"https://api.github.com/users/dragantl/repos","events_url":"https://api.github.com/users/dragantl/events{/privacy}","received_events_url":"https://api.github.com/users/dragantl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-10-13T06:25:21Z","updated_at":"2016-10-21T10:46:18Z","closed_at":null,"body":"I get the following sequence of events:\r\n\r\n- `opening`\r\n- `buffering`\r\n- `playing`\r\n- `buffering`\r\n\r\nHowever, I would expect `playing` to be emitted after the last `buffering` event, assuming that the two events are reflections of `waiting` (http://www.w3schools.com/tags/av_event_waiting.asp) and `playing` (http://www.w3schools.com/tags/av_event_playing.asp) events of HTML5 video.\r\n\r\nI remember we had this conversation a while ago. It was mentioned that VLC lib emits a huge number of events and they are hard to sync/report. However, wcjs-player already tracks and syncs end of buffering event. That is seen by it being able to remove the `Buffering %` UI element. What needs to happen is it should also emit `playing` event at that time (I do not think `buffering` state can be entered while in `paused` state)."},"comment":{"url":"https://api.github.com/repos/jaruba/wcjs-player/issues/comments/255350995","html_url":"https://github.com/jaruba/wcjs-player/issues/75#issuecomment-255350995","issue_url":"https://api.github.com/repos/jaruba/wcjs-player/issues/75","id":255350995,"user":{"login":"jaruba","id":1777923,"avatar_url":"https://avatars.githubusercontent.com/u/1777923?v=3","gravatar_id":"","url":"https://api.github.com/users/jaruba","html_url":"https://github.com/jaruba","followers_url":"https://api.github.com/users/jaruba/followers","following_url":"https://api.github.com/users/jaruba/following{/other_user}","gists_url":"https://api.github.com/users/jaruba/gists{/gist_id}","starred_url":"https://api.github.com/users/jaruba/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaruba/subscriptions","organizations_url":"https://api.github.com/users/jaruba/orgs","repos_url":"https://api.github.com/users/jaruba/repos","events_url":"https://api.github.com/users/jaruba/events{/privacy}","received_events_url":"https://api.github.com/users/jaruba/received_events","type":"User","site_admin":false},"created_at":"2016-10-21T10:46:18Z","updated_at":"2016-10-21T10:46:18Z","body":"I'm not saying it doesn't work, just that I can't predict all the possible implications of it. For example, keep in mind that the 'playing' event is not the one that's wrong here. The 'buffering' event is wrong. Because in order to prevent what's commonly known as event flood, the 'buffering' events are being queued one after the other. So 'playing' is sent properly, while 'buffering' is being pushed further into the timeline. What you did is correct in fixing it for your requirements, and the perfect / simplest way of avoiding a similar issue for others. But in reality, the 'playing' event should count as 'buffering 100', not the other way around. :)"}}
{"actor":{"display_login":"jaruba"}}