Could this be the culprit? Has anybody who had SAC problems in Logic with Kontakt 5 noticed that they went away with Kontakt 6?Yepp... the CPU difference between VST and AU in Kontakt 5 disappeared in Kontakt 6 (no matter which host).
Do you mean we can test-drive a beta of full K6 for the purposes of resolving this issue?NI sent us a new private beta for K6 that should help further, based on their investigation of the issue. If you haven't had any luck, please email us and we'll send it to you. (We can't distribute it publicly.)
Hi Lance,UPDATE: with potential lead to fix, ISW:
I deleted my Kontakt Snapshot folder for SAC that I had imported from my 2017 studio. This temporarily fixed monstrously long spinning ball of death, but still crashed when I tried to import SOME (not all) instrument channels from older projects. Then the issue resumed pretty quickly and I am right back where I started with forever-long spinning balls and crashes. My guess is that ISW needs some work on backward compatibility with patches and snapshots saved with older versions of SAC. This has now caused 1.5 days of troubleshooting when I have deadlines only days away.
When we have the next Kontakt beta available, you will want to replace your current Kontakt plugin file with that of the new one using the same file name. This should allow Logic to load using the new version of Kontakt which should load the old project files just fine. If you install it as a plugin with a different name than your normal Kontakt plugin, Logic will still attempt to load the old one and still crash.Again, SAC is one of my favorite libraries and is irreplaceable. The reason I can't simply use another DAW or VI is that I am needing to get into dozens of project files from 2017 using SAC.
Product owner, actually.Dinos Vallianatos (lead Kontakt developer/programmer)