Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
To fix adobe products crashes on AMD hackintosh
MOVED HERE:
https://gist.github.com/naveenkrdy/26760ac5135deed6d0bb8902f6ceb6bd
@Sceko

This comment has been minimized.

Copy link

Sceko commented May 16, 2019

For Bridge

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Bridge\ CC\ 2019/Adobe\ Bridge\ CC\ 2019.app/Contents/Plug-ins/MMXCore.plugin/Contents/MacOS/MMXCore

@Joaolbrocha

This comment has been minimized.

Copy link

Joaolbrocha commented May 25, 2019

Doesnt work in Illustrator CC 2019

@Joaolbrocha

This comment has been minimized.

Copy link

Joaolbrocha commented May 25, 2019

sudo rm -rf /Applications/Adobe\ Illustrator\ CC\ 2019/Adobe\ Illustrator.app/Contents/MacOS/MMXCore.plugin /Applications/Adobe\ Illustrator\ CC\ 2019/Adobe\ Illustrator.app/Contents/Required/Plug-ins/Text\ Filters/TextModel.aip <<<< Running command.

@Sceko

This comment has been minimized.

Copy link

Sceko commented Jun 8, 2019

old version camera raw and this is very bad for now

@ghostuz

This comment has been minimized.

Copy link

ghostuz commented Jun 30, 2019

have anyone know how to fix lightroom classic cc 2019?

@ghostuz

This comment has been minimized.

Copy link

ghostuz commented Jun 30, 2019

have anyone know how to fix lightroom classic cc 2019?

@braynshock

This comment has been minimized.

Copy link

braynshock commented Aug 11, 2019

thank you

@glics

This comment has been minimized.

Copy link

glics commented Aug 19, 2019

Does anyone have a fix for Media Encoder? I can't find neither MMXCore or FastCore inside its Contents

@cpboleto

This comment has been minimized.

Copy link

cpboleto commented Aug 25, 2019

this fix liquify crash?

@EfraimLA

This comment has been minimized.

Copy link

EfraimLA commented Sep 7, 2019

Applied all patches but PS crashes when i use liquify and select subject, someone know why? Is there solution? Thanks btw

@yelanxin

This comment has been minimized.

Copy link

yelanxin commented Sep 8, 2019

acr crash

@petitbrain

This comment has been minimized.

Copy link

petitbrain commented Sep 21, 2019

have anyone know how to fix InDesign cc 2019?

@WangZhuo2015

This comment has been minimized.

Copy link

WangZhuo2015 commented Oct 4, 2019

Any solution for Lightroom CC?

@Sceko

This comment has been minimized.

Copy link

Sceko commented Oct 7, 2019

only intel cpu :) is solution

@cakaragiannis

This comment has been minimized.

Copy link

cakaragiannis commented Oct 30, 2019

Terminal response for Bridge 2019 fix:
Can't open /Applications/Adobe Bridge CC 2019/Adobe Bridge CC 2019.app/Contents/Plug-ins/MMXCore.plugin/Contents/MacOS/MMXCore: No such file or directory.

@Spivix

This comment has been minimized.

Copy link

Spivix commented Nov 3, 2019

Does anybody have a fix for designer?

@dj-sash

This comment has been minimized.

Copy link

dj-sash commented Nov 16, 2019

What about Adobe Indesign CC 2017 / 2018 / 2019 ?
As there are some 3rd-party plugins for older versions. But, Indesign keeps upgrading to give better usability.
Can it be patched please?

@Vralis

This comment has been minimized.

Copy link

Vralis commented Nov 17, 2019

I would also be really glad for InDesign Fix. Thank you

@CreatiV92

This comment has been minimized.

Copy link

CreatiV92 commented Dec 2, 2019

For Photoshop 2020

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/FastCore.plugin/Contents/MacOS/FastCore

@printfjesus

This comment has been minimized.

Copy link

printfjesus commented Dec 4, 2019

Any solution with Warp stabilizer in premiere pro and after effects? cant use that, both programs crash after try to use it

@simonvollmer

This comment has been minimized.

Copy link

simonvollmer commented Dec 17, 2019

Anything for lightroom CC?

@cemkoker

This comment has been minimized.

Copy link

cemkoker commented Dec 25, 2019

Lightroom please :)

@roznick

This comment has been minimized.

Copy link

roznick commented Dec 30, 2019

For Photoshop 2020

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/FastCore.plugin/Contents/MacOS/FastCore

Thanks for the info! I am trying this and it keeps saying "Password" with a little key symbol, but will not allow me to type anything in. Any insight? Thanks again!

@CreatiV92

This comment has been minimized.

Copy link

CreatiV92 commented Dec 30, 2019

For Photoshop 2020
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/FastCore.plugin/Contents/MacOS/FastCore

Thanks for the info! I am trying this and it keeps saying "Password" with a little key symbol, but will not allow me to type anything in. Any insight? Thanks again!

you must enter your password, which you enter when you turn on mac. characters will not show when typing, this is normal

@roznick

This comment has been minimized.

Copy link

roznick commented Dec 31, 2019

For Photoshop 2020
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Plug-ins/Extensions/FastCore.plugin/Contents/MacOS/FastCore

Thanks for the info! I am trying this and it keeps saying "Password" with a little key symbol, but will not allow me to type anything in. Any insight? Thanks again!

you must enter your password, which you enter when you turn on mac. characters will not show when typing, this is normal

That did the trick! Thanks so much.
Seems like Lightroom and InDesign have no hope as of right now from what I am seeing?

@CreatiV92

This comment has been minimized.

Copy link

CreatiV92 commented Dec 31, 2019

Seems like Lightroom and InDesign have no hope as of right now from what I am seeing?

I do not use these programs)

@kortbyoussama

This comment has been minimized.

Copy link

kortbyoussama commented Jan 3, 2020

Hi Bro,
i need this fix for lightroom classic and inDesign
i did it for photoshop and illustrator and after effect and it's working but i need the others

@roznick

This comment has been minimized.

Copy link

roznick commented Jan 3, 2020

@kortbyoussama

This comment has been minimized.

Copy link

kortbyoussama commented Jan 3, 2020

@anthonyalves92

This comment has been minimized.

Copy link

anthonyalves92 commented Jan 12, 2020

Photoshop 2020 worked perfectly. Looks like Illustrator 2020 is now having an issue as well.

@EfraimLA

This comment has been minimized.

Copy link

EfraimLA commented Jan 12, 2020

Doesn't PS2020 crash?

@glics

This comment has been minimized.

Copy link

glics commented Jan 18, 2020

Works for me on Ai 2020:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Illustrator\ 2020/Adobe\ Illustrator.app/Contents/MacOS/MMXCore.plugin/Contents/MacOS/MMXCore
sudo rm -rf /Applications/Adobe\ Illustrator\ 2020/Adobe\ Illustrator.app/Contents/Required/Plug-ins/Text\ Filters/TextModel.aip
@glics

This comment has been minimized.

Copy link

glics commented Jan 18, 2020

Couldn't fix Ae by removing camera raw tho. Still looking for an Ae patch.
Shame cuz everything else just works so well on AMD.

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Jan 19, 2020

Lightroom Classic (Version 9.1) seems to work with this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
@kortbyoussama

This comment has been minimized.

Copy link

kortbyoussama commented Jan 19, 2020

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Jan 20, 2020

Don't have Indesign unfortunately...
But this could potentially fix more CameraRaw related issues - which I don't believe is the case with Indesign.

I have no clue why the patch works exactly like this, it was a wild guess. I used the information of the original post for further investigation. You can also do that by analysing the crash report:
The top entry in the crashed thread reveals which binary image is causing the crash (in this case AgImageIO). Further down, the list of binary images leads the way to the file in the file system representing that binary image (in this case CameraRaw). Then you can binwalk -R "\x90\x90\x90\x90\x56\xE8" <path-to-offending-file> and see if you have a match. Then try to put other numbers at the \x5A/\x3A part. In this case the crash report even showed on which address the segfault was triggered, exactly the addresses that have to be patched...

what about indesign? On Jan 20, 2020 00:18, gasseluk notifications@github.com wrote:Lightroom Classic (Version 9.1) seems to work with this: sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

@shadowmx

This comment has been minimized.

Copy link

shadowmx commented Jan 21, 2020

Lightroom Classic (Version 9.1) seems to work with this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

This seems to work for Lightroom Classic, but the app will crash mentioning code signature.
You can run sudo codesign --remove-signature /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app to remove codesignature from the app and it will work then.

The same fix works for Lightroom CC, but if you remove code signature the app will fail in other ways (no network) and it doesn't connect to Adobe CC so you can't use it.

@KameraKasino

This comment has been minimized.

Copy link

KameraKasino commented Jan 24, 2020

Awesome fixes here. I'm 100% on LR, but PS still crashes using any tools that open up in separate window. Select and mask, Liquify, etc. Does anybody have a fix. Greatly appreciated!!

@CreatiV92

This comment has been minimized.

Copy link

CreatiV92 commented Jan 25, 2020

After Effects 2020 crash fix
delete file "Camera Raw.plugin" from path:
/Library/Application Support/Adobe/Plug-Ins/CC/File Formats/

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Jan 25, 2020

Awesome fixes here. I'm 100% on LR, but PS still crashes using any tools that open up in separate window. Select and mask, Liquify, etc. Does anybody have a fix. Greatly appreciated!!

Seems to be caused by Intel MKL, as seen through the debugger.
Try to run photoshop from the terminal like this:

MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2020

Source: pytorch/pytorch#31106

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Jan 25, 2020

Awesome fixes here. I'm 100% on LR, but PS still crashes using any tools that open up in separate window. Select and mask, Liquify, etc. Does anybody have a fix. Greatly appreciated!!

Seems to be caused by Intel MKL, as seen through the debugger.
Try to run photoshop from the terminal like this:

MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2020

Source: pytorch/pytorch#31106

Interesting. I did some reading on the very few places I could find info about this (puget systems) and I'm not sure how this relates to my Photoshop issue. Can you expand on this?

Sure. I have no clue what exactly is the link between PS and MKL. Anyway if I run photoshop, open an image and head to "Liquify..." the spin wheel turns up and nothing more happens. Is that what you experience?
Now on the console output, I get something like this:

2020-01-25 22:46:52.534030+0100 Adobe Photoshop 2020[1099:20660] [DYMTLInitPlatform] platform initialization successful
2020-01-25 22:46:52.596465+0100 Adobe Photoshop 2020[1099:20592] AdobeCrashReporterInitialize: executionTime = 0.003401 seconds
Creating new log file at: /Users/someweirduser/Library/Logs/Adobe/Adobe Photoshop 2020//ACPL__2020-01-25_22-46-53-442_00.log
2020-01-25 22:46:53.512670+0100 Adobe Photoshop 2020[1099:20822] Reachability Flag Status: xR ------- networkStatusForFlags
2020-01-25 22:46:54.366841+0100 Adobe Photoshop 2020[1099:20685] MessageTracer: Falling back to default whitelist
2020-01-25 22:46:55.159018+0100 Adobe Photoshop 2020[1099:20592] Metal GPU Frame Capture Enabled
2020-01-25 22:46:55.159308+0100 Adobe Photoshop 2020[1099:20592] Metal API Validation Enabled
2020-01-25 22:46:55.277270+0100 Adobe Spaces Helper[1105:20897] MessageTracer: Falling back to default whitelist
2020-01-25 22:46:55.305866+0100 Adobe Spaces Helper[1105:20884] Metal API Validation Enabled
2020-01-25 22:46:55.341011+0100 Adobe Spaces Helper[1105:20884] GVA error: AGPMGetManagedPortForAccelerator returned 0x4 for VP4
2020-01-25 22:46:55.343173+0100 Adobe Spaces Helper[1105:20884] GVA error: AVD_api.Create failed (err=14, displayID=1124263423, mask1=127, mask2=127, mask3=8)
2020-01-25 22:46:55.343256+0100 Adobe Spaces Helper[1105:20884] GVA error: Flow_QT0::physicalAcceleratorDispose, m_physical_accel_created == false
objc[1099]: Class CertificateVerifier is implemented in both /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/Adobe Photoshop 2020 (0x10a7ff358) and /Library/Application Support/Adobe/Adobe Desktop Common/LCC/imshelper.dylib (0x19c80b648). One of the two will be used. Which one is undefined.
objc[1114]: Class HTTPHeader is implemented in both /Library/Application Support/Adobe/AdobeGCClient/AdobeGCClient.app/Contents/MacOS/AdobeGCClient (0x10041e1d0) and /Library/Application Support/Adobe/AdobeGCClient/HDPIM.dylib (0x10f5f5890). One of the two will be used. Which one is undefined.
objc[1114]: Class ProxyManager is implemented in both /Library/Application Support/Adobe/AdobeGCClient/AdobeGCClient.app/Contents/MacOS/AdobeGCClient (0x10041e220) and /Library/Application Support/Adobe/AdobeGCClient/HDPIM.dylib (0x10f5f58e0). One of the two will be used. Which one is undefined.
*** GPU Warning: GPU3 disabled because hard requirements not met ***
2020-01-25 22:47:03.835348+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.835520+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.835592+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.835881+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.836583+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.837441+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.840193+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.845590+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
Intel MKL ERROR: CPU 0 is not supported.

That made me google for that last line Intel MKL ERROR: CPU 0 is not supported.. Then after setting the environment variable as stated, Liquify seems to work.

Versions:

  • Adobe Photoshop Version: 21.0.2 20191122.r.57 2019/11/22: e3e4068e635 x64
  • Liquify 21.0.2, © 2001-2019 Adobe. All rights reserved. - from the file “Liquify.plugin”
@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Jan 26, 2020

Awesome fixes here. I'm 100% on LR, but PS still crashes using any tools that open up in separate window. Select and mask, Liquify, etc. Does anybody have a fix. Greatly appreciated!!

Seems to be caused by Intel MKL, as seen through the debugger.
Try to run photoshop from the terminal like this:

MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2020

Source: pytorch/pytorch#31106

Interesting. I did some reading on the very few places I could find info about this (puget systems) and I'm not sure how this relates to my Photoshop issue. Can you expand on this?

Sure. I have no clue what exactly is the link between PS and MKL. Anyway if I run photoshop, open an image and head to "Liquify..." the spin wheel turns up and nothing more happens. Is that what you experience?
Now on the console output, I get something like this:

2020-01-25 22:46:52.534030+0100 Adobe Photoshop 2020[1099:20660] [DYMTLInitPlatform] platform initialization successful
2020-01-25 22:46:52.596465+0100 Adobe Photoshop 2020[1099:20592] AdobeCrashReporterInitialize: executionTime = 0.003401 seconds
Creating new log file at: /Users/someweirduser/Library/Logs/Adobe/Adobe Photoshop 2020//ACPL__2020-01-25_22-46-53-442_00.log
2020-01-25 22:46:53.512670+0100 Adobe Photoshop 2020[1099:20822] Reachability Flag Status: xR ------- networkStatusForFlags
2020-01-25 22:46:54.366841+0100 Adobe Photoshop 2020[1099:20685] MessageTracer: Falling back to default whitelist
2020-01-25 22:46:55.159018+0100 Adobe Photoshop 2020[1099:20592] Metal GPU Frame Capture Enabled
2020-01-25 22:46:55.159308+0100 Adobe Photoshop 2020[1099:20592] Metal API Validation Enabled
2020-01-25 22:46:55.277270+0100 Adobe Spaces Helper[1105:20897] MessageTracer: Falling back to default whitelist
2020-01-25 22:46:55.305866+0100 Adobe Spaces Helper[1105:20884] Metal API Validation Enabled
2020-01-25 22:46:55.341011+0100 Adobe Spaces Helper[1105:20884] GVA error: AGPMGetManagedPortForAccelerator returned 0x4 for VP4
2020-01-25 22:46:55.343173+0100 Adobe Spaces Helper[1105:20884] GVA error: AVD_api.Create failed (err=14, displayID=1124263423, mask1=127, mask2=127, mask3=8)
2020-01-25 22:46:55.343256+0100 Adobe Spaces Helper[1105:20884] GVA error: Flow_QT0::physicalAcceleratorDispose, m_physical_accel_created == false
objc[1099]: Class CertificateVerifier is implemented in both /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/Adobe Photoshop 2020 (0x10a7ff358) and /Library/Application Support/Adobe/Adobe Desktop Common/LCC/imshelper.dylib (0x19c80b648). One of the two will be used. Which one is undefined.
objc[1114]: Class HTTPHeader is implemented in both /Library/Application Support/Adobe/AdobeGCClient/AdobeGCClient.app/Contents/MacOS/AdobeGCClient (0x10041e1d0) and /Library/Application Support/Adobe/AdobeGCClient/HDPIM.dylib (0x10f5f5890). One of the two will be used. Which one is undefined.
objc[1114]: Class ProxyManager is implemented in both /Library/Application Support/Adobe/AdobeGCClient/AdobeGCClient.app/Contents/MacOS/AdobeGCClient (0x10041e220) and /Library/Application Support/Adobe/AdobeGCClient/HDPIM.dylib (0x10f5f58e0). One of the two will be used. Which one is undefined.
*** GPU Warning: GPU3 disabled because hard requirements not met ***
2020-01-25 22:47:03.835348+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.835520+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.835592+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.835881+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.836583+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.837441+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.840193+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
2020-01-25 22:47:03.845590+0100 Adobe Photoshop 2020[1099:20592] dynamic_cast error 1: Both of the following type_info's should have public visibility.  At least one of them is hidden. 16CExpressionScope, 17CExpressViewScope.
Intel MKL ERROR: CPU 0 is not supported.

That made me google for that last line Intel MKL ERROR: CPU 0 is not supported.. Then after setting the environment variable as stated, Liquify seems to work.
Versions:

  • Adobe Photoshop Version: 21.0.2 20191122.r.57 2019/11/22: e3e4068e635 x64
  • Liquify 21.0.2, © 2001-2019 Adobe. All rights reserved. - from the file “Liquify.plugin”

You have an intel processor?

Ehm... Of course not.
See IMO the in order to get MKL working correctly on AMD, that MKL_DEBUG_CPU_TYPE must be set, at least on macOS. And the console output of PS makes it obvious that PS uses MKL in some way.
It's obviously a big deal that tools which use MKL do not support AMD properly. See https://en.wikipedia.org/wiki/Math_Kernel_Library for more insight.

@coun7zero

This comment has been minimized.

Copy link

coun7zero commented Jan 29, 2020

For the people for whom the above solution for Photoshop 2020 doesn't work (it is probably a change for the version 21.0.3 )

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/FastCore.plugin/Contents/MacOS/FastCore

sudo rm -rf /Library/Application\ Support/Adobe/Plug-Ins/CC/File Formats/Camera\ Raw.plugin
@alansleep

This comment has been minimized.

Copy link

alansleep commented Jan 31, 2020

I see. I must be applying the fix wrong on my end. I'm still having no success using these tools.

Hi, I also have a crash with liquify and black/white filter, but console doesn't show anything about MKL. I have FX-8350 and 10.13.6 os. Tried to remove HDPIM.dylib and AdobeGCClient, no luck.

iMac-Pro:~ sam$ MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2020
2020-01-31 18:05:25.493 Adobe Photoshop 2020[1372:22245] AdobeCrashReporterInitialize: executionTime = 0.003686 seconds
Creating new log file at: /Users/sam/Library/Logs/Adobe/Adobe Photoshop 2020//ACPL__2020-01-31_18-05-26-685_00.log
2020-01-31 18:05:31.786 Adobe Photoshop 2020[1372:22321] Reachability Flag Status: xR ------- networkStatusForFlags
Logging Generator in directory: /Users/sam/Library/Logs/Adobe/Adobe Photoshop 2020/Generator
Use '-v' option to print logs to stdout
objc[1389]: Class HTTPHeader is implemented in both /Library/Application Support/Adobe/AdobeGCClient/AdobeGCClient.app/Contents/MacOS/AdobeGCClient (0x1103c41d0) and /Library/Application Support/Adobe/AdobeGCClient/HDPIM.dylib (0x11b675890). One of the two will be used. Which one is undefined.
objc[1389]: Class ProxyManager is implemented in both /Library/Application Support/Adobe/AdobeGCClient/AdobeGCClient.app/Contents/MacOS/AdobeGCClient (0x1103c4220) and /Library/Application Support/Adobe/AdobeGCClient/HDPIM.dylib (0x11b6758e0). One of the two will be used. Which one is undefined.
Illegal instruction: 4

@aschilletus

