2007/12/12, Øyvind Kolås <pippin@xxxxxxxx>:
By requesting a subregion to be rendered, the minimal required regions
to be computed for every node is first computed in a first pass
(expanding as needed for context for blurs, and restricted by crop
operations present in the graph.) Moving scaling to be performed as
early as possible is something that has been considered but currently
is not done since it would be in conflict with the per-node caches.
As mentioned there is only a single cache, but the buffers these
caches are built on have built in capabilities for mipmap scaling.
These things are not mentioned in detail on the webpage because
they are things that might change for the better in the future
independently of the public API.
When you say that the buffers have built in capabilities of mipmap scaling, what do you mean by that? For me mipmaps are prescaled versions of images to make arbitrary scaling much faster. When executing an operation do you only use the mipmap buffer that is nearest the desired scale so you don't need to operate on the full scale image?
To exemplify. If you want to make a fast preview by applying an operation on a scaled down version of an image, do you have to use separate graph representations for the scaled down version versus the full size image meaning that you need a scale operator in one of graph paths or will this be managed by the mipmap buffers and using the scale parameter in the blit-function. Meaning that the operation is only performed on the mipmap scaled version that is closest to the choosen scale.
/Patrik Ö
_______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
