I'm using Pro Tools 2023.9 and Kontakt 7.7.0. When I insert Kontakt in a session, everything is fine - until I close the session and attempt to reopen it - then Pro Tools will freeze/SWOD if Kontakt was active in the session.
I've tried all of the steps listed in the 115004169849-KONTAKT-Crashes support article. I've also reported this issue on multiple occasions; back when the 7.4 update was released (#3973742), and again when 7.6 came out (#4063148), and so far the "support" I've received does falls far below what I would expect from an industry-leading software developer.
The only fix so far has been to deactivate Kontakt in my Pro Tools session every single time I close/quit, and then when I re-open I have to copy the Kontakt instance to a new insert, drag it over the original insert to replace it, and then re-assign all of my instrument channels.
I understand the way that software development works, and pressure that product managers feel to make the decisions they make. But let's face it, anyone who reviews the severity of this bug knows intuitively it's a blocker. And I guess that's what upsets me the most - support should be a customer advocate, raising our voices above the din of procedural updates and minor features when we are in pain. I think it's fair to say that the Kontakt roadmap hasn't been "on the pulse" of the customer for some time - we want stability, for our production environments and our fleeting muses.
So if you're a Native Instruments employee, please, please - all I can ask is that you escalate this to the Kontakt Product Manager and/or lead developer, advise them of the severity of this issue (and any others that have been confounding customers for months or years), and spend a development cycle doing some housekeeping. Your customers will love you for it far more than if you spent your time crafting some shiny new widget or store tie-in. Contrary to what you might think, we value seeing release notes that actually address issues.
I encourage the community to chime in here with a "+1" for anyone who thinks this sounds like their issue. From the research I've done, there are several potential other reports here on the forums, but no one has collectively brought attention to this in an organized way (see above support responses for an indication as to why). Here are some of those threads:
