Larger images now supported on Windows
Blurity no longer limits images on Windows to 24 megapixels. We heard this complaint time and again, with increasing frequency as high-pixel-count cameras became more common. Fundamentally, the problem was memory: Blurity requires a very large amount of memory to process images. The newest version of Blurity, at least on Windows, resolves the problem.
That limitation had been in place because Windows prevents 32-bit applications from allocating more than 2 GB of memory. Starting in version 1.4.167, the core deconvolution code is built as a 64-bit application, allowing it to use a virtually unlimited amount of memory. All that is required is enough RAM and a 64-bit version of Windows.
An informal survey of Blurity users showed that almost all have more than 2 GB of RAM, with 4 GB and even 8 GB being relatively common. A handful even had systems with 16 GB or more of RAM. Blurity can now make use of all of that extra space. On a system with 16 GB of RAM, Blurity should (in theory) be able to handle a 267 megapixel image.
If your system has less than the recommended amount of RAM (i.e., less than 4 GB of RAM), or you’re using a 32-bit version of Windows, Blurity now has better logic about when to sacrifice performance for the sake of image size. Therefore, large images on those systems have a higher probability of being processed, albeit at a slower speed relative to systems with the recommended amount of memory.
One other major improvement in version 1.4.167 of Blurity is that processing is roughly 10% faster than 1.4.165.
The Mac version of Blurity is still built as a 32-bit application, but because Mac OS X allows 32-bit applications to allocate up to 4 GB of memory, the size limit has always been higher: at least 33 megapixels, possibly more. The speed and small-memory optimizations will be released soon, so watch for a new 64-bit version for the Mac.