The crash listed as a known issue in 0.4.0 is fixed — along with a second one nobody had reported, found while looking for the first.
Updating
A 0.4.0 installation offers this release by itself: it checks at startup, downloads in the background, and installs when you quit. Nothing to do by hand. Coming from 0.3.0 or earlier, download below and install as before — from 0.4.0 onwards MatteLoop updates itself.
What is new
Quitting no longer ends in a crash report. Quitting while work was still running let Qt destroy a thread that had not stopped yet, and Qt aborts the process when that happens. Shutdown now waits a bounded five seconds for each worker; if one outlives that, MatteLoop records it in the log and exits cleanly instead of aborting. A clean shutdown is never shortened, and no worker is ever killed mid-frame — the wait for a model download, which had no limit at all, is now bounded too, so a stalled download can no longer turn Quit into a silent hang (#142).
The segmentation runtime's telemetry is switched off. ONNX Runtime ships with Microsoft's telemetry SDK compiled in, which collected diagnostic information about the machine at startup and sent it on. MatteLoop now switches it off before the runtime starts, so nothing is gathered and nothing is sent (#145). The same SDK was behind a second crash at quit, which goes away with it.
Diagnostic entries written by earlier versions stay in the runtime's own local store. With the switch in place nothing new is added and nothing is uploaded.
On Windows the runtime writes a single startup entry to Windows' own event tracing before anything can intervene. It records version numbers and similar build details rather than anything identifying the machine, and whether it goes any further is governed by your Windows diagnostic data settings. Everything after startup is switched off there too, and the README now describes this per platform.
Windows shows the application's own name. The title bar read MatteLoop 0.4.0 - MatteLoop; it now reads it once. The file properties showed a product name of matteloop and a description of matteloop.exe, both derived from the filename; they now carry the application's name, a description and a licence line (#133).
Installing
The builds are unsigned by decision, so both systems warn on first launch:
- Windows — SmartScreen: choose More info, then Run anyway.
- macOS — the first launch is refused. Open System Settings → Privacy & Security, find the message naming MatteLoop, and choose Open Anyway. Move the application to your Applications folder before launching it; an app left in Downloads may run from a read-only copy and then cannot update itself.
~/Applicationsworks just as well and is the better choice without administrator rights.
MatteLoop never needs administrator rights to update itself. If such a prompt ever appears, the application is installed somewhere you cannot write: cancel it and install the new version by hand.
Assets
MatteLoop-v0.4.1-macos-arm64.zip for macOS 15+ on Apple Silicon; MatteLoop-v0.4.1-windows-x64-Setup.exe or MatteLoop-v0.4.1-windows-x64.zip for Windows x64. The .nupkg packages and releases.*.json feeds are what the updater reads — you do not need to download them.
The MatteLoop-*-sources-* archives are the complete corresponding sources for the LGPL libraries (FFmpeg, libwebp, Qt) inside the application, published here as their licences require. They are not needed to run MatteLoop.