jimrey wrote:I am wondering if it it a problem created by that fact I have a late 2012 MAC which have been legacy core patched to Sequoia
Hey
I'm no more into this garage like stuff and whatever dosdude tricks - but I liked it a lot - and therefore cannot tell, but ... it's very unlikely you'll find a specific answer to your question here around, because you know, 12 years in Apple space-time usually means huge different changes, especially since ARM Mx era...
For example I manage around 40 - OSX - computers for family and friends around, and the gap has gone wider now with ARM ones : it was easier to deal with 2003-2008 machines to be trained and upgraded up to 2019 ones, but afterwards, it's not only the QT replacement by core video, it's a whole new system which has implementation guidelines that might change a lot in the end compared to what was a piece of cake back to old times...
Secondly and moreover, BMD obviously tries to optimize Resolve. Yes, big companies still try to distribute Intel AND ARM version (as it was for universal binaries PPC/Intel years ago), just like nVidia kept drivers for mac years after their divorce with Apple, but most of them will probably ditch their Intel version soon I think, meaning patching solutions will disappear at the same pace.
Thus quickly, I doubt a few folders in Library might fix it, even if I wish it could make it for you. And even quicker, Sequoia carries a bunch of problems anyway (even on a standard install) which leads power users to prudently remain on previous OS versions, and you maybe should as well, just sayin'
Tl;DR : if you tweak your MacOs, stay away from Sequoia (and for XMas start seriously thinking about upgrading your hardware
)
*MacMini M1 16 Go - Sonoma - Ext nvme SSDs on TB3 - 14 To HD in 2 x 4 disks USB3 towers
*Legacy MacPro 8core Xeons, 32 Go ram, 2 x gtx 980 ti, 3SSDs including RAID
*Resolve Studio everywhere, Fusion Studio too
*https://www.buymeacoffee.com/videorhin