PostWatch FAQs

The Story

Like most post-production professionals during Covid, I had a roller coaster year. Between working in the studio, stuck at home with a makeshift edit bay on my kitchen table, and back to the studio working solo (with other staff at home) It was a challenge to say the least. But one thing I was needing, especially when trying to work through remote desktop software, was a way to be alerted when something was finished, crashed or failing.

It started from an idea that came from using the fantastic free Final Cut Pro assistant called CommandPost which has a nice feature that would send a push notification to a mobile phone when a Share was complete. But I wanted more. More apps to be precise. Then through some web searches I came across some AppleScripts that could help me build my own solution.

A few months later and a lot of real life testing I slowly came up with what I’m now calling PostWatch. This is an ongoing project that I use everyday and will continue to develop, add more applications and keep up with new macOS releases.

Why did PostWatch switch to a paid model?

As a working post-production professional I had originally offered PostWatch as a free application for the editing community. Both of my Apps (including PostSync) are developed solely by myself in my spare time. However, due to the costs of maintaining a website and an Apple Developer account I’ve had to switch to a paid model to keep the projects alive.

In doing this I still wanted to have a version with some basic features to share for free. So I balanced the development costs of keeping up with application and macOS updates with the usability of a free version. The Lite edition should have enough features for the average user.

Many features have required more of my time to code plus need repeated testing to maintain compatibility with future application updates. These are included in Pro edition.

Issues with Privacy & Security?

In certain situations I have found that macOS Privacy & Security can block PostWatch from the resources it needs. This can happen after using Migration Assistant or Time Machine to restore User files, Applications or macOS.

Here are some things to try to fix the issue:

  • Go to Security & Privacy -> Files and Folders. Make sure all entries under PostWatch are enabled.
  • Go to Security & Privacy -> Automation. Make sure all entries under PostWatch are enabled.
  • If you are using macOS Sequoia, go to Security & Privacy -> Full Disk Access. Make sure PostWatch is enabled.

If this still doesn’t solve the problem, try clearing all of the Security settings for PostWatch:

  • Quit PostWatch.
  • Open the Terminal app.
  • Type in “tccutil reset All com.crfilms.postwatch” and tap enter.
  • Type in “tccutil reset All com.crfilms.postwatch.watcher” and tap enter.
  • Close Terminal.
  • Delete the PostWatch app from the Applications folder.
  • Restart the computer.
  • Re-download and install PostWatch from this site.
  • Launch PostWatch and make sure to “Allow” all requests for access to System/App resources.