[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Public WebGL] texImage2D calls with HTMLVideoElement
- To: email@example.com
- Subject: [Public WebGL] texImage2D calls with HTMLVideoElement
- From: Adrienne Walker <firstname.lastname@example.org>
- Date: Fri, 13 Aug 2010 11:03:23 -0700
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1281722635; bh=WXut9jfvrb9cecntTf+q9KWnSbY=; h=MIME-Version:From:Date:Message-ID:Subject:To:Content-Type; b=IkxCUL5TFucqNQ83WlWMnSeAOOZpX7/xFfs9FquuFWDQ9cWOt7TgRxz7ZhZjd/vj6 ZNOsymAFbYPPp3L+zqgxQ==
- Domainkey-signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:from:date:message-id:subject:to:content-type:x-system-of-record; b=Yvt3SDvVbUQ+pvJ61acNxps5q7Mo1iWQVTdGKpBrdWWO2A7rfjVYfcPllGbAV/ims BftemYya5bHj954naTwgA==
- Sender: email@example.com
I was looking at the WebGL spec about the tex(Sub)Image2D calls and
had two questions:
1) Why do the texImage2D calls that take HTMLMediaElement parameters
allow the specification of format and type? Along those same lines,
why is the spec so insistent that image data must be downconverted to
lower precision if it is specified?
The only use case I can imagine is that with a packed format you save
on upload bandwidth and texture memory at the expense of conversion,
but only if the HTMLMediaElement is being composited on the CPU, which
is likely to not be the case for most of those element types in the
future. The element's width and height are already implicitly used as
parameters in the call--why not the format as well?
2) Regarding the texImage2D call with the HTMLVideoElement, the spec
is unclear about how to handle poster attributes. Is this
intentionally left as an implementation detail?
Forgive me if either of these have been discussed before. I tried
searching the email archives, but couldn't turn anything up.
You are currently subscribed to firstname.lastname@example.org.
To unsubscribe, send an email to email@example.com with
the following command in the body of your email: