Successfully launched and running natively on ARM!
This is fantastic, thank you for all of your work!
Code signature + notrization results via What’s Your Sign: Screenshot.png
Is your plan to continue building without the version number in the filename? (as is normal on macOS) I ask because I’ve added the /Contents/MacOS/ folder to PATH to make scripting easier. Previously I would have to update this each time, so I consider the change a benefit 
That is our plan, yes. As I stated to touchstone64 when that question came up: I only did it like I did back then due to not knowing jack shit about macOS conventions 
You’re welcome!
To be blunt I can only take credit for updating the packaging that @mbunkus had previously created, and of course the real magic is in the functionality of MKVToolNix itself 
Homebrew users, this one’s for you:
==> Updating Homebrew…
Already up-to-date.
Upgrading…
==> Upgrading 1 outdated package:
mkvtoolnix-app 97.0 → 98.0-1
==> Fetching downloads for: mkvtoolnix-app
✔︎ Cask mkvtoolnix-app (98.0-1) Verified 39.0MB/ 39.0MB
...
==> Upgrading mkvtoolnix-app
97.0 → 98.0-1
...
🍺 mkvtoolnix-app was successfully upgraded!
==> Upgraded 1 outdated package
mkvtoolnix-app 97.0 → 98.0-1
Homebrew now supports the test ‘MKVToolNix for Mac’ packages, automatically installing the right release for your Mac, and will do so as new releases become available.
This is probably the last post for this thread: please check here for ‘MKVToolNix 99.0 for Mac’, from here on in it should be ‘business as usual’ for macOS binaries 