macOS 10.13.6 High Sierra & latest DSP Trigger 1.6.2.0

[BenzeneWings]

Hello all. I just downloaded the demo to excitedly try DSP Trigger and it is not showing for an audio effect in Logic X.
I am in Logic 10.4.1 and (as the subject of post says) macOS 10.13.6 High Sierra & latest DSP Trigger 1.6.2.0. I checked my audio/plug-ins/components folder to make sure dspTrigger.component was present among the rest of my plugins, and the file is indeed there. Do I need an earlier version of the plugin since I am still on High Sierra, which I know to many is a dinosaur probably, but I don't update often (there used to not be so many updates). . Or can this work somehow? I saw some where on these forums that it was mac 10.7 and up...Any ideas what might be goin on?

[Rob]

HI,

I've put version 1.6.1 back in the downloads if you want that a go. You might need to uninstall first. It's actually been a very long time since I updated DSP TRIGGER. I'm not entirely sure why it's not working on your system, but I'll investigate. Thanks.

[BenzeneWings]

Solved. For those facing similar, you must install then do a full system restart and relaunch DAW. I'd put that message on the installer.

[djbclark]

Did you have to downgrade to 1.6.1 for it to work?

Update: Nevermind, as far as I can tell the AU in the 1.6.2.0 install is version 1.6.1 (or it is different but the version # didn't get upgraded)

Here is getinfo of the file that Mainstage Plug-in Manager reports as being 1.6.1, after a 1.6.2 install (and several reboots):

dspTrigger.component
8.3MB
8,262,107 bytes
Created/Modified: Sept 17, 2021 8:07am
Version: Copyright 2015 Audiofront

Update 2: Used pacifist to unpack the 1.6.2.0 AU pkg to a differnent folder, verified it is exactly the same as the version that gets installed. So for the Mac OS X AU, either 1.6.1=1.6.2 or some string needs to get updated somewhere. If anyone does have a 1.6.1 package installed or laying around, could you see if it is the same as above?

Also, anyone know of a way of doing checksums for .app files? From command-line POV they are folders so the usual sha1sum etc. don't work.

[Rob]

The version discrepancy is likely just a string identifier that didn't get updated. Not something to be concerned about.