This comment has been minimized.

Copy link

aschilletus commented Jan 31, 2020

Photoshop 2020 doesn't work !!!!!!!!!!

@jogerj

This comment has been minimized.

Copy link

jogerj commented Jan 31, 2020

For the people for whom the above solution for Photoshop 2020 doesn't work (it is probably a change for the version 21.0.3 )

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/FastCore.plugin/Contents/MacOS/FastCore

sudo rm -rf /Library/Application\ Support/Adobe/Plug-Ins/CC/File Formats/Camera\ Raw.plugin

Confirmed to be working with latest version of PS 2020

@aschilletus

This comment has been minimized.

Copy link

aschilletus commented Jan 31, 2020

For the people for whom the above solution for Photoshop 2020 doesn't work (it is probably a change for the version 21.0.3 )

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/FastCore.plugin/Contents/MacOS/FastCore

sudo rm -rf /Library/Application\ Support/Adobe/Plug-Ins/CC/File Formats/Camera\ Raw.plugin

Confirmed to be working with latest version of PS 2020

Yes it works. Thank you.

@arachule

This comment has been minimized.

Copy link

arachule commented Feb 3, 2020

Hi There you are life saver thank you for fixes,, I want to share a solution for adobe indesign 2020. Use. this MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ InDesign\ 2020/Adobe\ InDesign\ 2020.app/Contents/MacOS/Adobe\ InDesign\ 2020

originally this is advised for Photoshop 2020 liquefy tool crash and it works. But it also work r adobe indesign. I did not try all functions yet but it opens without any problem..

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 3, 2020

With MKL_DEBUG_CPU_TYPE=4 black and white filter and even 3d functions and preserve details 2.0 work with amd fx but liquify just makes the app freeze

@artech4520

This comment has been minimized.

Copy link

artech4520 commented Feb 9, 2020

Thank you so much. I was almost about to give up. And your method actually worked for me. (PS 2020)

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 21, 2020

made a video on the topic - https://youtu.be/SkStHcT3Axs

@jogerj

This comment has been minimized.

Copy link

jogerj commented Feb 21, 2020

made a video on the topic - https://youtu.be/SkStHcT3Axs

I don't get why you need to tell Terminal to run a shell script. Forget about the Close.app
do shell script "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/Adobe Photoshop 2020'" works just fine.
Liquify also works on Ryzen with this fix.

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 21, 2020

do shell script "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/Adobe Photoshop 2020'" works just fine.

Without Close.app Terminal has to be closed manually, I preffer automatisation)

Liquify also works on Ryzen with this fix.

Thanks for the info

@jogerj

This comment has been minimized.

Copy link

jogerj commented Feb 21, 2020

Without Close.app Terminal has to be closed manually, I preffer automatisation)

Heh, worked flawlessly to me

gif

Here I copied the icon from PS to the applet and renamed it. No Terminal popping. Might upload code later, idk still busy atm.

EDIT3: Disclaimer: many portions of the auto script are not implemented yet, as of now only PS is implemented. Please leave feedback and report issues or even help complete the code (template's all there). Will put more work into it when got some spare time
EDIT2:
Automatic scripts here: https://github.com/jogerj/Adobe-AMD-Fix
EDIT:
Here's how you make your own:

  1. Open Script Editor
  2. Paste code: do shell script "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/Adobe Photoshop 2020'" (For Ryzen, FX and below use MKL_DEBUG_CPU_TYPE=4)
  3. File > Export (as Application), use whatever file name like Run Adobe Photoshop 2020.app
  4. (Optional) Copy PS icon to applet: cp '/Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/Resources/PS_AppIcon.icns' 'PATH/TO/Run Adobe Photoshop 2020.app/Contents/Resources/applet.icns'
  5. Place Run Adobe Photoshop 2020.app anywhere you like, then pin to your dock if you want
@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 21, 2020

Heh, worked flawlessly to me

actually it worked, thanks) I'm a newbie in AppleScript

@seven2099

This comment has been minimized.

Copy link

seven2099 commented Feb 22, 2020

When using the fixes above for Photoshop, I was able to get Premier 2020, Lightroom Classic 2020, and Photoshop 2020 fully working.
However I'm stuck on After Effects with the following error:

When I run: "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe After Effects 2020/Adobe After Effects 2020.app/Contents/MacOS/After Effects'"

error "objc[10995]: Class AdobeSimpleURLSession is implemented in both /Applications/Adobe After Effects 2020/Adobe After Effects 2020.app/Contents/Frameworks/pie.framework/Versions/A/pie (0x1332b6540) and /Applications/Adobe After Effects 2020/Adobe After Effects 2020.app/Contents/Frameworks/cclibmanager.framework/Versions/A/cclibmanager (0x12ff6d3b8). One of the two will be used. Which one is undefined.
2020-02-22 16:54:45.462 After Effects[10995:10724194] AdobeCrashReporterInitialize: executionTime = 0.003606 seconds
2020-02-22 16:54:45.485 AdobeCRDaemon[10996:10724519] CR dialog Preference for force quit 1
2020-02-22 16:54:48.292 AdobeCRDaemon[10996:10724520] exitStatus: 0" number 1011

Any ideas?

@cemkoker

This comment has been minimized.

Copy link

cemkoker commented Feb 23, 2020

MKL CPU doesn't work for Lightroom CC; anyone had success ?

@artech4520

This comment has been minimized.

Copy link

artech4520 commented Feb 23, 2020

can anyone please help me in fixing Camtasia 2019? sorry if I'm asking under the wrong section.
Thanks in advance

@ForresterAlex

This comment has been minimized.

Copy link

ForresterAlex commented Feb 23, 2020

MKL CPU doesn't work for Lightroom CC; anyone had success ?

Are you referring to lightroom CC or lightroom classic 2020? Lightroom Classic 2020 appears to work fine (if not much better than my windows laptop) on my 2700x & 5700xt system with one of the above fixes. Link to comment with fix:
https://gist.github.com/XLNCs/86d7a391e46f85a04d28db171656b458#gistcomment-3144637

Anyone have any success with premire? I saw some ppl got it to work, but I didn't see any fixes for it. mine launches, but then errors out, it's not too much of a priority, i don't use it much, i have it through school, so I'm not paying directly for it.

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 23, 2020

MKL CPU doesn't work for Lightroom CC; anyone had success ?

on FX I couldn't get it launched at all

@ForresterAlex

This comment has been minimized.

Copy link

ForresterAlex commented Feb 23, 2020

on FX I couldn't get it launched at all

On FX you should be using MKL_DEBUG_CPU_TYPE=4 instead of 5

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 23, 2020

on FX I couldn't get it launched at all

On FX you should be using MKL_DEBUG_CPU_TYPE=4 instead of 5

is that a joke?) I am the one who made a video about those commands

@ForresterAlex

This comment has been minimized.

Copy link

ForresterAlex commented Feb 23, 2020

I believe one of the posts above mentions that you have to use a 4 for FX a MN d below, would link, but on mobile, I'm just repeating what was said above, my system is ryzen, I'm using =5

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 23, 2020

I believe one of the posts above mentions that you have to use a 4 for FX a MN d below, would link, but on mobile, I'm just repeating what was said above, my system is ryzen, I'm using =5

besides of me no one here mentioned mkl=4, so I am the original source and I am the only one who found the alternative commands, do you really think I would forget what to use? :) again - lightroom is not working at all on FX

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Feb 23, 2020

When using the fixes above for Photoshop, I was able to get Premier 2020, Lightroom Classic 2020, and Photoshop 2020 fully working.
However I'm stuck on After Effects with the following error:

When I run: "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe After Effects 2020/Adobe After Effects 2020.app/Contents/MacOS/After Effects'"

error "objc[10995]: Class AdobeSimpleURLSession is implemented in both /Applications/Adobe After Effects 2020/Adobe After Effects 2020.app/Contents/Frameworks/pie.framework/Versions/A/pie (0x1332b6540) and /Applications/Adobe After Effects 2020/Adobe After Effects 2020.app/Contents/Frameworks/cclibmanager.framework/Versions/A/cclibmanager (0x12ff6d3b8). One of the two will be used. Which one is undefined.
2020-02-22 16:54:45.462 After Effects[10995:10724194] AdobeCrashReporterInitialize: executionTime = 0.003606 seconds
2020-02-22 16:54:45.485 AdobeCRDaemon[10996:10724519] CR dialog Preference for force quit 1
2020-02-22 16:54:48.292 AdobeCRDaemon[10996:10724520] exitStatus: 0" number 1011

Any ideas?

Hi Alex
Is that the complete stdout of your After Effects run?
I don't use After Effects but for the trial version the original method described in the gist works.
Alternatively you could try this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Library/Application\ Support/Adobe/Plug-Ins/CC/File\ Formats/Camera\ Raw.plugin/Contents/MacOS/Camera\ Raw
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Library/Application\ Support/Adobe/Plug-Ins/CC/File\ Formats/Camera\ Raw.plugin/Contents/MacOS/Camera\ Raw

BTW this Camera Raw patch should also work for Photoshop as an alternative to the complete removal.

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Feb 23, 2020

MKL CPU doesn't work for Lightroom CC; anyone had success ?

Seems to be the same issue as with Lightroom Classic. This could help:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ CC/Adobe\ Lightroom.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/Current/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ CC/Adobe\ Lightroom.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/Current/CameraRaw

This helps starting the app here. But I don't know if it works correctly, I don't use it...

@ForresterAlex

This comment has been minimized.

Copy link

ForresterAlex commented Feb 24, 2020

alansleep

I regret to inform you that, you are wrong, someone did mention that in order to use fx series and older CPUs you need to use MLK=4.

it's only the first comment
https://gist.github.com/XLNCs/86d7a391e46f85a04d28db171656b458#file-adobefixamd
in case you can't scroll to the top for some reason.

#ID crash fix:-

Run the app binary with MKL_DEBUG_CPU_TYPE=5 flag from terminal.

Example:

MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ InDesign\ 2020/Adobe\ InDesign\ 2020.app/Contents/MacOS/Adobe\ InDesign\ 2020

NOTE:

For FX and lower CPU's , you will need to use MKL_DEBUG_CPU_TYPE=4 flag.

In response to gassluk, you appear to be confusing me with someone else, I was attempting to get premire working, not after effects. I ended up getting premire to work with an MLK=5 flag. Thanks for the response though, and I will keep that in mind if I ever do try to work with after effects, as none of this works on linux at all, and I'm hoping that with my MacOS system finally working, windows can sit on a dusty old HDD in it's current ubootable state due to the very casual method of copying only the main partition onto an unused laptop HDD.

@DustUnderBag

This comment has been minimized.

Copy link

DustUnderBag commented Feb 24, 2020

Without Close.app Terminal has to be closed manually, I preffer automatisation)

Heh, worked flawlessly to me

gif

Here I copied the icon from PS to the applet and renamed it. No Terminal popping. Might upload code later, idk still busy atm.
EDIT2:
Automatic scripts here: https://github.com/jogerj/Adobe-AMD-Fix

EDIT:
Here's how you make your own:

  1. Open Script Editor
  2. Paste code: do shell script "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/Adobe Photoshop 2020'"
  3. File > Export (as Application), use whatever file name like Run Adobe Photoshop 2020.app
  4. (Optional) Copy PS icon to applet: cp '/Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/Resources/PS_AppIcon.icns' 'PATH/TO/Run Adobe Photoshop 2020.app/Contents/Resources/applet.icns'
  5. Place Run Adobe Photoshop 2020.app anywhere you like, then pin to your dock if you want

Hi, some error occurred when I use your install.sh.
Please select your CPU: 2
/Volumes/macHDD/Downloads/Adobe-AMD-Fix-master/Install.sh: line 100: syntax error near unexpected token )' /Volumes/macHDD/Downloads/Adobe-AMD-Fix-master/Install.sh: line 100: *) echo "Not implemented yet!";;'
yin@n219073014026 ~ %

@jogerj

This comment has been minimized.

Copy link

jogerj commented Feb 24, 2020

Hi, some error occurred when I use your install.sh.

whoops missed some semicolons. fixed that! try it again

@DustUnderBag

This comment has been minimized.

Copy link

DustUnderBag commented Feb 27, 2020

Hi, some error occurred when I use your install.sh.

whoops missed some semicolons. fixed that! try it again

The same error persists :(
Not sure if it is because I've already deleted unsupported files then made a DIY Photoshop launcher before using your script.

@frankieboy69

This comment has been minimized.

Copy link

frankieboy69 commented Feb 27, 2020

Thanks for all the tips here ladies and gents. Managed to get Photoshop working but Lightroom is still continuing to refuse to work. Any ideas? Thanks.

@frankieboy69

This comment has been minimized.

Copy link

frankieboy69 commented Feb 27, 2020

Further to my last post I'm getting this:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007ffeea18cff8
Exception Note: EXC_CORPSE_NOTIFY

@alansleep

This comment has been minimized.

Copy link

alansleep commented Feb 28, 2020

Let's pretend that I'm a complete newb(maybe not so much with the pretending) and I want to run this. Can you walk me through it step by step. I've tried downloading the package and dragging the .sh file into terminal but that didn't work so I think I'm missing a step or two.

This IS the step-by-step guide for complete newbies :) If you don't know how to find and launch script editor - no one can help. You even miss the export and launch in .app and do that in .sh, why people just can't read

@alansleep

This comment has been minimized.

Copy link

alansleep commented Mar 2, 2020

I GOT IT WORKING WITHOUT SCRIPTS!!!!) And it works for every app you want, not only the Photoshop.

  1. open Terminal and run command "cd desktop" then "nano Adobe\ Photoshop\ 2020"
  2. inside nano editor paste without quotes "MKL_DEBUG_CPU_TYPE=4 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2021"
  3. press ctrl + X then Y then Enter
  4. run command "chmod +x Adobe\ Photoshop\ 2020"
  5. close the Terminal and go to the folder /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/
  6. rename file "Adobe Photoshop 2020" to "Adobe Photoshop 2021"
  7. drag and drop file "Adobe Photoshop 2020" from Desktop into this folder (MacOS)
  8. Enjoy! now even if you launch the Photoshop by clicking "open with" on any image - it will run with MKL_DEBUG_CPU_TYPE=4 (or whatever command you want)

If you find this helpful please toss a like to my video https://youtu.be/SkStHcT3Axs

@arachule

This comment has been minimized.

Copy link

arachule commented Mar 3, 2020

I GOT IT WORKING WITHOUT SCRIPTS!!!!) And it works for every app you want, not only the Photoshop.

  1. open Terminal and run command "cd desktop" then "nano Adobe\ Photoshop\ 2020"
  2. inside nano editor paste without quotes "MKL_DEBUG_CPU_TYPE=4 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2021"
  3. press ctrl + X then Y then Enter
  4. run command "chmod +x Adobe\ Photoshop\ 2020"
  5. close the Terminal and go to the folder /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/
  6. rename file "Adobe Photoshop 2020" to "Adobe Photoshop 2021"
  7. drag and drop file "Adobe Photoshop 2020" from Desktop into this folder (MacOS)
  8. Enjoy! now even if you launch the Photoshop by clicking "open with" on any image - it will run with MKL_DEBUG_CPU_TYPE=4 (or whatever command you want)

If you find this helpful please toss a like to my video https://youtu.be/SkStHcT3Axs

Nice work.. It works fine.. but during application opening process it goes to 'no response '' mode for a few seconds so it opens a little bit late..But still the best solution .. Thank you.. I used same method for Adobe Indesign too, It works as well but the same issue is there again ..By the way because of my cpu is ryzen I used MKL_DEBUG_CPU_TYPE=5 instead of MKL_DEBUG_CPU_TYPE=4

@gokieks

This comment has been minimized.

Copy link

gokieks commented Mar 7, 2020

I GOT IT WORKING WITHOUT SCRIPTS!!!!) And it works for every app you want, not only the Photoshop.

  1. open Terminal and run command "cd desktop" then "nano Adobe\ Photoshop\ 2020"
  2. inside nano editor paste without quotes "MKL_DEBUG_CPU_TYPE=4 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2021"
  3. press ctrl + X then Y then Enter
  4. run command "chmod +x Adobe\ Photoshop\ 2020"
  5. close the Terminal and go to the folder /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/
  6. rename file "Adobe Photoshop 2020" to "Adobe Photoshop 2021"
  7. drag and drop file "Adobe Photoshop 2020" from Desktop into this folder (MacOS)
  8. Enjoy! now even if you launch the Photoshop by clicking "open with" on any image - it will run with MKL_DEBUG_CPU_TYPE=4 (or whatever command you want)

If you find this helpful please toss a like to my video https://youtu.be/SkStHcT3Axs

Tried this with both Photoshop and Lightroom Classic (CPU type 5, as I'm on a Ryzen 3900X), and neither worked. With PS, it will start but say cannot verify CC subscription status:
Screen Shot 2020-03-07 at 02 13 46 PM

Using the provided scripts for PS2020 does work:
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/MMXCore.plugin/Contents/MacOS/MMXCore
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/PlugIns/Required/Extensions/FastCore.plugin/Contents/MacOS/FastCore
sudo rm -rf /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Deep_Font
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Library/Application\ Support/Adobe/Plug-Ins/CC/File\ Formats/Camera\ Raw.plugin/Contents/MacOS/Camera\ Raw
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Library/Application\ Support/Adobe/Plug-Ins/CC/File\ Formats/Camera\ Raw.plugin/Contents/MacOS/Camera\ Raw

And just running it from Terminal using MKL_DEBUG_CPU_TYPE=5 does too:
MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2020

With LR Classic, I used this modified script:
MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/MacOS/Adobe\ Lightroom\ Classic2
And renamed the file inside Contents/MacOS to "Adobe Lightroom Classic2", but whenever I try to run it I get an error saying it's not supported on this type of Mac:
Screen Shot 2020-03-07 at 02 19 23 PM

But the scripts for LR Classic does not:
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

Nor does trying to run it using MKL_DEBUG_CPU_TYPE=5 from Terminal:
MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/MacOS/Adobe\ Lightroom\ Classic

I'm running LR Classic 9.2 (latest), but downgrading to 9.1 and then running those didn't seem to work either.

@frankieboy69

This comment has been minimized.

Copy link

frankieboy69 commented Mar 7, 2020

I finally got Lightroom working! So delighted!! I had to used the script that someone put up here but I had to correct the path to the toolkit which wasn’t quite right.

@gokieks

This comment has been minimized.

Copy link

gokieks commented Mar 8, 2020

''Can not verify sub. Cc '' I think it is something about crack.. just try Adobe Zii to patch PS again. and be sure your camera raw is not updated automatically. if so just Use Camera Raw 9.12.1
http://download.adobe.com/pub/adobe/photoshop/cameraraw/mac/9.x/CameraRaw_9_12_1_mac.zip which is advised by XLNC ..

My apps are not cracked - I'm an actual paying customer of Adobe CC. So if this method actually requires the apps to be pirated versions to work, then yeah, I guess I won't be bothering with it.

I suppose I shouldn't be surprised that a (large?) portion of the people who are trying to run Adobe apps on AMD hackintoshes are pirating. Not casting aspersions (since I myself have definitely pirated Photoshop in the past), but that's very much not something I'm interested in doing anymore when I can justify the $10/mo. subscription cost for Photoshop and Lightroom.

@arachule

This comment has been minimized.

Copy link

arachule commented Mar 8, 2020

Uppss.. :D ...Probably it somehow crashing online subscription... So just ask adobe costumer service but tell them about your HAckintosh system which is also a kind of pirating :D And I really have no idea if this methods for only for pirated ones...

''Can not verify sub. Cc '' I think it is something about crack.. just try Adobe Zii to patch PS again. and be sure your camera raw is not updated automatically. if so just Use Camera Raw 9.12.1
http://download.adobe.com/pub/adobe/photoshop/cameraraw/mac/9.x/CameraRaw_9_12_1_mac.zip which is advised by XLNC ..

My apps are not cracked - I'm an actual paying customer of Adobe CC. So if this method actually requires the apps to be pirated versions to work, then yeah, I guess I won't be bothering with it.

I suppose I shouldn't be surprised that a (large?) portion of the people who are trying to run Adobe apps on AMD hackintoshes are pirating. Not casting aspersions (since I myself have definitely pirated Photoshop in the past), but that's very much not something I'm interested in doing anymore when I can justify the $10/mo. subscription cost for Photoshop and Lightroom.

Uppss.. :D ...Probably it somehow crashing online subscription... So just ask adobe costumer service but tell them about your HAckintosh system which is also a kind of pirating :D And I really have no idea if this methods for only for pirated ones...

@d4vid1

This comment has been minimized.

Copy link

d4vid1 commented Mar 8, 2020

Add to your default shell configuration file (~/.bashrc for bash, ~/.zshrc for zsh etc) the line "export MKL_DEBUG_CPU_TYPE=5" without "".
Its worked for me, without to create a Run File in MacOS Folder of Photoshop or Illustrator.

Original: here

@nikoelt

This comment has been minimized.

Copy link

nikoelt commented Mar 9, 2020

I'm guessing no one has so far found a solution for warp stabilization in either PP or AE yet? I get crashes no matter what I try; funnily if I warp stabilize in windows, the result can be worked in MacOS environment including tracking - so what I currently do is create my project in MacOS, then once I have finished with everything there, I reboot into windows, warp stabilize the things I need and then reboot into macos and continue working on the project from there

@frankieboy69

This comment has been minimized.

Copy link

frankieboy69 commented Mar 9, 2020

Would anyone happen to have a fix for Adobe DNG converter? Thanks.

@hunterahon

This comment has been minimized.

Copy link

hunterahon commented Mar 10, 2020

Does anyone have a fix for Adobe Illustrator's cropping tool? It crashes immediately after using it.

Thanks

@arachule

This comment has been minimized.

Copy link

arachule commented Mar 10, 2020

Does anyone have a fix for Adobe Illustrator's cropping tool? It crashes immediately after using it.

Thanks

it works if you open illustrator using terminal with code MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Illustrator\ 2020/Adobe\ Illustrator.app/Contents/MacOS/Adobe\ Illustrator
or you can use the way provided by alansleep

'' GOT IT WORKING WITHOUT SCRIPTS!!!!) And it works for every app you want, not only the Photoshop.

open Terminal and run command "cd desktop" then "nano Adobe\ Photoshop\ 2020"
inside nano editor paste without quotes "MKL_DEBUG_CPU_TYPE=4 /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/MacOS/Adobe\ Photoshop\ 2021"
press ctrl + X then Y then Enter
run command "chmod +x Adobe\ Photoshop\ 2020"
close the Terminal and go to the folder /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/
rename file "Adobe Photoshop 2020" to "Adobe Photoshop 2021"
drag and drop file "Adobe Photoshop 2020" from Desktop into this folder (MacOS)
Enjoy! now even if you launch the Photoshop by clicking "open with" on any image - it will run with MKL_DEBUG_CPU_TYPE=4 (or whatever command you want)''

@arachule

This comment has been minimized.

Copy link

arachule commented Mar 10, 2020

Add to your default shell configuration file (~/.bashrc for bash, ~/.zshrc for zsh etc) the line "export MKL_DEBUG_CPU_TYPE=5" without "".
Its worked for me, without to create a Run File in MacOS Folder of Photoshop or Illustrator.

Original: here

can you explain exactly how you managed this ... I couldn't get it work

@d4vid1

This comment has been minimized.

Copy link

d4vid1 commented Mar 10, 2020

Add to your default shell configuration file (~/.bashrc for bash, ~/.zshrc for zsh etc) the line "export MKL_DEBUG_CPU_TYPE=5" without "".
Its worked for me, without to create a Run File in MacOS Folder of Photoshop or Illustrator.
Original: here

can you explain exactly how you managed this ... I couldn't get it work

hi

open Terminal and copy and past

for Zsh:

echo "export MKL_DEBUG_CPU_TYPE=5" >> ~/.zshrc

for Bash:

echo "export MKL_DEBUG_CPU_TYPE=5" >> ~/.bashrc

have a fun!

@alansleep

This comment has been minimized.

Copy link

alansleep commented Mar 11, 2020

have a fun!

I tried that couple of weeks ago and it only works if you launch apps through the Terminal, at least on High Sierra

@arachule

This comment has been minimized.

Copy link

arachule commented Mar 12, 2020

''I tried that couple of weeks ago and it only works if you launch apps through the Terminal, at least on High Sierra''
yes I either got it worked.. It is same for Mojave, too. You should run app via terminal so still alansleep's solutions is the best one ...

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Mar 15, 2020

I realized there was an error in my initial comment for LR classic fix: The two commands were in the wrong order. They have to be like this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

Of course the 0x3A->0x1A part has to be replaced before the 0x5A->0x3A otherwise it cannot work!
Please fix the gist accordingly. And sorry for the misinformation...

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Mar 15, 2020

Yet another solution to the environment variable problem. Found it based on this article:

Create a launch agent which sets a global environment variable at boot.
The following snippet enables MKL_DEBUG_CPU_TYPE=5 for ALL apps started after this launch agent has started.

For single user install, paste this in the terminal:

AGENT=~/Library/LaunchAgents/environment.plist

cat << EOF > ${AGENT}
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">
<dict>
 <key>Label</key>
 <string>mkl-debug</string>
 <key>ProgramArguments</key>
 <array>
 <string>sh</string>
 <string>-c</string>
 <string>launchctl setenv MKL_DEBUG_CPU_TYPE 5;</string>

 </array>
 <key>RunAtLoad</key>
 <true/>
</dict>
</plist>
EOF

launchctl load ${AGENT}
launchctl start ${AGENT}

NOTE:

  • If you want to install it for all users, omit the tilde in the AGENT variable.
  • Alter the number value (5) to a lower number for older AMD architectures (e.g. MKL_DEBUG_CPU_TYPE 4 for FX)
  • You have to wait a few seconds after the Finder has started in order for this to take effect. Maybe anyone finds a way to have the lauch agent started earlier.
@arachule

This comment has been minimized.

Copy link

arachule commented Mar 15, 2020

AGENT=~/Library/LaunchAgents/environment.plist

cat << EOF > ${AGENT}

Label mkl-debug ProgramArguments sh -c launchctl setenv MKL_DEBUG_CPU_TYPE 5; RunAtLoad EOF

launchctl load ${AGENT}
launchctl start ${AGENT}

Nice workkk... Thanks man it works flawless. I tried it for PS, AI and ID. So as you mentioned It seems ıt works for every app..

@alansleep

This comment has been minimized.

Copy link

alansleep commented Mar 16, 2020

Yet another solution to the environment variable problem. Found it based on this article:

flawless work, man!)

@Isaabella

This comment has been minimized.

Copy link

Isaabella commented Mar 16, 2020

Screenshot at Mar 16 13-19-23
im with this problem "your order could not be completed due to a program error" anyone have a soluction?

@pradorocchi

This comment has been minimized.

Copy link

pradorocchi commented Mar 21, 2020

This seems to work for Lightroom Classic, but the app will crash mentioning code signature.
You can run sudo codesign --remove-signature /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app to remove codesignature from the app and it will work then.

(...) but if you remove code signature the app will fail in other ways (no network) and it doesn't connect to Adobe CC so you can't use it.

You can re-code-sign the app, after removing the original signature. Have you tried to re-codesign it to run locally?

MacOS will fully recognize it like any original codesigned app [but only permitted to be executed on the specific machine that you have recodesigned the app] (you would have to re-codesign it locally again on any other machine if you copy the app to other machine, to be codesigned validated and correctly run)

Try this please:

sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

I dont have the adobe app right now on my machine, otherwise I would have tried re-codesigning it before asking you to try to recodesign it. But I consider valid to explain it, hoping that it helps you and solve the codesign problem.

@nikoelt

This comment has been minimized.

Copy link

nikoelt commented Mar 22, 2020

@gasseluk's method has now started working with Warp Stabilize in Premiere Pro and After Effects. Bravo!

Unfortunately 3D Camera Tracker makes the application shutdown completely after 'analyze' step is complete. This is the case for MP4, ProRes and Raw DNG. Can not get it work. Has anyone else tried?

@lpffernando

This comment has been minimized.

Copy link

lpffernando commented Mar 23, 2020

lightroom doesn't work , both 9.1 and 9.2.

@lpffernando

This comment has been minimized.

Copy link

lpffernando commented Mar 23, 2020

Lightroom works, there are two CameraRaw files, so I changed both the files, and it works!
/Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
/Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

@mycorunner

This comment has been minimized.

Copy link

mycorunner commented Mar 28, 2020

I realized there was an error in my initial comment for LR classic fix: The two commands were in the wrong order. They have to be like this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

Of course the 0x3A->0x1A part has to be replaced before the 0x5A->0x3A otherwise it cannot work!
Please fix the gist accordingly. And sorry for the misinformation...

Still not working, even patched the version A as well. Any advice? which version did you try?

Screen Shot 2020-03-28 at 5 00 10 PM

@hvrsh

This comment has been minimized.

Copy link

hvrsh commented Mar 29, 2020

Thanks! Photoshop is working but Lightroom and Illustrator is not working. Only loading screen is fixed after that it just crash as usual.

@yarik67777

This comment has been minimized.

Copy link

yarik67777 commented Mar 31, 2020

Hello! Faced the problem of launching lightroom, I tried everything that is written above, as a result of errors and crashes

lavs-iMac-Pro ~ % MKL_DEBUG_CPU_TYPE=4 /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/MacOS/Adobe\ Lightroom\ Classic 2020-03-31 17:50:24.752 Adobe Lightroom Classic[648:11250] AdobeCrashReporterInitialize: executionTime = 0.005093 seconds *** GPU Warning: Special file 'TempDisableGPU3' found -- skipping GPU3 *** zsh: illegal hardware instruction MKL_DEBUG_CPU_TYPE=4

what am I doing wrong?

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented Apr 3, 2020

Hello! Faced the problem of launching lightroom, I tried everything that is written above, as a result of errors and crashes

lavs-iMac-Pro ~ % MKL_DEBUG_CPU_TYPE=4 /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/MacOS/Adobe\ Lightroom\ Classic 2020-03-31 17:50:24.752 Adobe Lightroom Classic[648:11250] AdobeCrashReporterInitialize: executionTime = 0.005093 seconds *** GPU Warning: Special file 'TempDisableGPU3' found -- skipping GPU3 *** zsh: illegal hardware instruction MKL_DEBUG_CPU_TYPE=4

what am I doing wrong?

Not sure if this applies for you, but if you're on a ryzen or newer AMD CPU, "MKL_DEBUG_CPU_TYPE=4" needs to be "MKL_DEBUG_CPU_TYPE=5"

@yarik67777

This comment has been minimized.

Copy link

yarik67777 commented Apr 5, 2020

Not sure if this applies for you, but if you're on a ryzen or newer AMD CPU, "MKL_DEBUG_CPU_TYPE=4" needs to be "MKL_DEBUG_CPU_TYPE=5"

just the same, I'm using AMD Fx 6300, in one case or another, the terminal writes: *** GPU Warning: Special file 'TempDisableGPU3' found - skipping GPU3 ***
GPU nvidia geforce gt 640 kepler

@KameraKasino

This comment has been minimized.

Copy link

KameraKasino commented Apr 6, 2020

AGENT=~/Library/LaunchAgents/environment.plist

cat << EOF > ${AGENT}

Label mkl-debug ProgramArguments sh -c launchctl setenv MKL_DEBUG_CPU_TYPE 5; RunAtLoad EOF

launchctl load ${AGENT}
launchctl start ${AGENT}

That's dope!! Nice!

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 11, 2020

Hello friends,
Thanks for great info up there. All latest apps work except LR and Bridge. Did someone make LR and Bridge work?

@romancin

This comment has been minimized.

Copy link

romancin commented Apr 18, 2020

This patches work for Lightroom Classic, tested on 9.2 and 9.2.1:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 21, 2020

Tried that but no go with fresh Catalina/Adobe CC installed. LR Crashed instantly.

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 21, 2020

@lpffernando

Lightroom works, there are two CameraRaw files, so I changed both the files, and it works!
/Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
/Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

What did you change to make LR work. Still no luck here.

Thanks

@TheDemonBarber

This comment has been minimized.

Copy link

TheDemonBarber commented Apr 25, 2020

I wonder if anyone here has a fix or and idea of how to fix After Effects? Specifically Warp Stabiliser or 3D Camera Track which both cause crashes. On a Ryzen 3900X.

Initially, they wouldn't load... Fixed with the terminal commands at the top of this page.
Then Warp Stabiliser or 3D Camera Tracker would crash the program the moment you apply them... Fixed that with the MKL environment agent fix (thanks @gasseluk).

Now, much like @nikoelt, they apply and analyse, but the moment they get past analysis and actually try to do the applying of the effect, it crashes out immediately. Both Warp and 3D Cam Track. Warp weirdly works in Premiere, but not in AE.

@yarik67777

This comment has been minimized.

Copy link

yarik67777 commented Apr 25, 2020

Эти патчи работают для Lightroom Classic, протестированной на 9.2 и 9.2.1.

не работает fx-6300

@alansleep

This comment has been minimized.

Copy link

alansleep commented Apr 25, 2020

Эти патчи работают для Lightroom Classic, протестированной на 9.2 и 9.2.1.

не работает fx-6300

я уже писал, что на эфыксах он не работает

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 26, 2020

The patch provided here does not work with LR 9.2, 9.2.1/Catalina. Whoever made it work please share your experience in detail.

The only location of "CameraRaw" is under CameraRaw.lrtoolkit/Version/A. There are 2 other locations: CameraRaw.lrtoolkit and CameraRaw.lrtoolkit/Version/A/current but those are alias.

I tried many different way but none work so far. After patch, LR crash without crash report. Whoever create the original patch please fine tune so it can work with latest LR version.

Thank you very much.

@romancin

This comment has been minimized.

Copy link

romancin commented Apr 26, 2020

The patch provided here does not work with LR 9.2, 9.2.1/Catalina. Whoever made it work please share your experience in detail.

The only location of "CameraRaw" is under CameraRaw.lrtoolkit/Version/A. There are 2 other locations: CameraRaw.lrtoolkit and CameraRaw.lrtoolkit/Version/A/current but those are alias.

I tried many different way but none work so far. After patch, LR crash without crash report. Whoever create the original patch please fine tune so it can work with latest LR version.

Thank you very much.

Captura de pantalla 2020-04-26 a las 22 40 26

It is not my case, working perfectly here on Catalina 10.15.4 with supplemental update. Only used latest Adobe Zii and used the patches I said 8 days ago. Ryzen 5 3600 here, Gigabyte Aorus B450 M.

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 26, 2020

Could you please copy & paste the exact command line used. Because i could not made it work over here. LR crash instantly after patch. Thanks

@gasseluk

This comment has been minimized.

Copy link

gasseluk commented Apr 26, 2020

Could you please copy & paste the exact command line used. Because i could not made it work over here. LR crash instantly after patch. Thanks

Please note that there is still an error in the Gist at the top of this page. The two commands have to be executed in reverse order otherwise it won't work. See my comment here:
https://gist.github.com/XLNCs/86d7a391e46f85a04d28db171656b458#gistcomment-3213925

Works here with High Sierra and most recent version from Creative Cloud Subscription.

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 26, 2020

@gasseluk

I did notice your post up there and follow that order. I did uninstall and reinstall LR. Still no luck. In what exactly location of CameraRaw did you patch?

_The only location of "CameraRaw" is under CameraRaw.lrtoolkit/Version/A. There are 2 other locations: CameraRaw.lrtoolkit and CameraRaw.lrtoolkit/Version/A/current but those are alias.

Thanks

@polymax2016

This comment has been minimized.

Copy link

polymax2016 commented Apr 27, 2020

My Lightroom would crash after the patch too. The initial logo would come on screen then crash within 1 second. I had to add

sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

The program would then start and ask for acess to something on the Mac. I "always allowed" it and now everything is good

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 27, 2020

@polymax2016

Finally, it works with the "codesign"

Thank you very much.

@hvrsh

This comment has been minimized.

Copy link

hvrsh commented Apr 29, 2020

Now I got problem with Photoshop, everything is working fine except "Photoshop Object Selection Tool". Whenever I click on Object selection tool Photoshop 2020 Crashes so bad.

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented Apr 30, 2020

I used gasseluk script and command lines from the top. Works great include object selection.

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented May 1, 2020

@polymax2016

My Lightroom would crash after the patch too. The initial logo would come on screen then crash within 1 second. I had to add

sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

The program would then start and ask for acess to something on the Mac. I "always allowed" it and now everything is good

Did you run?
sudo codesign --remove-signature /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

Or Just?
sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented May 1, 2020

The second one, -fs-

It will ask me to enter password all the time even I click "always allowed" but I'll live with that

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented May 1, 2020

Cool, thanks. Very much appreciate the quick response.
I can definitely live with that too!

Do you know if this works on legit CC?
I'm doing this for a friend and am trying to convince him to use Zii, seems more certain to work, but it's uphill.

So just to be certain, you did:

  1. gasseluk script
  2. commands from top
  3. sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

In that order?

@ngocrebel

This comment has been minimized.

Copy link

ngocrebel commented May 1, 2020

I'm not sure if Gasseluk script is needed for LR. I did that right after installed CC apps so they could launch. If you use more than just LR then I think it need.

  1. Gasseluk script

  2. Command in reverse order like this:
    sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

  1. sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

The above fix doesn't have anything to do with CC subscription. It only makes LR classic launch and run on Ryzentosh. You need subscription or Adobe Zii to make it works after trial.

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented May 1, 2020

Awesome, thanks so much for the detailed reply @ngocrebel

I did manage to catch the need to reverse those(saw above warning), but appreciate the heads up.

@gokieks above couldn't open photoshop or lightroom, and got a dialog popup "cannot verify subscription status",
is this because of the nano editor solution causing the error with the cc subscription?
Thanks for your help, sorry for the noob questions.

@lucaslimapnn

This comment has been minimized.

Copy link

lucaslimapnn commented May 6, 2020

Good evening! I hope someone helps me! So, I use photoshop 2020 on high sierra, my computer is a ryzan 5 and NVIDIA GeForce GTX 1050 Ti 4095 MB video card.
My photoshop has some problems, it crashes when I use filters or make selections, sometimes it keeps loading, or else it closes. I don't have the money to invest now. THE
Can someone help me?

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented May 7, 2020

Good evening! I hope someone helps me! So, I use photoshop 2020 on high sierra, my computer is a ryzan 5 and NVIDIA GeForce GTX 1050 Ti 4095 MB video card.
My photoshop has some problems, it crashes when I use filters or make selections, sometimes it keeps loading, or else it closes. I don't have the money to invest now. THE
Can someone help me?

@lucaslimapnn You'll almost certainly need to disable your graphics card or force it to be an iGPU. Technically, high sierra may support nvidia in a couple of cases, but as osx software gets updated such as photoshop, support for nvidia even on high sierra is becoming near nonexistent. Did you use OpenCore or Clover? If you can, I recommend doing a clean install of catalina using opencore 0.5.8.

  1. Make sure you follow this guide:
    https://dortania.github.io/OpenCore-Desktop-Guide/

  2. Then disable your dgpu or force it to be an igpu:
    https://khronokernel.github.io/How-to-disable-your-unsupported-GPU-for-MacOS/

  3. Then copy and paste this to terminal, and press enter. This elegant solution was kindly provided above thanks to @gasseluk:

AGENT=~/Library/LaunchAgents/environment.plist

cat << EOF > ${AGENT}
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">
<dict>
<key>Label</key>
<string>mkl-debug</string>
<key>ProgramArguments</key>
<array>
<string>sh</string>
<string>-c</string>
<string>launchctl setenv MKL_DEBUG_CPU_TYPE 5;</string>

</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
EOF

launchctl load ${AGENT}
launchctl start ${AGENT}

  1. Next copy and paste the relevant patches from the top of this page to terminal. Just run the patches relevant to your version. if you use photoshop 2020, just use the patches under ps2020, or whatever year version you have respectively. You can run all the commands for photoshop at the top of this page safely if this doesn't make sense. The commands that are for a different year version of PS will just do nothing. so it is safe to run all the commands at the top of this page regarding photoshop.

  2. Install this:
    http://download.adobe.com/pub/adobe/photoshop/cameraraw/mac/9.x/CameraRaw_9_12_1_mac.zip

  3. good to go

@frankieboy69

This comment has been minimized.

Copy link

frankieboy69 commented May 7, 2020

I can't get Lightroom 9 working, but here is my Lightroom 8.2 fix if this helps anyone:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic\ CC/Adobe\ Lightroom\ Classic\ CC.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic\ CC/Adobe\ Lightroom\ Classic\ CC.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented May 7, 2020

Yet another solution to the environment variable problem. Found it based on this article:

Create a launch agent which sets a global environment variable at boot.
The following snippet enables MKL_DEBUG_CPU_TYPE=5 for ALL apps started after this launch agent has started.

For single user install, paste this in the terminal:

AGENT=~/Library/LaunchAgents/environment.plist
......```

@gasseluk A method to get this to launch faster seems to be omitting the tilde. I didn't have priveleges to do this as admin, tried sudo, still said I didn't have priveleges, so I enabled root access: https://support.apple.com/en-ca/HT204012 then created a txt file in System/Library/LaunchAgents. Copied and pasted your code, omitting tilde. Renamed to environment.plist, and now seems to take hold instantly at bootup.

Thanks so much for providing this solution btw

@pradorocchi

This comment has been minimized.

Copy link

pradorocchi commented May 7, 2020

Yet another solution to the environment variable problem. Found it based on this article:
Create a launch agent which sets a global environment variable at boot.
The following snippet enables MKL_DEBUG_CPU_TYPE=5 for ALL apps started after this launch agent has started.
For single user install, paste this in the terminal:

AGENT=~/Library/LaunchAgents/environment.plist
......```

@gasseluk A method to get this to launch faster seems to be omitting the tilde. I didn't have priveleges to do this as admin, tried sudo, still said I didn't have priveleges, so I enabled root access: https://support.apple.com/en-ca/HT204012 then created a txt file in System/Library/LaunchAgents. Copied and pasted your code, omitting tilde. Renamed to environment.plist, and now seems to take hold instantly at bootup.

Thanks so much for providing this solution btw

Hi,

about the privileges and launchAgent..
LauchAgents are only loaded after the user login

you can change it to a LaunchDaemon, and put inside /Library/LaunchDaemons

LaunchDaemons are user independent and are loaded on boot time, before the GUI login comes up
It serves for any user which will later login on MacOS

Differently than LaunchAgents, which will only be executed (scripts, daemons, whatever) after the user successfully login on the GUI interface

I prefer LaunchDaemons because that characteristic.
And, you can put it inside /Library/LaunchDaemons (which is accessible and writable for any admin user) instead of
/System/Library/(...) which is a system protected directory

anyway, either under /system/Library or /Library
what is important is:

anything under (...)/LaunchAgents are only executer AFTER some user successfully LogIn on the GUI Desktop
and anything under (...)LaunchDaemons are user-independent and are executed on boot time before the MacOS GUI comes up

/System/Library/LaunchDaemons: stuff here are Apple system daemons, and are executed on boot-time, before the GUI login
/Library/LaunchDaemons: stuff here are free to be added by any admin, and are execute on boot-time, before the GUI comes up

/System/Library/LaunchAgents: stuff here are basically Apple stuff, which will be executed/loaded AFTER ANY user LogIn on the GUI
/Library/LaunchAgents: stuff here are free to be added, and will be executed AFTER ANY user logs in on GUI via his user/password on the GUI login

there is a third case, which is ~/Library/LaunchAgents , which refers to "~" which means /User/THELOGGEDUSER/Library/LaunchAgents and will only be executed for that such user.

On previous OSX versions there had existed ~/LaunchDaemons, but not anymore (since El Capitan) so, the valid options are the options I mentioned above.

(PS: I haven't read the complete thread above, only last portions of it, so I don't know if i am being redundant to add something that another member has already has mentioned... but anyway, since I just received this thread email update, I have considered that the above information may be valid for someone... sorry if it is redundant or if someone already had mentioned it. Later I will read all replies, but please consider my intention to aggregate something here which may be valid about MacOS processes startup things :)

Thanks!
:)

@polymax2016

This comment has been minimized.

Copy link

polymax2016 commented May 11, 2020

I know this a bit off topic, but I have searched all over for an answer/remedy. I sometimes use alien skin/ exposure x5 as a plug in to photoshop and Lightroom. I have both photoshop and Lightroom running, but exposure crashes on startup in both programs and as a stand alone. Does anyone have this running? I would appreciate any ideas.
I had a problem with Nik collection plug-ins hanging at startup in photoshop and Lightroom. Once I started the Nik components up as stand alone programs and closed them out, they then were able to open up in plug-in form also. No such luck with exposure though.
Thanks

@binauraloptions

This comment has been minimized.

Copy link

binauraloptions commented May 12, 2020

@pradorocchi
Thank you very much for the insight. You weren't redundant (I've read this entire thread) and the info was highly appreciated!

Does the term "Daemon" consistently mean something that will run at boot prior to GUI login? I mean it in a general sense outside of just OSX, like if someone downloaded a Daemon tool for windows, would that mean it starts at boot prior to GUI login?

I'll switch my friend's ryzentosh I built for him to a LaunchDaemon next time I see him. But just curious, does it make sense that /Library/LaunchAgents would initialize faster than ~/Library/LaunchAgents? I do get that they both occur after GUI login whereas LaunchDaemons are faster and launch prior to GUI login. But /Library/LaunchAgents seems to run within a second of me logging in, whereas ~/Library/LaunchAgents can take 30 seconds to start.

@hunterahon

This comment has been minimized.

Copy link

hunterahon commented May 20, 2020

Thanks for all of the comments from everyone. I'm impressed that this thread is still going strong even after over a year.

Does anyone have a fix for the Adobe Illustrator crash for image trace? As soon as I click on it Illustrator crashes.

Any help would be greatly appreciated!

@avtarsingh1122

This comment has been minimized.

Copy link

avtarsingh1122 commented May 21, 2020

Sh*t I don't know what happened. Everything was working fine. I installed Photoshop, After Effects, Premiere Pro, Adobe XD. Premiere Pro was working fine out of the box. The rest three were crashing.
I used the above-mentioned commands for Photoshop and After Effects and then both were working absolutely fine. Also, Adobe XD started working fine.

Then after a few restarts, another day, Photoshop and Adobe XD are crashing.

Here is the log of Adobe Photoshop 2020

2020-05-21 11:31:52.374 Adobe Photoshop 2020[1101:25565] AdobeCrashReporterInitialize: executionTime = 0.002784 seconds
Creating new log file at: /Users/blablabla/Library/Logs/Adobe/Adobe Photoshop 2020//ACPL__2020-05-21_11-31-53-909506-+0530_00.log
2020-05-21 11:31:53.982 Adobe Photoshop 2020[1101:25705] Reachability Flag Status: xR ------- networkStatusForFlags
<4813581760> <DynamicLink> <5> Attempting to launch dynamiclinkmanager
<4813581760> <DynamicLink> <5> /Applications/Adobe Photoshop 2020/Adobe Photoshop 2020.app/Contents/MacOS/DynamicLinkMediaServer/dynamiclinkmanager.app
<4813581760> <DynamicLink> <5> Increase wait time to 2
[0521/113156.556456:ERROR:local_storage_context_mojo.cc(706)] Lost connection to database

Now I have tried using the above-mentioned commands but no luck

I am using Catalina 10.15.4 in a Ryzentosh

@DonkeyKongJr

This comment has been minimized.

Copy link

DonkeyKongJr commented May 21, 2020

Lightroom Classic crashes every time I import around 1k photos and then every time I restart Lightroom. Only a complete reinstallation fixes this starting issue, but after importing the photos again everything start from the beginning.

I did the script on the top in reverse order and the codesign.

Process:               Adobe Lightroom Classic [993]
Path:                  /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom Classic
Identifier:            com.adobe.LightroomClassicCC7
Version:               9.2.1 [202004070813-7699d98a] (9.2.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Adobe Lightroom Classic [993]
User ID:               501

Date/Time:             2020-05-21 12:47:27.595 +0200
OS Version:            Mac OS X 10.15.4 (19E287)
Report Version:        12
Anonymous UUID:        14036C20-23C2-3E22-B478-6210A0046543


Time Awake Since Boot: 720 seconds

System Integrity Protection: enabled

Crashed Thread:        12  Worker Thread

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x000070000e2c5ff8
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [993]

VM Regions Near 0x70000e2c5ff8:
    Stack                  000070000e243000-000070000e2c5000 [  520K] rw-/rwx SM=COW  thread 10
--> STACK GUARD            000070000e2c5000-000070000e2c6000 [    4K] ---/rwx SM=NUL  stack guard for thread 12
    Stack                  000070000e2c6000-000070000e4c8000 [ 2056K] rw-/rwx SM=COW  thread 12


@zhutson24

This comment has been minimized.

Copy link

zhutson24 commented May 26, 2020

Would there happen to be any fixes for Adobe Audition's Multitrack Session Remix function? Every time I run the remix, it crashes. Current Adobe Audition Version (13.0.1).

@acoffeeworld

This comment has been minimized.

Copy link

acoffeeworld commented May 29, 2020

Lightroom Classic (Version 9.1) seems to work with this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

Lightroom Classic (Version 9.1) seems to work with this:

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

Bro,I can‘t run Lr Classic ver9.1 after patch.My devices : R7 2700 + Aorus B450m +Rx 5500xt.
The Lr windows flash back after I run it.

@Sceko

This comment has been minimized.

Copy link

Sceko commented Jun 1, 2020

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ CC/Adobe\ Lightroom.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ CC/Adobe\ Lightroom.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

Work for Lightroom with export MKL_DEBUG_CPU_TYPE=5

@monkeyboyohyeah

This comment has been minimized.

Copy link

monkeyboyohyeah commented Jun 1, 2020

Does anyone have a fix for the Adobe Illustrator crash for image trace? As soon as I click on it Illustrator crashes.

+1 for this. Super annoying.

@monkeyboyohyeah

This comment has been minimized.

Copy link

monkeyboyohyeah commented Jun 1, 2020

MKL_DEBUG_CPU_TYPE=5 fix worked for ID, PS and IL for image trace/select colour range crashes.
Still get crashes periodically.

@alvarini

This comment has been minimized.

Copy link

alvarini commented Jun 3, 2020

MKL_DEBUG_CPU_TYPE=5 fix worked for ID, PS and IL for image trace/select colour range crashes.
Still get crashes periodically.

How to do with Illustrator? I tryed every path config with no success :/

@monkeyboyohyeah

This comment has been minimized.

Copy link

monkeyboyohyeah commented Jun 4, 2020

MKL_DEBUG_CPU_TYPE=5 fix worked for ID, PS and IL for image trace/select colour range crashes.
Still get crashes periodically.

How to do with Illustrator? I tryed every path config with no success :/

Depends on your version of each Adobe. For me it was;

MKL_DEBUG_CPU_TYPE=5 "/Applications/Adobe Photoshop CC 2019/Adobe Photoshop CC 2019.app/Contents/MacOS/Adobe Photoshop CC 2019"

I made apps to run each Adobe app. They were formatted like this (e.g. PS2019);

do shell script "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe Photoshop CC 2019/Adobe Photoshop CC 2019.app/Contents/MacOS/Adobe Photoshop CC 2019'"

I run ID 2020 and IL 2020 so just changed the paths as appropriate.

Hope this helps.

@alvarini

This comment has been minimized.

Copy link

alvarini commented Jun 4, 2020

MKL_DEBUG_CPU_TYPE=5 fix worked for ID, PS and IL for image trace/select colour range crashes.
Still get crashes periodically.

How to do with Illustrator? I tryed every path config with no success :/

Depends on your version of each Adobe. For me it was;

MKL_DEBUG_CPU_TYPE=5 "/Applications/Adobe Photoshop CC 2019/Adobe Photoshop CC 2019.app/Contents/MacOS/Adobe Photoshop CC 2019"

I made apps to run each Adobe app. They were formatted like this (e.g. PS2019);

do shell script "MKL_DEBUG_CPU_TYPE=5 '/Applications/Adobe Photoshop CC 2019/Adobe Photoshop CC 2019.app/Contents/MacOS/Adobe Photoshop CC 2019'"

I run ID 2020 and IL 2020 so just changed the paths as appropriate.

Hope this helps.

Thx so much for your answer.

I got running well image tracing in AI 2020 with
MKL_DEBUG_CPU_TYPE=5 /Applications/Adobe\ Illustrator\ 2020/Adobe\ Illustrator.app/Contents/MacOS/Adobe\ Illustrator

I will try to make a shell script like yours.

Thx

@hetaldesai

This comment has been minimized.

Copy link

hetaldesai commented Jun 4, 2020

any solution to fix a Adobe DNG Converter Version 12? it's crash on startup on MacOS Catalina 10.15.5.

@iiskuzii

This comment has been minimized.

Copy link

iiskuzii commented Jun 6, 2020

Seriously needing some help getting Lightroom 9.x to run on my Hackintosh. I have a 3900x and a Der Devil 5700xt GPU. Please let me know what other info is needed for help. It would be truly appreciated!

@sir-connofir

This comment has been minimized.

Copy link

sir-connofir commented Jun 8, 2020

Just wanted to give everyone a potential heads up about the functionality of the Spring/May 2020 Adobe updates on AMD.

Previously, the environment variable MKL_DEBUG_CPU_TYPE=5 needed to be set like this on both MacOS and Windows 10.
See here if you're curious: https://www.pugetsystems.com/labs/hpc/How-To-Use-MKL-with-AMD-Ryzen-and-Threadripper-CPU-s-Effectively-for-Python-Numpy-And-Other-Applications-1637/

Anyway, after I updated Adobe CC, Warp Stabilizer in AE began crashing. Removing the environment variable fixed this. Prior to the update AE would have crashed at launch without the environment variable. (This is on windows, I'll be updating Adobe on my MacOS system later today, but I'm expecting the same result, as this should be the result of, "MKL looks for 'Genuine Intel' and if it doesn't find that it drops to a code path only optimized to SSE2 instruction level i.e. no modern hardware optimizations."

What would be AMAZING is if there was a script that could set MKL_DEBUG_CPU_TYPE=5 only when an application was checking for 'genuine intel', then deletes the variable right after the check, ensuring it doesn't get in the way of any other applications.

Imagine an 'Interrupt' that'd take the form of a 'Listener'. It'd wait for the instruction corresponding to the checking of 'genuine intel', set MKL_DEBUG_CPU_TYPE=5, resume the actual checking of 'genuine intel', then the MKL_DEBUG_CPU_TYPE=5 would force the rest of the operation to follow an optimized code path, at which point the environment variable MKL_DEBUG_CPU_TYPE=5 is deleted, and that'd mark the end of the interrupt.

It'd be minimally invasive, instead of being applied to an entire application or system, MKL_DEBUG_CPU_TYPE=5 in the above idea would only exist for the stack calls that require it.

However, I don't understand how MKL_DEBUG_CPU_TYPE=5 caused warp stabilizer in AE to crash, and once the environment variable was deleted worked perfectly. I thought setting MKL_DEBUG_CPU_TYPE=5 globally was fine, and basically couldn't interfere?

@mazen-khalil1

This comment has been minimized.

Copy link

mazen-khalil1 commented Jun 8, 2020

I need fix to Adobe Lightroom CC 2019

@mazen-khalil1

This comment has been minimized.

Copy link

mazen-khalil1 commented Jun 8, 2020

Anything for lightroom CC?

@mazen-khalil1

This comment has been minimized.

Copy link

mazen-khalil1 commented Jun 9, 2020

Anything for lightroom CC not Classic ?

@polymax2016

This comment has been minimized.

Copy link

polymax2016 commented Jun 9, 2020

iiskuzii, I have a 3700x and red devil 5700xt also. Running the following one by one in terminal worked for me.

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

sudo codesign -fs - /Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app

@acoffeeworld

This comment has been minimized.

Copy link

acoffeeworld commented Jun 10, 2020

iiskuzii,我也有3700x和紅色魔鬼5700xt。在終端中逐一運行以下內容對我來說很有效。

sudo perl -i -pe's | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x5A \ x00 | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x3A \ x00 | sg'/ Applications / Adob​​e \ Lightroom \ Classic / Adob​​e \ Lightroom \ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe's | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x3A \ x00 | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x1A \ x00 | sg'/ Applications / Adob​​e \ Lightroom \ Classic / Adob​​e \ Lightroom \ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw

sudo perl -i -pe's | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x3A \ x00 | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x1A \ x00 | sg'/ Applications / Adob​​e \ Lightroom \ Classic / Adob​​e \ Lightroom \ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

sudo perl -i -pe's | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x5A \ x00 | \ x90 \ x90 \ x90 \ x90 \ x56 \ xE8 \ x3A \ x00 | sg'/ Applications / Adob​​e \ Lightroom \ Classic / Adob​​e \ Lightroom \ Classic.app/Contents/Frameworks/CameraRaw.lrtoolkit/Versions/A/CameraRaw

sudo codesign -fs-/ Applications / Adob​​e \ Lightroom \ Classic / Adob​​e \ Lightroom \ Classic.app

Hello Bro.It works on my r7 2700 with MacOS 10.15.5 . B-T-Y, I want to know how you run PS2020 .The Photoshop patch only allowed me to open the software, but it crashed after I imported the images

@polymax2016

This comment has been minimized.

Copy link

polymax2016 commented Jun 11, 2020

Yes I'm running PS2020. Version 21.1.2. Catalina 10.15.4
It's working fine for me opening images back and forth with Lightroom

@rafaeldrincon

This comment has been minimized.

Copy link

rafaeldrincon commented Jun 12, 2020

Yes I'm running PS2020. Version 21.1.2. Catalina 10.15.4
It's working fine for me opening images back and forth with Lightroom

Hey Guys... Having similar issues here. X570 Aorus Ultra 3900X OS X 10.15.5 64G RAM Rig.
LR Running Fine so far, but PS2020 when I try to use content aware fill. Opening RAW images or editing from LR works fine.

I hope someone will find a solution soon :)

Thanks in advance for any suggestions.

@kittywhiskers

This comment has been minimized.

Copy link

kittywhiskers commented Jun 14, 2020

Worked on a bash script that should automate the patching process... AMDAdobePatch.sh

Warning: Might break activation in applications like Bridge CC due to subsequent failed integrity checks when querying Adobe activation servers

@ar13kn

This comment has been minimized.

Copy link

ar13kn commented Jun 14, 2020

This worked for After Effects.

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x3A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' /Library/Application\ Support/Adobe/Plug-Ins/CC/File\ Formats/Camera\ Raw.plugin/Contents/MacOS/Camera\ Raw

sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x5A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' /Library/Application\ Support/Adobe/Plug-Ins/CC/File\ Formats/Camera\ Raw.plugin/Contents/MacOS/Camera\ Raw

sudo codesign --remove-signature /Applications/Adobe\ After\ Effects\ 2020/Adobe\ After\ Effects\ 2020.app

@Sceko

This comment has been minimized.

Copy link

Sceko commented Jun 15, 2020

@alvarini

This comment has been minimized.

Copy link

alvarini commented Jun 15, 2020

PH2020 crashing too with Color Region selection. Patch applied but not running with MKL_DEBUG_CPU_TYPE=5

@LLf13

This comment has been minimized.

Copy link

LLf13 commented Jun 15, 2020

PH2020 crashing too with Color Region selection. Patch applied but not running with MKL_DEBUG_CPU_TYPE=5

Same for me. What I found out is that if you want to adjust for example hue/saturation, you can uncheck the preview box and you will be able to apply these changes. This might work for the other filters as well, however I did not test it yet.

MKL_DEBUG_CPU_TYPE=5 sadly is no option for me because I get a program error if I open a file.

I really hope there will be a fix in the near future.

@yurkins

This comment has been minimized.

Copy link

yurkins commented Jun 23, 2020

Photoshop Font crash fix :-
#PS2020 21.2.0
sudo rm -rf /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Sensei_Models/Deep_Font

@surajmandalcell

This comment has been minimized.

Copy link

surajmandalcell commented Jun 23, 2020

Photoshop Font crash fix :-
#PS2020 21.2.0
sudo rm -rf /Applications/Adobe\ Photoshop\ 2020/Adobe\ Photoshop\ 2020.app/Contents/Required/Sensei_Models/Deep_Font

Why are fonts crashing ps and others?

@hossamtarek

This comment has been minimized.

Copy link

hossamtarek commented Jun 23, 2020

What about the new Camera Raw in PS2020 21.2.0 ? Does it work on ryzen ?

@TobiMiller

This comment has been minimized.

Copy link

TobiMiller commented Jun 26, 2020

lightroom crashes when trying to use person/face detection. after that it crashes on each start. you cannot leave the person tab.

@XLNCs

This comment has been minimized.

Copy link
Owner Author

XLNCs commented Jun 28, 2020

Gist is now moved here :
https://gist.github.com/naveenkrdy/26760ac5135deed6d0bb8902f6ceb6bd

please continue the further discussions there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.