You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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
The text was updated successfully, but these errors were encountered: