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
Access to raw metadata #3
Comments
Absolutely agree. But given that we are adopting the frames from WebCodecs, can you raise an issue on this in the WebCodecs repo and link it here? |
@youennf ? |
Thanks for the ping, will do it shortly. |
Great, closing in this repo. |
I think there are WebRTC bits we need to discuss outside of WebCodecs. Reopening this issue for now. Though maybe we could move it to webrtc encoded transform. |
I think we have been discussing this in the context of encoded transform, so closing this. |
I can see use cases where it would be useful to have metadata attached to raw frames be exposed to JavaScript.
This could for instance be head detection metadata that some cameras already generate.
Or it could be a track processor that adds such metadata in addition to (or in lieu of) modifying the pixels.
There may be also use cases where this metadata should be preserved by the encoder (or decoder) so that the JS raw frame metadata would be kept attached to the JS encoded frame (or vice versa).
The text was updated successfully, but these errors were encountered: