[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] lossless texture uploading
- To: "Gregg Tavares (wrk)" <email@example.com>
- Subject: Re: [Public WebGL] lossless texture uploading
- From: Kenneth Russell <firstname.lastname@example.org>
- Date: Thu, 18 Nov 2010 15:39:11 -0800
- Cc: "Mo, Zhenyao" <email@example.com>, public webgl <firstname.lastname@example.org>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1290123554; bh=k/IA3RFXKLBkoXI1mlTaAfVcKPU=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=yVzlXCnX0FbZyi/GHK30EVG2/hSuytJh2ugGKYVI+/Dj2reoTwyQTJ20j4STHcVmh B6cm19hEAUQ93tgVK0NVg==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Trkphc7FpCt4+37NS/o/ArJQbzPSSXQMLoAQGXSwXw4=; b=JlZ6CkhJvViqHpL+3IMolSBsiFzX7d0g1fzL0l0bUNqZEoF8nBpd8xHr+hho4kflXa ciu03kpJnPk1cAb25CeQ==
- Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mxNMSwMmNQEFKz9BduGLmlyEWr3t/z5WX+stb3xI+eBy5h/vYfadVIPul70jGdbVRt ZI5VVy8/dfHyqKV9YuKQ==
- In-reply-to: <AANLkTikNrWRm1Y21TMi1NCJbssFhQ5Rvn6XrVJCDamk1@mail.gmail.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <AANLkTi=Z3P1=WJOLtv1zbA1PmyormasqOifuFn46W+QS@mail.gmail.com> <AANLkTikNrWRm1Y21TMi1NCJbssFhQ5Rvn6XrVJCDamk1@mail.gmail.com>
- Sender: email@example.com
On Wed, Nov 17, 2010 at 4:50 PM, Gregg Tavares (wrk) <firstname.lastname@example.org> wrote:
> On Wed, Nov 17, 2010 at 4:05 PM, Mo, Zhenyao <email@example.com> wrote:
>> During the implementation of COLORSPACE_CONVERSION setting in webkit,
>> I began to think that maybe COLORSPACE is not the correct word for the
>> issue. What we want is the raw bits from the image data, ignoring all
>> the settings in the image header (meta data). Color space only covers
>> one of those settings. Others include gamma, image orientation, and
>> who knows what might be added in the future?
> I noticed this as well. The original intent was to provide a way to get
> exact binary data from lossless image formats into a WebGL into a texture.
> For PNG that means ignoring the sRGB, iCCP, cHRM, gAMA chucks.
> But the new UNPACK_COLORSPACE_CONVERSION_WEBGL pixelStore setting only
> mentions that colorspace will not be applied. It mentions nothing about
> gamma or other settings that might end up changing the values uploaded to
> the texture and it mentions nothing about only caring about lossless images.
> The implication is that colorspace settings should also be ignored in JPEGs
> as well.
> I thought the goal was to specify a way to guarantee, cross browser, that
> loading certain kinds of images into a WebGL textures would have the exact
> same binary values passed to glTexImage2D and related functions.
> Should we update the spec and/or the name of the enum to make that clearer?
> or maybe just changing the description of UNPACK_COLORSPACE_CONVERSION_WEBGL
> to cover the goals?
The wording in the spec is intentionally vague because some of the
authors (like me) aren't well versed in all of the parameters of these
files. That having been said, while JPEGs aren't useful for uploading
data losslessly to WebGL, if we have an option for passing through PNG
files' data without applying an ICC color profile then I think it
might as well apply to JPEG files as well. At least in the WebKit
implementation, Mo has wired up the flag to both JPEGs and PNGs.
Personally I think the current wording is fine and we can supplant
this flag with another more tightly defined one in a future version of
the spec if necessary.
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: