-
Notifications
You must be signed in to change notification settings - Fork 57
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
new feature - add remove sourcebuffer in every moment #120
Comments
either firefox either chrome dont work in this case. I submited same feature also in firefox bugtracker, receiving positive feedbacks for this proposal |
@publicocean0, thank you for reporting this issue. The V1 version of the spec does not allow changes to number or type of tracks in a SourceBuffer after that SourceBuffer has parsed the first initialization segment appended to it (I understand this isn't the scenario you're asking for, though). Web authors can perhaps work-around user agents which support the minimum required SourceBuffer configurations, but perhaps not the dynamic addition of new SourceBuffers once HAVE_METADATA has been reached, by one of the following:
Changing the minimum requirement for SourceBuffer configurations is beyond scope of MSE v1 spec changes (it's a substantive change). Triaging this issue as VNext, accordingly. Comments are very welcome around this (including viability of or addition to the workarounds mentioned here). |
With the changeTypee() incubation succeeding so far (shipped in multiple implementations), this issue seems less problematic. I'll keep it alive in the backlog though, in case web authors strongly desire this capability in MSE. |
I imagine to have multiple audio /video tracks with different languages and a user can change on the fly the language.
It is interesting if developer can add/remove a audio track on the fly permitting to keep the position of stream. Probably it is necessary add a new sourcebuffer , add initialization buffer and then add the segment at right stream position.
The text was updated successfully, but these errors were encountered: