John Cupitt
John Cupitt
Could you post a sample image? It'd help me understand exactly what you're working with.
Wow that's a pretty crazy pyramid, I've not seen one like that before. I wish manufactures would follow conventions :( ``` $ for i in {0..44}; do echo -n "page...
Hello @sinamcr7, 1. I think I'd use Q=85, that's roughly what slide scanner companies use. You could possibly use 512x512 tiles, though 256x256 is a good choice. 1024x1024 is probably...
I've just realised you already have the entire image in memory as a numpy array, is that right? In which case you can simply do: ```python image = pyvips.Image.new_from_array(big_numpy_array) image...
I'd stick to opencv if your code is working. pyvips ought to be able to make the pyramidal tiff directly from the numpy array with only a relatively small amount...
Sorry, no, array resize needs to reallocate memory, and that means it must double. You could change to a tiled array. Cut your image into eg. 1024x1024 tiles and keep...
... though a tiled array will make save difficult, of course. I've built several imaging systems like this. I've always done it in two stages: first, scan the camera over...
The scanners I've made have driven the stage in an approximate grid, then examined the overlaps to find a set of exact offsets. The set of offsets are an overdetermined...
Ah OK, I've never tried with a manual stage, I agree that would need a different approach. Other friends have made interactive scanners using a manual stage, but I don't...
8.15.1 fixed that bug, so Q100 should be fine.