Skip to content

Support Serialization with forStorage=true #291

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

Open
chcunningham opened this issue Jul 6, 2021 · 2 comments
Open

Support Serialization with forStorage=true #291

chcunningham opened this issue Jul 6, 2021 · 2 comments
Labels
extension Interface changes that extend without breaking.

Comments

@chcunningham
Copy link
Collaborator

VideoFrame and AudioData don't currently'support forStorage=true.

@padenot mentioned that apps will want this https://github.com/w3c/webcodecs/pull/286/files/01117f8cd1ab2fe293991e4cdc27ab5811f20781#r656313078

@chcunningham chcunningham added the extension Interface changes that extend without breaking. label Jul 6, 2021
@sandersdan
Copy link
Contributor

sandersdan commented Jul 7, 2021

The main reason this wasn't implemented in Chrome's version is that hardware-backed frames don't behave exactly the same when deserialized after a readback, and also it requires synchronous readback during serialization. This is not so much a problem for AudioFrame (and is probably a UA quality-of-implementation issue for VideoFrame).

The most direct comparisons are ImageBitmap (can be stored) and ArrayBuffer (can be stored unless it is a SharedArrayBuffer).

@ChunMinChang
Copy link
Member

It seems this conflicts with #590. Is this request still needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extension Interface changes that extend without breaking.
Projects
None yet
Development

No branches or pull requests

3 participants