How to update UA Midi Control on your Mac

1. Let UA Midi Control update itself. Open UA Midi Control. It checks for new versions on its own, and if it has not offered one yet, look in the UA Midi Control menu, or under Help or its preferences, for Check for Updates, then let it download and relaunch.
2. Upgrade the Homebrew cask. If you installed UA Midi Control with Homebrew, open Terminal and run brew upgrade --cask ua-midi-control. Homebrew downloads the current build and replaces the app in your Applications folder.
3. Or download it from fonoflow.com. Otherwise get the current build from fonoflow.com, which is the same download Homebrew points at. Quit UA Midi Control, open the download and put the new UA Midi Control in Applications in place of the old one: a disk image is dragged across, an installer package runs its own steps. Your settings and documents live outside the app and are kept.

brew upgrade --cask ua-midi-control

That is one app. The same walk, through a different menu or page each time, is what every other app on the Mac asks of you, which is where Floodtide comes in.

Floodtide reads the same Homebrew record for UA Midi Control that the brew command above does, without needing Homebrew installed, to learn which version is current. When yours is behind, the row appears under Updates with the version it will move to and the download size. Pressing Update, or Update All, does the rest:

• The vendor's own build is downloaded, several apps at a time, with real progress.
• The download is verified against the developer signature of the installed copy; Gatekeeper must accept it before anything is replaced.
• UA Midi Control is asked to quit politely if it is open, and never forced.
• The bundle is swapped and the old version kept for seven days, so Undo Last Update always works.
• The replacement's code signature is checked; a build signed worse than the one you had is rolled back automatically.

UA Midi Control's publisher does not publish a checksum, so Floodtide verifies each download by requiring the same developer signature as the copy already installed, and Gatekeeper has to accept it before anything is replaced.

If UA Midi Control lives in a folder macOS protects, the swap asks for your administrator password once for the whole batch, exactly as the Finder does when you install anything by hand.