John Cupitt
`Interpretation` is documented here: https://libvips.github.io/pyvips/enums.html#pyvips.enums.Interpretation
I made an enhancement issue for linking enum args to the relevant enum, thanks for the suggestion.
Args should link to enums now, eg.: https://libvips.github.io/pyvips/vimage.html#pyvips.Image.colourspace I credited you in the changelog.
Yes, PNG write is horribly slow. It's mostly down to libpng. What kind of image data do you want? If you need it in PNG format, there's not much else...
That's just the speed PNG is, it's a slow format. You could try JPG, it's a lot quicker. TIFF should be faster again, if you can use that. The fastest...
You need `write_to_memory`. There's an example here: https://github.com/libvips/pyvips/blob/master/examples/pil-numpy-pyvips.py#L53 That makes a simple memory array of pixel values. It'll be tricky to send over a network though -- it's supposed to...
Yes, exactly, it's just a raw memory array, they are difficult to work with. If you need type, metadata etc. you need a format like JPG, PNG or TIF.
Hello, libvips only supports the rotation orientations, not the mirror ones. I don't know of any real devices that use the mirror codes -- they only appear in test suites.
Oh, interesting, I didn't know they were really used. Sure, let's tag this issue as an enhancement. Do you have a sample image?
Hey @Gabry993, It won't be any faster, but you could probably use `similarity` rather than `affine`, eg.: ```python out = image.similarity(scale=1.2, angle=45) ``` The output image is the bounding box...