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

fix: Return the correct buffer for each segmentloader #542

Merged
merged 3 commits into from
Jun 13, 2019

Conversation

brandonocasey
Copy link
Contributor

With the current implementation a separate video and audio segment loader will try to use the combined buffered value, this causes all kinds of issues. For high bit rate sources we see a lot of append over max on source buffer errors.

@brandonocasey brandonocasey mentioned this pull request Jun 11, 2019
19 tasks
@brandonocasey brandonocasey added this to the TBA/LHLS milestone Jun 11, 2019
gkatsev
gkatsev previously approved these changes Jun 11, 2019
Copy link
Member

@gkatsev gkatsev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense and seems to sort of match usage in remove().
I'd still like to test this before merging, though.

@brandonocasey
Copy link
Contributor Author

Added the source I used for testing, although you will have to force the 4k rendition to get it to happen.

@gkatsev
Copy link
Member

gkatsev commented Jun 12, 2019

Would be nice to add the quality-levels plugin on this page as well. I added 'node_modules/videojs-contrib-quality-levels/dist/videojs-contrib-quality-levels' to the list of scripts in the change handler thingy. I then used Array.from(player.qualityLevels()).forEach(l=>l.enabled = l.height > 1000) to choose the 4k rendition

gkatsev
gkatsev previously approved these changes Jun 12, 2019
Copy link
Member

@gkatsev gkatsev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just tested this. Without the change, I kept getting sourcebuffer is full error messages and then about 6 minutes it stalled. With this change it is playing back without any error messages.

ldayananda
ldayananda previously approved these changes Jun 12, 2019
Copy link
Contributor

@ldayananda ldayananda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, makes sense to me.

Edit: Did a quick test with the 4K rendition and got a lot of buffering but quick recovery and no stalls

@@ -150,6 +150,7 @@
var urls = [
'node_modules/video.js/dist/alt/video.core',
'node_modules/videojs-contrib-eme/dist/videojs-contrib-eme',
'node_modules/videojs-contrib-quality-levels/dist/videojs-contrib-quality-levels',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this breaks the Netlify build, probably because videojs-contrib-quality-levels would have to be added to the devDependencies

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, whoops. Needs to be copied over in the netlify script

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just needs to be added here

const vjs = 'node_modules/video.js/dist/alt/video.core.js';
const vjsCss = 'node_modules/video.js/dist/video-js.css';
const eme = 'node_modules/videojs-contrib-eme/dist/videojs-contrib-eme.js';
const indexScript = 'scripts/index.js';
const deployDir = 'deploy';
const files = [vjs, vjsCss, eme, indexScript];

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interesting will do

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there any reason that we don't just deploy out of the root project directory?

@gkatsev
Copy link
Member

gkatsev commented Jun 13, 2019

The only failing test is the live dash playback one. It is also failing unreliably, even if most of the time. When applying #545 it can reliably pass.
Going to go ahead a merge this particularly since master is frozen until all the TBA/LHLS work is in.

@gkatsev gkatsev merged commit 5124355 into master Jun 13, 2019
@gkatsev gkatsev deleted the fix/over-max-append branch June 13, 2019 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants