different method for the issue at hand

[metropical]

the issue at hand is explained in 2 previous posts/threads.

basically QS was crashing after a time. It seemed to be most often when editing custom Triggers.  I had thought it was an audio plug-in for Pro Tools, but now I think not.

The plist I used I had used just a few days before when taking my unsupported 2013 MBA to Sequoia via OCLP.

The MBA and QS and Sequoia are just dandy.

I decided that even though I had success with that plist and the MBA, perhaps it has become corrupt.

So today as I built back Sequoia onto my 2018 mini for the 4th time (even after an Apple DFU Restore), I decided to add custom triggers from scratch and not use the old plist.

So far so good.

2 issues.  I can't get QS Triggers to accept Cntl/Cmd/D or HyperKey/Q. (HyperKey is provided by Karabiner.  I was thinking there was some OS conflict with either of those shortcuts, but can't find them.

If anyone has a suggestion ...

[metropical]

and then this morning. back to the same issues.  I give.  I'm gonna step back to Monterey and see if that is still stable.

If not, then I'd say the mini was corrupted upgrading to Sequoia, as impossible as that sounds to me.

[metropical]

There are definitely some issues upgrading a 2018 mini to Sequoia. YMMD.

At an Apple store the tech looked for a way to DFU restore to Monterey, but said Apple no longer proved the tools as they wanted every user current.

Fine for Apple, but at least in my experience the last 2 weeks, not for everyone.
I created a bootable installer (MrMacintosh has good info) which installed Monty in less than an hour then let Migration Asst do the other work from my old 5400 back up.

That took many hours, of course, but I am back to Monty.  Next move, an ext SSD for Sequoia.