Catalina Support??? You should have a notice before purchasing.
-
Hey guys. I was excited to give this a try, and realized (after downloading) that you do not support the latest MacOS. This should be made apparent to users before purchasing. I was really hoping to use it on a project with a deadline, and now I am unable.
-
Same thing happened to me. I'm waiting on a response about a refund.
-
Hi,
macOS Catalina introduced a certification process called "Notarisation", which is pretty annoying because it requires developers to upload their binary to Apple servers to get it certified. There was a lot of buzz especially in the audio developer community when this "feature" was introduced and we decided to bypass this step for PercX (it's code-signed by the default Apple developer ID), so if you try to open the installer on Catalina, you'll see an error message like this:
It obviously doesn't show QLStephen.qlgenerator, but that's the first image that pops up on the Google image search for Catalina Notarisation error. Poor stephen
However it's pretty easy to bypass the notarisation check for end users: you just have to right click on the installer, then choose Open from the context menu (you might have to enter your admin password once so that Apple can add PercX to the list of trusted apps).
-
@Christoph-Hart yes this worked! thanks
-
@Christoph-Hart can you please give specific instructions again, it is not working for me and I just purchased and downloaded the Pro program.
-
@Christoph-Hart I have Mac Catalina, and the program is not opening from my download, even when I right click the Open from contexr menu.
-
@Christoph-Hart hi, I'm having the same problem as these other people; even though I forced the installer to open, it just won't open... First try I got a message saying the installer was "broken", after that the pkg-file just stopped executing at all when I tried again... Please fix this as I am eager to try the software out...
edit: I'm on OS 10.15.3 btw
Best,
Ludvig
-
This post is deleted!
-
Update: downloading the installer a second time fixed it for me. Cheers.