Adobe After Effects 22.3.0 (build 47)AMD Fix

[fabiosun]

libiomp5.dylib

libmkl_avx512.1.dylib

libmkl_core.1.dylib

 

remember to codesign after effects app if you need

 

Enjoy!

 

[nikoel]

Hey brochachi

 

Where did you get 22.3 from? The latest that is showing up on my end is 22.2 

 

 

[fabiosun]

6 hours ago, nikoel said:

Hey brochachi

 

Where did you get 22.3 from? The latest that is showing up on my end is 22.2 

 

 

 

 

with this script it builds also beta full off line installer:

https://github.com/Drovosek01/adobe-packager

[hoeveler]

I patched the AE (beta) v22.3.0 (build 97) using your 3 attached files (and then code signing each) but when running the Puget Systems PugetBench, I got the following error:

[fabiosun]

35 minutes ago, hoeveler said:

I patched the AE (beta) v22.3.0 (build 97) using your 3 attached files (and then code signing each) but when running the Puget Systems PugetBench, I got the following error:

It seems a different build if I am not wrong 47—>97?

[fabiosun]

@hoevelerif you like to try, these are the exact build 97 libs:

 

Build 97

 

patched with @Nyaomiapp

 

 

 

 

[hoeveler]

9 hours ago, fabiosun said:

@hoevelerif you like to try, these are the exact build 97 libs:

 

Build 97

 

 

patched with @Nyaomiapp

 

 

 

 

Thanks! I saw that github page but was unclear if it would interfere with the HackinDROM that I'm using for my system. Does it only patch apps and binaries and won't mess with the system?

[fabiosun]

@hoeveleryou patch only the libs you want to patch and useful for you to patch

then it is not related ..I use a thunderbolt with a SSDT

but patching libraries is a different story!

 

 

 

 

[hoeveler]

That's what I thought, but always good to ask first. I see that I simply enter my filepath and that's all the program sees. Thanks!

[hoeveler]

@fabiosun ever since I used the 

sudo codesign --force --deep --sign - 

command (on a few of the lib files inside AE contents), I have been getting these popping up and keep happening even though I'm clicking "always allow". Do I need to use the Adobe repair tool to reset these permissions? Or is there something else I need to codesign?

[hoeveler]

@fabiosun I've used the AMD friend command line method but I'm still having pop up windows (shown above) asking me to use my login twice each time a new Adobe app opens, and also still not being able to get Puget Bench to run without failing on that one screen I shared above. Any solutions?

Thanks!