Re: [Public WebGL] WEBGL_dynamic_texture extension proposal

[Mark Callow <callow_mark@hicorp.co.jp>]

    On 06/07/2012 06:02, Chris Marrin wrote:

There are a couple of inconsistencies:

1) The IDL says "dynamicTextureAcquireImage" and the description says "dynamicTextureAcquireFrame". Same for release.

    Fixed. Thanks. The search/replace in my XML editor when I decided to
    change the name, missed these because they are element attributes.

2) dynamicTextureSetSource passes the texture in the IDL and description, but not in the example.

    Also fixed.

Given the nature of OpenGL, seems like you should not pass the texture, but rather use the currently bound texture? Same would be true of all the other API calls.

    Yeah. See issues #3, #4 & #9, currently unresolved.
    
    I was thinking that an app. might have dynamic textures on several
    texture units and doing activeTexture/bindTexture on each in order
    to call acquireImage was a bit much. This led me to pass
    <texture> to acquireImage. Once I'd done that, I decided to
    make setSource direct access as well.

I am also concerned about timestamping. ...

Your proposal doesn't deal with timestamps, so it's possible to get out of sync with the decode rate, causing strobing or other undesirable effects.

    How do you handle this today when an HTMLVideoElement is passed to
    texImage2D?
    
    I'm not sure that strobing, etc. will really be a problem. Basically
    the images are triple buffered, as Gregg described upthread, and you
    will always get the latest available frame. The worst that will
    happen is a few dropped frames. If the app. is drawing so fast it
    gets the same video frame more than once in succession, I don't
    think that is a problem.
    
    But you bring up a good point and this definitely needs
    consideration.
    
    Regards
    
        -Mark

--

注意：この電子メールには、株式会社エイチアイの機密情報が含まれている場合が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情報の使用を固く禁じております。エラー、手違いでこのメールを受け取られましたら削除を行い配信者にご連絡をお願いいたし ます。

NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.