Archive for the 'Release' Category

This release introduces a few new features: automatic anti-ghosting, FITS support, integration with Windows Task Bar, improved I/O with TIFF 32 bit (which will make possible to export to third party software for high-quality post processing), redesigned merge algorithms.

Of course, because we have so many new features out on the table, we are aware that we might have a lot of bug reports: please use our Tracker and we will try to tackle them as soon as possible.

Minimum requirement for Luminance HDR is a CPU that supports SSE2.

For Mac OS X users, Luminance HDR has been compiled on Maverick (10.9) and should be compatible with Mac OS X 10.8 as well.

If you spot any bug, or you want to suggest a new feature, please use our Tracker.

If you appreciate Luminance HDR, please consider a donation (there is no minimum amount!):

If you want to share with other users your results, you can use our Flickr group and Facebook group.

For advanced users: if you want to compile your copy of Luminance HDR, please note that Luminance HDR requires Qt5 from this version onwards. If for some reasons you cannot install Qt5 on your platform, we have reports of Luminance HDR running smoothly on Linux under Wine 1.6.1.

We are pleased to announce Luminance HDR 2.3.1, an improvement release for Luminance HDR.

It’s a long time since version 2.3.0: unfortunately 2012 has been a really busy year for all of us in the development team, so we couldn’t dedicate much time to the project. However, we are now up to speed and we will try to push releases more often, with new features.

This release introduces some work made by Franco on the antighosting mask: he is absolutely looking forward to receive your feedback on that, so that he will improve it even further.
There are also other improvements in the processing engine (a long refactoring that has been my – Davide – company for almost a year, and will continue probably as much as that). Ideally, a new processing engine will allow more flexibility, hence new functionalities and improvement to be release more often. At least, this is the aim.
On top of that, Daniel is continuing his amazing work on Windows, with the introduction of a portable mode (yes, put your Luminance HDR on a USB drive!) and an update checker, to notify all the user a new release is available (we just make sure you don’t miss Luminance HDR 2.3.2!).

Minimum requirement for Luminance HDR is a CPU that supports SSE2.

For Mac OS X users, Luminance HDR has been compiled on Mountain Lion (10.8), so it might not work on early systems. I am currently try to build a virtual machine based on Snow Leopard, where I can build Luminance HDR also for older systems: I’ll try to make it happen as soon as possible, promise!

If you spot any bug, or you want to suggest a new feature, please use our Tracker.

We are pleased to announce Luminance HDR 2.3.0, a shiny new major release with important new features, than completes the progress of the beta version of 8 weeks ago.

Thanks to the important work made by Franco and Daniel, this new release brings into Luminance HDR a brand new colour management system, improved JPG, TIFF and PNG readers and writers and a new image alignment tool for RAW files as well (plus many other small changes). Since the beta1, minor flaws and bugs have been fixed. Moreover, we ported the new colour management system from LCMS to LCMS2.

Thanks to the work of our contributor Tino Kluge, Luminance HDR 2.3.0 has now got a size independent implementation of the Fattal operator. I would never thank enough Tino for this patch!

Minimum requirement for Luminance HDR is a CPU that supports SSE2.

If you spot any bug, or you want to suggest a new feature, please use our Tracker.

We are pleased to announce Luminance HDR 2.3.0-beta1, a major release with important new features.

Thanks to the important work made by Franco and Daniel, this new release brings into Luminance HDR a brand new color management system, improved JPG, TIFF and PNG readers and writers and a new image alignment tool for RAW files as well (plus many other small changes).

Minimum requirement for Luminance HDR is a CPU that supports SSE2.

If you spot any bug, or you want to suggest a new feature, please use our Tracker.

We are pleased to announce Luminance HDR 2.2.1, a minor release with a few bug fixes.

For all the Windows users, TIFF support is now fully working again. Moreover, we also decided to split the GUI and the CLI into two independent executable: for those who use the CLI often, you have to use the new luminance-hdr-cli executable. This choice has several positive sides: Luminance HDR starts on Windows in a blink of an eye now, while the CLI is finally available on Mac OS X as well.

Just because we had a couple of bug reports in the past weeks, Luminance HDR requires at least SSE2 to work properly.

If you spot any bug, or you want to suggest a new feature, please use our Tracker.

A long time has passed since the last Luminance HDR (2.1.0), however we did work a lot on it, both on the user interface and on the internal engine. We do have great ideas of how to improve it even more, so we decided to give you the effort of around six months of work while we continue working on it.

If you spot any bug, or you want to suggest a new feature, please our Tracker.

If you appreciate Luminance, please consider a donation (there is no minimum amount!):

If you want to share with other users your results, you can use our Flickr group and Facebook group.

Note [Mac Users]: As the previous version, we have phased out support for 32 bit on Mac OS X. At the same time, we phased out support for Mac OS X Leopard as well, so you will need at least Snow Leopard to use Luminance HDR 2.2.0.

We are pleased to announce a new version of Luminance HDR. We are changing Luminance HDR deeply, re-factoring a lot of the legacy code. We are trying to add new features and at the same time take out the maximum from new multicore machines using new development techniques. This version is absolutely a big improvement for Windows users, which will experience a more stable and faster software. I do not want to list all the changes we made for this version, it will be too long, but we are definitely waiting for your comments in order to bring out a version 2.1.1 really quickly with all the improvements and the bug fix that Luminance HDR may require.

Note [Mac Users]: This version of Luminance HDR runs only with Mac OS X 10.6 Snow Leopard and Mac OS X 10.7 Lion, in 64-bit native. We do not think to release a 32-bit version anymore, so Mac OS X 10.5 users should stick to the old version.

Luminance HDR is growing, improving and leaving behind some of its historic problem: memory hungriness and unexpected faults. I am trying to sort out as many problem I can and, at the same time, I am getting a lot of patches from really smart guys that I will never thank enough. Most of the work in this new version has been made “under the hood”, so you will not see any drastic change in the UI (which is good… and bad!).

Changes [compared with 2.0.1, while some of them were already present in the 2.0.2-pre1]:

LibRAW is now in charge to convert RAW files, removing the dependency from dcraw as an external tool (Thanks to Franco Comida)

New Batch Tonemapping Engine

Smaller memory footprint during the TM process

Better acquisition/release of the memory

[Windows only] improved responsiveness of the UI

[Windows only] update of some of the dependencies

[Mac only] Luminance HDR 2.0.2 works on Mac OS X 10.5.X (64 bits version for Snow Leopard also planned, but not yet released)

I would also thank a great Luminance’s user, Ron Todd, who made available for all of us his experiments with the new LibRAW engine and blowing highlights (I strongly suggest you to read it!).

My current “To Do” list is too long to fit in here, but while I am releasing this version, I am playing with the Intel TBB library (Threading Building Blocks) and I am probably going to introduce a new dependency in the next version. At the same time, as I am already discussing in a previous blog post, the project will most likely switch to CMake, leaving QMake.