![]() Running the following one by one in terminal worked for me. Iiskuzii, I have a 3700x and red devil 5700xt also. I thought setting MKL_DEBUG_CPU_TYPE=5 globally was fine, and basically couldn't interfere? 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. 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. 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. Imagine an 'Interrupt' that'd take the form of a 'Listener'. ![]() 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. (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. ![]() Prior to the update AE would have crashed at launch without the environment variable. Removing the environment variable fixed this. Previously, the environment variable MKL_DEBUG_CPU_TYPE=5 needed to be set like this on both MacOS and Windows 10.Īnyway, after I updated Adobe CC, Warp Stabilizer in AE began crashing. Just wanted to give everyone a potential heads up about the functionality of the Spring/May 2020 Adobe updates on AMD.
0 Comments
Leave a Reply. |