Menu
What's new
By:
Filters

Kontakt is causing Logic to hard crash - anyone else?

danstein

danstein

dismember
Hi -

I have already opened a support ticket with NI, but their support system seems pretty borked. Among other things, there is a screen saying that for every request I submit, NI will open a ticket and send me an email with a link to that ticket. This is absolutely not the case - I have opened two tickets in the last few days, and the only reply I have gotten is an automated email for each request giving me a ticket number - but no link.

Anyhow - I made few changes to my system recently and I'm not sure what caused the problem, but I am finding that Kontakt 7 Player is causing Logic to hard crash when I load an instrument. I am on what I think are the most recent versions of all the software: Mac OS 14.2.1; Logic 10.8.1; Kontakt 7 Player 7.7.3.

There is a troubleshooting article on the NI website covering Kontakt crashes, and I have followed all the steps: Give Full Disk Access to Kontakt and NI Daemon; Rebuild database; Trash and rebuild prefs; Turn of data sharing\

Kontakt will open and load instruments without issue running standalone, but if I instantiate it inside Logic, it will hard crash Logic as soon as I try to load an instrument. One interesting data point is that once it has crashed, if I reopen Logic and try to load the same instrument into a Kontakt 6 instance, it will also crash.

So it seems like there is some sort of database corruption happening within (or relative to) Logic. I did see, in one thread, a mention of trashing a certain Logic file (Logic cs file was referred to) but there wasn't enough information to deduce what file they meant.

Anyone have any ideas about this? @EvilDragon maybe?

Thanks all for any thoughts!
Click to read more...
 
danstein said:
Hi -

I have already opened a support ticket with NI, but their support system seems pretty borked. Among other things, there is a screen saying that for every request I submit, NI will open a ticket and send me an email with a link to that ticket. This is absolutely not the case - I have opened two tickets in the last few days, and the only reply I have gotten is an automated email for each request giving me a ticket number - but no link.

Anyhow - I made few changes to my system recently and I'm not sure what caused the problem, but I am finding that Kontakt 7 Player is causing Logic to hard crash when I load an instrument. I am on what I think are the most recent versions of all the software: Mac OS 14.2.1; Logic 10.8.1; Kontakt 7 Player 7.7.3.

There is a troubleshooting article on the NI website covering Kontakt crashes, and I have followed all the steps: Give Full Disk Access to Kontakt and NI Daemon; Rebuild database; Trash and rebuild prefs; Turn of data sharing\

Kontakt will open and load instruments without issue running standalone, but if I instantiate it inside Logic, it will hard crash Logic as soon as I try to load an instrument. One interesting data point is that once it has crashed, if I reopen Logic and try to load the same instrument into a Kontakt 6 instance, it will also crash.

So it seems like there is some sort of database corruption happening within (or relative to) Logic. I did see, in one thread, a mention of trashing a certain Logic file (Logic cs file was referred to) but there wasn't enough information to deduce what file they meant.

Anyone have any ideas about this? @EvilDragon maybe?

Thanks all for any thoughts!
Click to expand...
Today Kontakt 7.8.0 came out. Hopefully that will solve your problems.
 
Sadly, that did not fix the issue. Same problem, Kontakt 7 works fine standalone but crashes inside Logic. I am wondering if something in my Logic setup got corrupted. Still welcoming suggestions!
 
