Skip to content

Immage 0.36.0

Choose a tag to compare

@github-actions github-actions released this 23 Oct 22:29
· 431 commits to main since this release

Downloads

macOS (Apple Silicon) Immage-0.36.0-macOS-arm64.dmg
Windows (x64) Immage-0.36.0-Windows-x64-setup.exe, or Immage-0.36.0-Windows-x64.msi
Linux (x86-64) Immage-0.36.0-Linux-x86_64.AppImage
Source immage-0.36.0-source.tar.gz

Improvements

  • Immage opens at the size and place it was closed at, and maximized if it was. On Linux under Wayland the size is kept but the desktop places the window
  • the filmstrip and the grid show a folder's photos in the order they were taken, rather than by file name
  • zooming is twice as quick, and a click, key or navigator zoom renders the sharp view while it zooms, so it is ready sooner. Zooming back to a view shown before, with nothing changed since, shows it at once. Zoomed in, the whole photo is kept sharp once rendered, so moving around it shows no blur and needs no wait
  • switching between Before and After, undoing, or putting a slider back where it was shows the photo at once when it was shown that way before, zoomed in too
  • a photo shows its thumbnail as soon as it is opened, rather than the photo before it, and the arrow keys' next photo is read ahead while the current one is open, so a compressed raw (an Olympus ORF, for one) opens about 0.3 s sooner

Bug fixes

  • on Linux, an AMD graphics card with only AMD's ROCm OpenCL driver installed is used again for the whole-photo render and export; since darktable 5.6 it was left out unless Mesa's RustiCL driver was installed instead, and with ROCm 7.1 darktable's OpenCL code did not build, so Immage ran on the CPU alone
  • on Linux with Mesa's RustiCL OpenCL driver and AMD's ROCm both installed, Immage no longer shows empty folders and a blank photo: its engine stopped at start while checking ROCm for AI acceleration, which the Linux build cannot use
  • in Before/After's left and right split, the After label lines up with Before instead of sitting lower

Installing

These builds are not signed with a developer certificate, so each system warns when Immage is opened for the first time. Updates after that install from inside Immage, without the warning.

  • macOS (Apple Silicon, macOS 15 or newer): open Immage-0.36.0-macOS-arm64.dmg and drag Immage to Applications. Open it once; when macOS says it cannot check it, go to System Settings › Privacy & Security and click Open Anyway. Or, in Terminal: xattr -dr com.apple.quarantine /Applications/Immage.app
  • Windows (x64): run Immage-0.36.0-Windows-x64-setup.exe (or Immage-0.36.0-Windows-x64.msi). When SmartScreen stops it, click More info, then Run anyway
  • Linux (x86-64, glibc 2.35 or newer, such as Ubuntu 22.04): make Immage-0.36.0-Linux-x86_64.AppImage executable (chmod +x Immage-0.36.0-Linux-x86_64.AppImage) and run it

Immage checks for a new version once a day (Preferences › About › Updates), and offers to install it.

Known issues

  • Linux with an NVIDIA graphics card: NVIDIA's driver holds Immage's window to a few updates a second, on Wayland and X11 alike (WebKit bug 303811). Immage works around it by having Mesa draw its window on the processor, when Mesa is installed, as it is on most distributions. On a fast processor that is about ten times faster, but it may be slower on a 4K screen or a slow processor; to compare, start Immage with __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json for NVIDIA's own drawing. A real fix has to come from NVIDIA's driver or WebKitGTK
  • Linux on Wayland with fractional scaling (125%, 150%, ...): sliders can be 2-3 times slower to update. The web view Immage is built on draws such a window at 200% and the desktop shrinks it, so it draws far more pixels than the screen shows. At 100% scaling, or started with GDK_BACKEND=x11, it is about as fast as elsewhere

Source

immage-0.36.0-source.tar.gz is the source of this release: Immage, with darktable and Immporter at the commits it was built from. The libraries bundled from Homebrew, MSYS2 and Ubuntu are listed in Preferences › About with the version shipped and where their source is published. For at least three years after this release, anyone may also ask for the complete source of any GPL or LGPL library in these binaries, at the version shipped, free of charge: open an issue at https://github.com/Rhettus/immage/issues.