If you're on a Mac, this is the release you want. Every macOS build before this one — including v0.4.2 — throws Apple's "Apple could not verify this app is free of malware" warning on launch, with no obvious way past it. That's fixed, and it was my fault, not Apple's.
What was wrong
The app was genuinely signed with a Developer ID and genuinely notarized by Apple — that part was true, and the notarization came back Accepted on every build. But it was shipped as a loose Unix executable in the disk image instead of a proper .app bundle, and Gatekeeper refuses to approve a bare executable no matter how well it's signed. Its own verdict on the v0.4.2 download:
spctl → rejected (the code is valid but does not seem to be an app)
There was a second half to it. A notarization ticket can only be attached to a bundle, a disk image, or an installer — never to a loose binary. The ticket was stapled to the .dmg, so the moment you dragged the contents out, the thing you actually ran had no ticket attached to it at all.
Net effect: a correctly signed, correctly notarized build that still couldn't open. The README promised "signed + notarized, opens clean" and delivered two out of three.
What changed
- macOS now ships a real
nam-a2a1-converter.app. Open the dmg, drag it to Applications, launch it. No warning, no right-click-Open trick, no trip to System Settings. - The notarization ticket is stapled to the app itself, not just to the disk image — so it stays verified after you copy it out, and it verifies offline.
- The build now checks Gatekeeper's actual verdict before publishing and fails the release if it isn't
accepted … source=Notarized Developer ID. This class of bug shipped because nothing ever asked macOS what it thought; now the release can't be cut unless it passes.
Nothing about the conversion changed. Windows and Linux builds are unaffected — same as v0.4.2 in every respect.
Already downloaded v0.4.2 on a Mac? Delete it and take this one. If you'd worked around the warning and it's running fine, there's no urgency — the app was never actually unsafe, it just couldn't prove it.
Downloads
| Platform | File |
|---|---|
macOS (signed + notarized .app) |
nam-a2a1-converter-macos.dmg |
| Windows | nam-a2a1-converter-windows.zip |
| Windows + NVIDIA | nam-a2a1-converter-windows-cuda.zip.001 and .002 |
| Linux x86_64 | nam-a2a1-converter-linux-x86_64.tar.gz |
| Linux x86_64 + NVIDIA | nam-a2a1-converter-linux-x86_64-cuda.tar.gz.001, .002 and .003 |
The CUDA bundles ship as numbered parts because GitHub caps one release file at 2 GiB:
cat nam-a2a1-converter-linux-x86_64-cuda.tar.gz.0* > nam-a2a1-converter-linux-x86_64-cuda.tar.gz
sha256sum -c --ignore-missing nam-a2a1-converter-linux-x86_64-cuda.tar.gz.sha256
tar -xzf nam-a2a1-converter-linux-x86_64-cuda.tar.gzWindows: download get-cuda-build.ps1 and run powershell -ExecutionPolicy Bypass -File get-cuda-build.ps1, or copy /b the two parts together by hand. Full detail is in the v0.4.0 notes.
Requires an NVIDIA card of compute capability 5.0+ with a current driver. Apple silicon uses its GPU automatically — nothing to download. Windows is still unsigned, so SmartScreen warns — More info → Run anyway.