Just to pin down a few details: When you say Logic is "hard crashing", you mean Logic is immediately closing without any popups? Or are you getting a popup saying "An audio unit plugin encountered a problem", etc? If you open Console (in Applications, in the Utilities folder) and click "Crash Reports" in the left-hand column, do you see entries there for Logic Pro? Do you also see entries for AUHostingServiceXPC_arrow (which hosts the plugins)? [Edit: Also, you're not loading Logic or Kontakt in Rosetta, are you?]

[Edit 2] Also, by "when I load an instrument", do you mean it crashes as soon as you insert Kontakt 6 or 7 into the instrument slot of a channel in Logic? Or can you create an empty instance of Kontakt, open the plugin window, etc, and only have it crash when you load a Kontakt instrument? What happens if open an old project that already has Kontakt instruments set-up?

If Logic is crashing without a popup, and the crash reports are for Logic and not AUHostingService, then it's probably worth troubleshooting Logic rather than Kontakt. It may still be a Kontakt issue, but I've had loads of plugins - including Kontakt - crash in lots of very undignified ways, yet they've never crashed Logic. The troubleshooting steps for Logic are here.
 
Last edited:
@aldous - thanks for asking for clarification and apologies for not being clear enough in my initial post.

By "hard crashing" I mean that Logic quits immediately, no popups or error messages other than the OS popup saying that Logic has crashed and do I want to send a report. I had not checked the Apple Console, but now that you suggested it I took a look and yes, there are crash reports for both Logic Pro and AUHostingServiceXPC_arrow. I am not running anything under Rosetta.

By "load an instrument" I mean that I am able to load an empty instance of Kontakt. It is when I try to load an .nki into the empty instance that the crash occurs. As to opening an old project - to be honest, most of my old projects use entirely Kontakt 6, whereas this seems to be a Kontakt 7 issue. I will have to hunt to find an instance of K7 in an older project or try to remember where one is.

Since my previous post, I tried opening Ableton Live 11. I was able to load multiple instances of K7 (and load .nkis into them) without trouble, so it does point to this being a Logic issue.

I see a pretty extensive troubleshooting list at the link you posted - thanks! I will run through those and see if anything there solves it for me.
 
...and I'm back. Thanks to @aldous for pointing me in the right direction. Step 4 of Apple's troubleshooting protocol is "Disconnect External Devices" and lo and behold - it turns out it's my brand new S88 that is causing the trouble. Makes sense since it's the only new device I have added recently. I think all the software on the S88 is up-to-date but I'll open (another) ticket with NI and see what happens.
 
danstein said:
...and I'm back. Thanks to @aldous for pointing me in the right direction. Step 4 of Apple's troubleshooting protocol is "Disconnect External Devices" and lo and behold - it turns out it's my brand new S88 that is causing the trouble. Makes sense since it's the only new device I have added recently. I think all the software on the S88 is up-to-date but I'll open (another) ticket with NI and see what happens.
Click to expand...
“Brand new” - how long ago did you add it, and have you done a complete system restart since?
 
danstein said:
...and I'm back. Thanks to @aldous for pointing me in the right direction. Step 4 of Apple's troubleshooting protocol is "Disconnect External Devices" and lo and behold - it turns out it's my brand new S88 that is causing the trouble. Makes sense since it's the only new device I have added recently. I think all the software on the S88 is up-to-date but I'll open (another) ticket with NI and see what happens.
Click to expand...
That was fast! This looks very similar to this report, which links to older versions of various libraries... so I guess could try rolling one back and see if that helps?

I also meant to say: the .cs file you mentioned, that's Step 10 in the Logic troubleshooter. The report I linked above said it didn't help, but just FYI.
 
@aldous - interesting find. I can look further down that road, as in fact it seems that not all libraries that are causing this crash. Will test further.
 
danstein said:
Added it 3 days ago, and yes, I have done several complete restarts (including rebooting my UA Apollos.)
Click to expand...
That's weird! Of all the hardware that should work flawlessly with Kontakt, it would be a NI keyboard. Apparantly not. Have you tried another controler?
But glad to hear you found the culprit.
 
It looks more and more like it is an issue with libraries that haven't been updated for the latest Komplete Kontrol. I wouldn't have noticed it prior to getting the S88 since I have been sticking primarily to K6, and only using K7 Player for libs that are not K6-compatible.

I guess for the problematic libs I'll have to stick to loading them into K6 if/until they get updated for better Komplete Kontrol compatibility. Great, another list of things to keep track of, I was running out of those (LOL)
 
danstein said:
...and I'm back. Thanks to @aldous for pointing me in the right direction. Step 4 of Apple's troubleshooting protocol is "Disconnect External Devices" and lo and behold - it turns out it's my brand new S88 that is causing the trouble. Makes sense since it's the only new device I have added recently. I think all the software on the S88 is up-to-date but I'll open (another) ticket with NI and see what happens.
Click to expand...
I had the same problems, it's due to N.I. Hardware MK3 with Sonoma. Kontakt 7 was always a "hard Logic crash". Workaround tip in the N.I. forum was to load via Komplete Kontrol.
In the end I brought the 88MK3 back and connected my old Roland and everything worked fine again. Sonoma has not yet been officially released for some N.I. Stuff so it seems although it has been on the market for over half a year. The interface to the hardware between Apple and N.I. is still a big construction site. Thats sad, hoped the new update 7.8. fixed this better..
 
Oof, sorry to hear about that @muddyblue.

I'm glad to say that overall I'm pretty happy with the S88 other than this issue. I bought it without testing since no one in the States has them, at least not near me. I was a bit worried about the feel of the action based on the complaints I had heard about the Mk2. It feels fine to me, a bit stiff straight out of the box but it's already loosening up so I expect there are some bushings that needs get played in a little. The polyphonic aftertouch was a big draw for me at it works really nicely, no need for excessive force to trigger it and it seems like there's enough room to give it quite a bit of nuance, but the action doesn't feel spongy. Nice job, Fatar!

Looks like I will just have to watch out for "Gotcha" libraries for a while and hope that NI and Apple get it sorted out eventually. I supposed I can give the "load via KK" option a try and see if that works.

Fingers crossed (those that aren't playing)
 
danstein said:
Oof, sorry to hear about that @muddyblue.

I'm glad to say that overall I'm pretty happy with the S88 other than this issue. I bought it without testing since no one in the States has them, at least not near me. I was a bit worried about the feel of the action based on the complaints I had heard about the Mk2. It feels fine to me, a bit stiff straight out of the box but it's already loosening up so I expect there are some bushings that needs get played in a little. The polyphonic aftertouch was a big draw for me at it works really nicely, no need for excessive force to trigger it and it seems like there's enough room to give it quite a bit of nuance, but the action doesn't feel spongy. Nice job, Fatar!

Looks like I will just have to watch out for "Gotcha" libraries for a while and hope that NI and Apple get it sorted out eventually. I supposed I can give the "load via KK" option a try and see if that works.

Fingers crossed (those that aren't playing)
Click to expand...
Then we hope that a solution comes as quickly as possible! An absurdity, but once again you can see how much the musicians mean to Apple ;)

I hope you enjoy it and hopefully no trouble for you with the fatar TP100 update.
 
EvilDragon said:
Action has been modified by NI, AFAIK. The regular Fatar TP/100LR is still not a very good keybed IMO.
Click to expand...
Yes, I should say "Nice job Fatar & NI!"

I'll also say that the overall build quality is very nice - all the encoders and wheels feel solid and have just about the right amount of resistance (although the 4-way-encoder part of the big knob is a little finicky for me.) I like the one-piece membrane cover over all the buttons, that seems like a good choice for longevity. I appreciate the added control over the onboard lights (you can dim them, change color, and turn the light guide on/off). The overall unit is surprisingly light for an 88-key weight action - compared to my old KX88, for sure!
 
EvilDragon said:
But yeah, Sonoma compatibility is being worked on, until you see this mentioned in the changelog for a new Kontakt version, it would be prudent not to update your OS if you can help it.
Click to expand...

I treated myself to a new M2 at the end of last year, but unfortunately Sonoma was already on it when I booted up the computer for the first time after installation. That was a shock, but everything worked until I plugged in MK3 hardware for the first time...
 
muddyblue said:
I treated myself to a new M2 at the end of last year, but unfortunately Sonoma was already on it when I booted up the computer for the first time after installation. That was a shock, but everything worked until I plugged in MK3 hardware for the first time...
Click to expand...
It took NI almost a year to bring the S61 mk2 to full functionality when that was released however many years ago, and that was before NI had been taken over. Nothing at NI seems better than it used to be, so I don't expect that the mk3 keyboards will be fully functional and working until they also have been out for nearly a year...
 
You must log in or register to reply here.
Top Bottom