hello
Id love some clarification on how the colorspace: parameter on the
various methods in QC work.
for lockTextureRepresentationWithColorSpace:forBounds on an
QCPlugInInputImageSource, does the colorspace method decide the source
colorspace of the image, or the destination colorspace? ie:
a) (source) interpret this image as <some colorspace> and convert it
to RGB since its going to be a texture and used in GL.
b) (destination) interpret this image in its native colorspace and
convert it to <some colorspace> ?
Similarly, for: QCPlugins
outputImageProviderFromTextureWithPixelFormat:pixelsWide:pixelsHigh:name:flipped:releaseCallback:releaseContext:colorSpace:shouldColorMatch
method
does this take a texture, assumed to be in RGB, and set it to be <some
colorspace> or does it take a texture, assumed to be <some colorspace>
and convert it to RGB, or does it take anything, as anything, and just
set a marker to be <some colorspace> to be dealt with at a later stage?
While we are on the topic, I would love some clarification:
Is there a default/native color space to QC? I would wager yes, and
that its RGB Linear since QC operates in GL land, and that RGB linear
is (am I correct) the assumed default colorspace of GL, or is the
'native' colorspace whatever the QCRenderer in question was initted
with?
Thanks, id love to hear a 'short story' on a few images of various
colorspaces passing through QC, and how it is converted etc. Might
make a fun exercise.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
