On 19.08.2005, at 09:41, Pierre-Olivier Latour wrote:
I just noticed that images are resized according to available
texture memory,
i.e. 2048 x 2048 before being passed into QC.
This kind of breaks my application - I would like to use
Compositions to postprocess
Digital Camera images at full resolution, allowing the user to
save the final image.
Is there any way around that limitation, if at a performance
penalty ?
(I could use the smaller image for display, the larger for saving)
You could pass a smaller version of the image for preview and when
rendering, tile the image and pass the tiles one by one to QC.
Hmm. That would work for color correction and the likes but could
as far as I understand lead to artifacts when using filters that
work on neighbouring pixels.
While one could get around that by using larger tiles and removing
the overlap
I think it would be nice to have API that either encapsulates such
action
(whatever the optimized technique to do it may be on a certain platform)
in the future.
I think most applications that work on still images will have this
problem
and I'd be interested to here other list members opinions before I file
a report about it.
