John Cupitt
Sorry, I don't know, you'd need to post a complete program I can test. Did the example work for you? I see: ``` $ ./progress.py preeval: run = 0 eta...
You should be able to cancel. But you need to show me a complete program that fails to work before I can say what's wrong. Here's another demo: ```python #!/usr/bin/python3...
You need to attach the callbacks before calling `write_to_file`.
Yes, you're attaching the callbacks after you've already written the image. Try: ```python image.set_progress(True) image.signal_connect('preeval', preeval_cb) image.signal_connect('eval', eval_cb) image.signal_connect('posteval', posteval_cb) image.write_to_file(sys.argv[2]) ```
No, it would stop the save at 20%. Try it!
`new_from_file` is a pixel source, so it supplies pixels down the pipeline to operations that need them. It does not loop over the image, and does no processing itself. The...
Hello, did you see: https://www.libvips.org/API/current/libvips-resample.html#vips-affine
That's the main documentation. In python you could write: ```python #!/usr/bin/python3 import sys import pyvips x = pyvips.Image.new_from_file(sys.argv[1]) if not x.hasalpha(): x = x.addalpha() y = x.affine([0.70710678, 0.70710678, -0.70710678, 0.70710678])...
Hi @euzada, Try removing the `access="sequential"`. You are splitting the images to separate RGB planes, then joining them vertically, so each input image needs to be scanned three times. With...
... I would assemble your tiles to a regular tiled tiff, then convert that file to ome-tiff in a second pass.