← Help Center

Getting started

Install Um Out on macOS or Windows

Um Out has two parts that install together: a small companion engine that runs on your computer, and a panel that opens inside Premiere Pro. This guide walks through both, plus the first-run checks and the fixes for the issues we see most often.

Um Out is not code-signed yet, and your computer will say so. On Windows you will get a blue “Windows protected your PC” box; on macOS, a message about an unidentified developer. That is the operating system telling you it has never seen this publisher before, which is true — it is not a virus warning, and nothing has scanned the file and found something wrong. What the warnings look like and how to get past them is written out below, including how to check that the file you downloaded is the file we built. A signing certificate is on the way; nothing about the price depends on when it lands.

Before you start

Check that your machine meets the basics. Um Out targets recent, supported versions of Premiere Pro and both current desktop operating systems.

  • Premiere Pro: a supported recent version, with at least one project and an open sequence to work on.
  • Operating system: macOS 13 or newer, or Windows 10 or 11 on 64-bit hardware. The download page states the processor each macOS build supports — an Apple silicon build will not run on an Intel Mac.
  • Disk space: roughly 2–4 GB free for the engine, its dependencies, and the on-device models.
  • Permissions: on macOS the installer asks for an administrator password, because the engine is installed for every user on the machine. On Windows it installs into your own user folder and asks for nothing.

Step 1: Download the installer

Sign in and open your download page. Take the file for your operating system, and only from there — an Um Out installer from a mirror, a forum post or a search-engine advertisement is not one we built.

  • macOS: a .pkg named like UmOut-0.1.0-macos.pkg.
  • Windows: an .exe named like UmOut-Setup-0.1.0.exe.

One file per platform. It carries the companion engine and the Premiere panel together, so there is nothing else to fetch.

Step 2: Get past the unsigned-software warning

Code signing is a certificate that tells Windows and macOS who published a file. Um Out does not have one yet, so both systems show a warning the first time you run the installer. Here is exactly what you will see, and what it does and does not mean.

Windows: “Windows protected your PC”

A blue box appears with a Don’t run button and, in small type at the top, a More info link. There is no Run anyway button until you click More info — that is the step almost everyone misses.

  1. Click More info. The publisher will read Unknown publisher. That is expected: it is what an unsigned file always says.
  2. Click Run anyway.
  3. Accept the licence terms and finish the installer.

This screen is SmartScreen, and it is about reputation, not infection. It appears for every new publisher until enough people have installed the file without incident, and it would still appear on the day one of our builds was genuinely broken. So do not treat clicking through it as a safety check. The safety check is the next paragraph.

macOS: “cannot be opened because it is from an unidentified developer”

  1. Double-click the .pkg. macOS refuses it.
  2. Ctrl-click (or right-click) the file and choose Open, then Open again in the box that follows. If that option does not appear, go to System Settings → Privacy & Security, scroll to the message about Um Out being blocked, and click Open Anyway.
  3. Enter your administrator password when the installer asks, and follow the prompts.

Check the file is the one we built

Every download on the download page is listed with a SHA-256 checksum — a fingerprint of the exact bytes. If your copy produces the same fingerprint, it is our file and nothing has altered it in transit. That is a stronger guarantee than any warning box, and it takes one command.

  • Windows (PowerShell): Get-FileHash .\UmOut-Setup-0.1.0.exe
  • macOS (Terminal): shasum -a 256 ~/Downloads/UmOut-0.1.0-macos.pkg

Compare the result with the checksum next to the download. If they differ, stop and tell us — do not install it.

Step 3: Finish the install

  1. Let the installer put the engine in its default location unless you keep tools on another drive.
  2. When asked, allow Um Out to install its local engine and model files.
  3. Finish the installer and open its diagnostics screen to confirm the engine is running.
The companion engine does the heavy local work: silence detection, media inspection, and supported transcription. Keep it installed even if you plan to use hosted AI later.

Step 4: Add the panel to Premiere Pro

The installer places the Premiere panel for you. To load it:

  1. Quit Premiere Pro completely if it was open during install, then reopen it.
  2. Open a project and a sequence.
  3. Go to Window → UXP Plugins → Um Out. Um Out is a UXP panel, so it is not under Window → Extensions — that menu is for the older CEP extensions and Um Out will never appear there.

If Um Out is not in the menu, see Troubleshooting below.

Step 5: First run and activation

The first time the panel opens, it runs a quick readiness check and confirms four things:

  • the companion engine is running and reachable;
  • your license or trial is active;
  • the on-device models are downloaded and ready;
  • a sequence is open so the tools have something to inspect.

Activation opens a sign-in page in your browser. Approve the code it shows you, return to Premiere, and the panel takes it from there. One licence covers two computers, and it stores a short signed lease so the tools keep working for up to seven days without a connection. Um Out never places its licence signing key inside the plugin.

Troubleshooting

Um Out is not in the Premiere menu

Fully quit and reopen Premiere Pro. If it still does not appear, run the installer again and let it reinstall the panel, then restart Premiere. On Windows the installer also leaves UmOut.ccx in its plugin folder; opening that file hands the panel to Creative Cloud Desktop to install instead.

“Engine not found” in the panel

The panel cannot reach the companion. Confirm the companion is running from its diagnostics screen. If a firewall or security tool blocked its local connection, allow Um Out and reopen the panel. Because the companion is not code-signed yet, some security tools are more suspicious of it than they will be later.

Models are stuck downloading

Models are fetched on first run and can take a while on a slow connection. Leave the panel open; it resumes rather than starting over. If it stalls completely, restart the companion from its diagnostics screen and reopen the panel.

Activation will not complete

Your licence covers two machines and works offline for up to seven days between checks. Never send an API key, password, full transcript, or project file through chat or email. For anything else, use the support chat or contact Um Out.

Installed and ready? Next, learn how the free trial works or jump straight into removing silences.