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.

Sign up for GitHub

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

Jump to bottom

Consider adding support for apps to get metadata about what is currently buffered #259

Open
wolenetz opened this issue Oct 20, 2020 · 3 comments
Open

Consider adding support for apps to get metadata about what is currently buffered #259

wolenetz opened this issue Oct 20, 2020 · 3 comments
Labels
TPAC-2022-discussion Marked for discussion at TPAC 2022 Media WG meeting Sep 16

Comments

@wolenetz
Copy link
Member

A "SourceBuffer Introspection API" proposal was discussed at FOMS 2019 in October, but I don't currently find a spec issue tracking further discussion and potential inclusion in MSE v2, so I've filed this issue.

This API would enable greater ability to have precise interop tests, as well as give apps much more information about what is buffered so that they can workaround potential content or API implementation issues.

Comments welcome, especially: is this or something like this something which you would really want available in MSE? Are we missing your use case? Or is this feature unnecessary?

credit for the proposal: @sandersdan
@wolenetz
Copy link
Member Author

Including the current mimetype+codecs string verbatim from the most recent of the addSourceBuffer() original call or possibly a more recent changeType() call in the introspection result could assist interoperable debugging.

@wolenetz wolenetz mentioned this issue Sep 16, 2021
Open
@wolenetz
Copy link
Member Author

This may also motivate getting the "track buffer" concept more clearly specified, especially if such an object model were made visible to apps via an introspection API.

This was referenced Sep 22, 2021
Merged
Closed
wolenetz added a commit that referenced this issue Sep 22, 2021
@wolenetz
Use internal slots for various MediaSource and SourceBuffer object st…
8842ce9 
…ate (#295)

Does the updates described in #286, though some remain for future updates
tracked by #297 and #259.

Modernizes to use internal slot for SB append state:
* Use internal slot for SB first initialization segment received flag
* Use internal slot for SB pending initialization segment for changeType flag
* Use internal slot for SourceBuffer's `input buffer`
* Use internal slot for SourceBuffer's `buffer full flag`
* Use internal slot for SB `group start timestamp`
* Use internal slot for SB `group end timestamp`
* Use internal slot for SB `generate timestamps flag`
* Use internal slot for MediaSource `live seekable range`

Also adds a reference to issue #289 in the coded frame eviction
algorithm.

Also adds text in the definition that mentions that `changeType()`

Updates `generate timestamps flag`: Note, this dfn is exported,
so any previous external references to it via
[=generate timestamps flag=] might need to be changed to
{{SourceBuffer/[[generate timestamps flag]]}} wherever it is referenced.
In particular, media-source.js is updated to (hopefully) enable correct
fragment reference for this definition from MSE BSF Registry ED. The
longer-term fix will be to update that registry's respec directly to
use xref and the linkage, above.
@wolenetz
Copy link
Member Author

This issue is part of a group of "introspection API" or similar API feature requests: #259, #209, #172, #40, #35.

@wolenetz wolenetz added the TPAC-2022-discussion Marked for discussion at TPAC 2022 Media WG meeting Sep 16 label Sep 16, 2022
This was referenced Sep 16, 2022
Open
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
TPAC-2022-discussion Marked for discussion at TPAC 2022 Media WG meeting Sep 16
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wolenetz