Nicely put @corticalcode 
I’ll finish the automation then link to the Github repo here. I’ll most likely add the disk image(s) to the Github releases and will also host a copy myself. Changes to build.sh to enable notarization will be patches in my repo for now, hopefully they can be added to the mkvtoolnix repo if suitable. I’ll raise a pull request when it’s done.
It would be great if you could release your version and possibly future versions as well.
I think many MKVToolNix users—myself included—don’t have the ability to do this work. I, for one, am very grateful to people like you and corticalcode who make it possible for others to continue using this wonderful tool on an ARM Mac!
Ah, that’s a whole other process I hadn’t been aware of until now. That’s the only reason I hadn’t done that for the binaries I used to provide.
Here is a copy of the notarized disk image of MVKToolNix GUI 98.0 for Apple Silicon (ARM64), for testing purposes.
I’ve installed and tested it on macOS 26.4.1 and 15.7.5, but I don’t have access to 13.x or 14.x installations. (MVKToolNix GUI 98.0 should run on those versions too, I might create a quadruple-boot Mac to test all four…)
Any reports of success or failure will be very gratefully received!
Hello!
I’ve now finished adding automated notarization to the repo, released it as v1.0 and submitted a pull request to the mkvtoolnix repo in the hope that my installation script patches become part of the main source.
The repo is public and can be found on Github.
Edit: links are intentionally broken, please see my next post.
The notarized disk image can be downloaded from the Github v1.0 release or my own hosted copy should that be unavailable. They’re the same file.
Hope this helps! Any reports of success or failure will be gratefully received 
Hi folks,
I’ve updated the Github repo to v1.1 and deprecated the previous disk images as I had the wrong git clone command in my script. Instead of cloning the tag release-98.0 it was cloning the whole repo into a directory called release-98.0. This meant that the disk images contained up-to-date builds, i.e. including changes made since 98.0 was released 
I’ve corrected my error and released v1.1 which includes a notarized disk image that actually includes MVKToolNix GUI 98.0. The image can be downloaded from the Github v1.1 release file or my own hosted copy should that be unavailable.
Sincere apologies for wasting your bandwidth, normal service will be resumed as soon as possible.
The git clone problem went deeper than I thought: the disk image in v1.1 was built with Qt 6.11 instead of Qt 6.10
It will have been fully functional but I’m a stickler for detail so I’ve addressed the issues, updated the Github repo to v1.2 and rebuilt the notarized disk image from scratch so that it matches Release 98.0 exactly.
The disk image can be downloaded from the Github v1.2 release file or my own hosted copy should that be unavailable.
‘Fail fast’ is a good maxim but ‘embarrass yourself in front of a new community’ is what I’m trying to reconcile myself with today 
I’ve learned a lot this week and it’s only Tuesday.
Hope this helps!
Don’t worry. Any maintainer who’s been at it long enough has gone through borked releases multiple times, including myself 
If the app is signed and notarized you may consider integrating the sparkle framework for easier updating.
It’s an interesting idea
However, I’d suggest one of the major benefits of the tool is that it is functionally identical across all platforms, and Sparkle targets macOS exclusively. The Apple Silicon builds we’re producing don’t affect the functionality, just the packaging.
I’d also miss the song choices of the ‘Help | Check for updates’ mechanism
Hi folks, I’m very happy to let you know that a notarized, universal binary of 98.0 is running just fine in ‘native’ mode on Tahoe 26.4.1. The same app, launched via Rosetta 2, also appears to be completely stable. Just a lot slower to load
Many thanks to @corticalcode for patiently creating and testing the Intel builds that are supporting these proof-of-concept tests.
I’m using this thread to document progress until it’s in a fit state to release
Signed up just to say thank you to @corticalcode !
ARM version working fine here 
Hi @devtimi,
You’re welcome. I really appreciate the feedback and I’m pleased that my build is working for you. I would like to ensure that the real credit goes to mbunkus for making MKVToolNix (CLI & GUI), even more so for his role in the Matroska project. I would say, at this time, what most strikes me, is his active participation in discussions and his personal responses to matters simple and complex.
I’d also like to credit others who had been building macOS versions of the GUI like Ryu67 and Touchstone64. The really exciting news is that @Touchstone64 has created Apple notarized versions of the MKVToolNix macOS GUI. I cannot say enough about it. The Apple notarized version will make it possible to release on Homebrew as an official cask and most importantly it can be installed without needing any bypass of macOS’s Gatekeeper system.
As for me, I will continue to do my bit, vibe out overengineered build scripts, and perchance a functional DMG or two.
Happy remuxing!
I was concerned because the notarized motivation seems to be intel preservation. I don’t mind using Sentinel to un-quarantine and ad-hoc sign an ARM build. I prefer your self-contained non-homebrew ARM version to the other options.
But absolutely thanks go to the original author!
Totally off-topic but @corticalcode this one’s for you! This is a video I took of my daughter once I’d indoctrinated her into the lore of … a certain film … and we visited … a certain castle … together
FYI @devtimi the notarization changes are really for the Apple Silicon releases, taking advantage of Apple’s service to ensure there’s no malicious code in the binaries. Right now the Intel releases get the same treatment but notarization will become more critical as macOS evolves and Intel releases get left behind. (Which I don’t agree with and is why I’ve invested in an Intel Mac so I can continue to create notarized MKVToolNix packages for that platform, too.)
The packages served by Homebrew are the same ones served by the MVKToolNix site so they’ll become easier to use – and, critically, not deprecated come September – once notarization is in place. The plan is that – thanks to @mbunkus’s generosity – the notarized packages will also be served from the MVKToolNix site.
I suddenly feel the need to … 
I’m so glad to hear you’ll be notarizing a native ARM version 
So to confirm for my own peace of mind, the ultimate plan/goal is to offer a standalone self-contained notarized version? I’ve loved using MKVToolNix thus far.
I’m very happy to report that the MKVToolNix 98.0 for Mac packages are complete and available for testing
TL;DR here are the links : Apple Silicon (sha-512), Intel (sha-512) and Universal (sha-512).
The Universal package will run on any Mac running macOS 13 (Ventura) or later, but if you know which kind of Mac you have, the Apple Silicon and Intel packages are smaller. (At the end of the day the Universal package includes both the Apple Silicon and Intel packages and executes the right one for your Mac when you run it. So you will get the same binary at run-time.)
I’ve tested the packages as much as I can with my limited hardware, if any of you have the chance to test the package that you prefer and let me know of any issues - or that there are no issues at all! - I’d be really grateful.
The packages are 100% built from source, signed by me and notarized by Apple (so no malicious content).
Possibly the only difference you will notice is that the app is now called MKVToolNix.app, the version number is no longer included in the app name. Oh, and the Apple Silicon release is rather … snappy.
@mbunkus is very kindly hosting the packages and will continue to manage MKVToolNix releases as he sees fit. I will merely build the ‘…for Mac’ packages and submit them for approval.
Enjoy!
Now that’s what I call timing™ If you have the opportunity @devtimi please feel free to grab the package (sha-512) and test it out! All feedback welcome, I want to get this right