Replies: 2 comments 1 reply
-
Hello @jstkdng, your project looks interesting!
You might have a reference leak. I would add
It always picks the best access mode for you (usually sequential, but not always).
It depends on the image format, number of pixels, size of thumbnail, etc., but yes, it can be many times faster. For example, with a 6k x 4k JPEG I see:
Most images don't really exist and have no data, they are just nodes in a computation graph. You can force an image into memory and get a pointer with: if (vips_image_wio_input(image))
error_handling();
// get a pointer to the pixel at this coordinate
unsigned char *p = VIPS_IMAGE_ADDR(image, 128, 2568); But this will (of course) take a lot of time and memory. |
Beta Was this translation helpful? Give feedback.
-
I tried using
I see a lot of copies (?
awesome, i'll keep using thumbnail_image
rip, i'll keep using write_to_memory then |
Beta Was this translation helpful? Give feedback.
-
Hello, I've rewritten my project from vips-cpp to C libvips and I found that it's memory usage goes from 8m (without loading any image) to 1gb after many images are loaded/unloaded.
This is the main file containing the implementation and the header file. I appreciate any help and thank you for building this awesome library.
Beta Was this translation helpful? Give feedback.
All reactions