Is there a place where newer Windows builds can be found?

No worry, I hope you enjoyed your travel.

Was it for pleasure or business (or maybe a combination :-S) ?

uploaded at

I travelled with friends during one month in the north of Madagascar. Very interesting but also tiring due to the roads and tracks conditions. Powerty is increasing compared to our last travel 3 years ago.



Madagascar sounds nice. I hope you got good pictures there :smile:


When I open this the about page shows V. 0.5.0 Which happens to be identical to what is shown when I open my already installed version downloaded and installed around a year ago from here: HDRMerge

Are they identical, as the “about” window leads me to believe, or are there actually changes and the “about” info just not updated yet?

I haven’t checked in a while but last time it wasn’t the same. There have also been some commits on a branch and I don’t know whether they have been integrated.

For nightly builds, the only meaningfull information about configuration is provided by the file name, for instance:

Branch: master
tag: continous
64: 64 commits form tag
g1408e42: 1408e42 hash from last commit
release: release build
64: 64 bit windows

The about window informations are not automatically updated with git configuration informations as it is done in Rawtherapee. Same for window title.

As far as I know, cacorrect branch is not merged into master branch.
Thoses branches include last commits.

Would be lovely to have another recent Windows build. There are several known issues which may be fixed in the meantime (e.g. the broken JPEG preview in the DNG due to upgrading Qt from v4 to v5).

uploaded at
HDRMergeNightlyBuilds/ –

It’s the last version I found.
Edited, thanks @LigH-de

Almost: HDRMergeNightlyBuilds/ – (“Merge” was missing in the URL)

Thank you!

PS: Unfortunately, this build does not yet contain the fix for the broken JPEG preview in the DNG. The output seems to be identical with continuous-64.

I will recheck in the HDRmerge repo if I find newer commit, but I doubt.

have you a link describing the fix or the issue?

This one?

SHA-1: 6c892cbb3ae2f7176d72ab3ee7cab42d711285ec

  • Fix wrong format “JPEG” for writing the preview.

The commit is included in

@LigH-de Are you sure you downloaded the build identified just above?

@heckflosse If it is a v0.6 version, why it is identified v0.5 in the window banner? If it is a stable version, could it be tagged 0.6 or if you prefer v0.6?

I am really sure, yes.

HDRMerge_master_continuous-64-g1408e42_release_64\hdrmerge.exe (2019-07-25, does not contain the string “JPG”) => DSCF4758-4758.dng (13056040 bytes, does not contain the string “JFIF”)

HDRMerge_release-v0.6_continuous-71-gd7d8041_release_64\hdrmerge.exe (2020-02-24, contains the string “JPG” once) => DSCF4758-4758.dng (13056040 bytes, does not contain the string “JFIF”)

Seems the patch is not the fix?

That seems so!
Then could you open a bug report at Issues · jcelaya/hdrmerge · GitHub

For help writing it, see How to write useful bug reports - RawPedia

I will possibly rather ask to reopen the already existing issue.

1 Like

@gaaned92 the imageformat plugins are missing in the zip.
An for jpeg support the jpeg plugin (libqjpeg) is needed.

For Windows, this will be a qjpeg.dll like in Luminance HDR.

I copied that DLL over to a subdirectory imageformats below the HDRMerge installation, and it created a DNG file containing a JPEG preview. You will prefer to deploy a current version from your QT 5 installation for future releases.

1 Like

I sort of messed up the build. Contrary to other SW I build with QT (filmulator, luminancHDR), there was no complaint about missing items.
correcting that error.

edit: It’s the problem with QT plugins. They are not managed by windeployQT.exe and I don’t know how to identify required plugins.

Build is corrected. Could you test?
thanks @LigH-de and @ff2000

1 Like

All of the links above seem to be gone. Is there any other place we can find Windows builds, or is someone willing to share once again? I’ve tried building myself briefly, but I have very limited skills in both Windows development and cross-compilation, so I’ve had no success so far.