This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
During development of some cloud service using html5, we find it is benefitial to send frame to video element for display and interaction. But when we study the internal implementation, it seems that video element must decode metadata, then buffer enough amount of data for display. Even if we set the video attribute autoplay, we can not prevent the buffer behavior of video element, should it be better if video can support a non-buffer mode? I think video game, video interaction will be very popular in the future. We have consider using Canvas, but a little more complex, and we need direct video to Canvas using JS, which is not good for real time. Can anyone give some hint or comment?
I think maybe WebRTC is something you're looking for?
This bug was cloned to create bug 17884 as part of operation convergence.
The buffering behavior is controlled by the preload attribute, currently having the values none, metadata and auto. It sounds like preload="none" might be what you want?
Eric: do Odin and Philip's suggestions address your concern?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Additional Information Needed Change Description: none yet Rationale: it's unclear whether the existing suggestions address the bug to the OP's satifaction or not.