John Cupitt
Hello Kleis and @feelgood-interface, yes, the previous folder structure was forced on us and the new structure is the one we plan to stick to if we possibly can.
Hi again @idc9, You'll get that error if you make an out of order read from a sequential image. Perhaps you passed `access="sequential"` by mistake? It's usually best to post...
I had a look at your test file, it's a Perkin-Elmer QPI, so it won't work with a standard TIFF loader. You'll need a specialized load library for this file...
> pyvips seems to work otherwise with this image format It's a plane-separated pyramid, unfortunately, so it won't work. It's to do with the way the reduced resolution levels are...
That's just a minor symptom -- the cause is this TIFF file being way outside the supported range for any general purpose TIFF reader. Options off the top of my...
Hi @LionelArn2, I'll see if I can reproduce this. It's a tricky one to test :(
Hi again, just use `avg` on the boolean result image. libvips uses 255 for true, so divide by 255 to get the number of true pixels. For example: ``` $...
Hi @euzada, We've talked about adding GPU path to libvips, but no one's done the work yet.
Improving efficiency is all about having good benchmarks. Make a small thing that's a good representation of what you need to do, then start digging in with a profiler and...
Hi @AntiSol, libvips goes to and from string for all exif values (except thumbnails), unfortunately, so you'll need to parse it. libvips has a parser for these strings, of course,...