Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Play Event: Investigate why secondsToLoad can report extremely high #3

Open
spodlecki opened this issue Nov 6, 2017 · 2 comments
Open
Assignees
Labels

Comments

@spodlecki
Copy link
Owner

spodlecki commented Nov 6, 2017

Within the play tracking, the secondsToLoad has been reported to be very high. It is possible that the video is being loaded and not played for a long time. Maybe the user paused before first frame?

Example graph;
play-secondstoload-graph

@spodlecki spodlecki added the bug label Nov 6, 2017
@spodlecki spodlecki self-assigned this Nov 6, 2017
spodlecki added a commit that referenced this issue Nov 18, 2017
* resolves #4 : Updating buffering tracking to reset when the player is paused or scrubbed (same event triggered for videojs: pause)

* updates #3 : reset secondsToLoad variable when a new loadstart is triggered
@spodlecki
Copy link
Owner Author

spodlecki commented Nov 18, 2017

merged & releasing 0.0.6 to npm

keeping open until stats show improvement on accuracy

@spodlecki
Copy link
Owner Author

accuracy improved, but I'm still getting cases where the numbers are sky-high. will need to keep looking around at specific cases when this happens... maybe it'll help me find and reproduce

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant