W3C home > Mailing lists > Public > public-html@w3.org > June 2012

[Bug 17610] New: suggest video element support non-buffered video play

From: <bugzilla@jessica.w3.org>
Date: Wed, 27 Jun 2012 01:20:45 +0000
To: public-html@w3.org
Message-ID: <bug-17610-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17610

           Summary: suggest video element support non-buffered video play
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: eric.sun@huawei.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 27 June 2012 01:23:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 01:23:39 GMT