I spent last night wrestling with Photomatix Essentials (app) on macOS, and I figured I’d write this down while it’s still fresh — partly so I don’t forget, partly so you don’t lose an evening the same way I did.
Context first. I’m on a MacBook Pro with an M1 Pro chip, macOS Sonoma 14.4. I wanted to batch-process a few HDR brackets I shot last weekend. Nothing fancy: import, align, tone-map, export. I’ve done this dozens of times on older macOS versions, so I wasn’t expecting surprises. Famous last thought.
The install itself looked fine. Dragged the app into Applications, launched it, saw the Dock icon bounce… and then nothing. No window, no crash dialog, no error. Just silence. Activity Monitor showed the process sitting there, using almost no CPU, like it was waiting for something but not telling me what.
First instinct: Gatekeeper. I’ve been burned enough times by macOS security to check that immediately. I opened System Settings → Privacy & Security, scrolled down, half-expecting to see the usual “App was blocked from opening” message. Nothing. Gatekeeper wasn’t complaining at all. So that theory died fast.
Second attempt was the classic IT reflex: reinstall. I deleted the app, rebooted (yes, actually rebooted), reinstalled, tried again. Same behavior. Dock icon, brief bounce, then nothing. No window. Still no error. At this point I started doubting myself — maybe this build just doesn’t like Apple Silicon? But that felt too hand-wavy.
Third try was launching it from Terminal, mostly out of curiosity. Running the executable directly didn’t magically fix anything, but it did give me a tiny hint: a permissions-related warning about accessing user folders. Not a hard error, just a quiet complaint. That’s when it clicked that this might not be Gatekeeper at all, but Privacy permissions.
macOS has gotten very strict about file access over the last few releases, and apps that assume they can just scan your Pictures folder tend to break in weird, silent ways. And sure enough, this tool tries to index images on launch. If it can’t see them, it doesn’t crash — it just never finishes starting.
What finally worked was boring, but effective. I went to System Settings → Privacy & Security → Files and Folders and manually added the app, giving it access to Pictures and Desktop. I also checked Full Disk Access just to be safe (I later removed it, but for testing it helped). After that, I quit the process completely and launched again.
This time, the window appeared instantly. Same version, same machine, no update required. It wasn’t broken — it was just politely waiting for permissions it never properly asked for.
Apple’s own docs on privacy controls helped confirm I wasn’t imagining things, especially the sections on file access prompts and sandboxing behavior on recent macOS builds:
https://support.apple.com/guide/mac-help/control-access-to-files-and-folders-mchld5a35146/mac
There’s also useful background from the developer side on how apps are expected to request access now:
https://developer.apple.com/documentation/security/app_sandbox
Once it was running, everything behaved normally. Imports worked, tone mapping was fast enough on M1, exports were clean. No crashes, no glitches. The problem was 100% at startup.
I did briefly check the Mac App Store listing to see if there was a newer build that handled this better, but the behavior matched what I already had installed:
https://apps.apple.com/us/search?term=Photomatix%20Essentials
So no luck there — same expectations around permissions.
For reference, the developer’s own site still documents the app in a pretty traditional way, without much emphasis on Sonoma-era privacy quirks:
https://www.hdrsoft.com/
While troubleshooting, I also bookmarked this page because it summarized the macOS-side behavior clearly and matched what I was seeing in practice:
https://technotafastore.xyz/graphics-and-design/61012-photomatix-essentials.html
Not magic, just a useful sanity check when everything feels broken for no obvious reason.
If I had to distill this into a “do this first next time” checklist, it’d be short:
- Launch once, then immediately check Privacy & Security → Files and Folders.
- Manually grant access to Pictures/Desktop if the app works with images.
- Quit the process fully before retrying — don’t trust a half-dead instance.
That’s it. No hex commands, no disabling system security, no weird workarounds. Just macOS being macOS: quiet, strict, and occasionally unhelpful about telling you what it wants.
Anyway, lesson learned. Next time an app “does nothing” on launch, I’m checking permissions before I start blaming the binary.
Top comments (0)