Automated Builds

Here you can download automated builds of HDRMerge - these include both stable releases and development builds.

How do development builds compare to stable builds? New "development" builds are created automatically every time the code changes, and once enough new features and bug fixes accumulate we release a new "stable" version. Any bugs found in the latest stable version will be subsequently fixed in the development builds which follow, and these will accumulate until the next stable release, and so on. These development versions are also where we improve existing features and add new ones, though it takes time to polish them and to make sure they work well out of the box. On the one hand, development versions always have the highest number of bugs fixed, but on the other hand the new features in these versions may be rough and unpolished and introduce new bugs. If you want to try out new features and don't mind the risk of encountering potentially critical bugs then get the latest development build. For general use we recommend the latest stable release which gives you a generally more polished experience.

How do you read and make sense of the development builds' names? The filename has roughly this structure:

HDRMerge_branch_tag_commit_date.extension

• Code changes happen often, and each code change is referenced by a unique hash number in the commit - it looks like this: d9ad93c15.
• Each commit happens on a "branch". The main branch is called master. New features are developed on their own branches, and then merged into master when ready.
• The "tag" is the human-friendly version of the latest release, e.g. v0.6.

HDRMerge v0.5

Features:

• First Mac OS X build! Thanks to Philip Ries for his help.
• Several bug fixes:
  • Fix dealing with images with non-ANSI file names.
  • Calculate response function with non-linear behavior.
  • Fix file locking issues by transfering Exif tags in memory.
  • Correctly calculate the response function of very dark images.

HDRMerge v0.4.5

Features:

• Better compatibility with other programs, by producing a DNG file that maintains the original layout: frame and active area sizes, black and white levels, etc. Note that, if you use RawTherapee, you need v4.1.23 or higher to open these files.
• Batch mode in command line! Merge several sets of HDR images at once.
• Creation of menu launchers and a Windows installer.
• Support for CYGM and Fujifilm X-Trans sensors (experimental).
• Several bug-fixes.
• Improved accuracy and performance.

HDRMerge v0.4.4

Features:

• Better support for more camera models.
• Better rendering of the embedded preview image.
• Change the edit brush radius with Alt+Mouse wheel.
• Several bugfixes.
  • The original embedded preview is not included in the output anymore.
  • Fixed some glitches with the edit tools.

HDRMerge v0.4.3

Features

• Fix segmentation fault error painting the preview of some rotated images.
• Fix DateTime tag in Windows hosts.

HDRMerge v0.4.2

Features:

• Improved GUI:
  • A slider to control the brush radius.
  • A slider to control the preview exposure.
  • Movable toolbars.
  • Layer selector with color codes.
  • Improved brush visibility on different backgrounds.
  • Posibility of saving the output options.
• First release with a Windows version, both 32- and 64-bit.

HDRMerge v0.4.1

Features:

• Buf fixes.

HDRMerge v0.4

Features:

• Great performance improvements with OpenMP.
• Not depend anymore on DNG & XMP SDK! Windows and Mac version soon...
• More robust MBT alignment.
• More control on the logging output.
• The user may disable alignment and/or cropping. This is most useful to obtain an image of the same size as the inputs. Some programs have this requirement to apply a flat-field image, for instance.

HDRMerge v0.3

Features:

• Supports any raw format supported by LibRaw.
• Automatic alignment of small translations.
• Automatic crop to the optimal size.
• Automatic merge mask creation. The mask identifies the best source image for each pixel of the output.
• Editable merge mask, to manually select pixels from specific source images.
• Writes DNG files with 16, 24 and 32 bits per pixel.
• Writes full, half or no preview to the output image.
• Copies the EXIF data from the least exposed source image.