[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] lossless texture uploading
- To: "Mo, Zhenyao" <email@example.com>
- Subject: Re: [Public WebGL] lossless texture uploading
- From: "Gregg Tavares (wrk)" <firstname.lastname@example.org>
- Date: Wed, 17 Nov 2010 16:50:06 -0800
- Cc: public webgl <email@example.com>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1290041408; bh=7zHztkn8PYN5Shy/bgqV1ylpNJI=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=xVm56SWpKRbQ0a5LUZm+SYgN0hIkSwKmStDqS6AgH1+46awV5vFrMIvOms2yHko9B MBM+a/IT8mNukVCuZ1nBQ==
- 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; bh=+OHhY5HY2jgk9YFm5HXBxJVyL32bVM8/VZvZjxKLy10=; b=K0eJ8VLHh56AChLE8d0bpc9sXSApj7ZORM75KWOCKr3wo8NJHjlnVONO3dAc3SqCm/ Yxe2oBEtOep6PCOjFGdg==
- 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; b=EryYePYgfuQ+2PcEBzhYSfCdj6A8sObcvKEKEZzVLCit2TfiCQso9BUOKqY8E743Sh aHYon3MmFhNE/Uvb0Mdw==
- In-reply-to: <AANLkTi=Z3P1=WJOLtv1zbA1PmyormasqOifuFn46W+QS@mail.gmail.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <AANLkTi=Z3P1=WJOLtv1zbA1PmyormasqOifuFn46W+QS@mail.gmail.com>
- Sender: firstname.lastname@example.org
On Wed, Nov 17, 2010 at 4:05 PM, Mo, Zhenyao <email@example.com>
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?
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: