Any Win11 Kontakt 8 users here?

[BobF]

K8 ver 8.8.0 here. Never an issue.
Did you relocate anything.
As a failsafe. Run Kontakt 8 as standalone. It will look for any or all related files in your library. Also run Komplete Kontrol as standalone. This will also update.
Then update your plugin manager in Studio Pro. All simple and quick fixes. Should iron things out for you.

Standalone is also a problem, so that's what I'm troubleshooting with.

 

[BobF]

Not sure I made this clear up front:
K8 is functioning perfectly both standalone and as a plugin. All libs are present and usable as are all controllers and audio interfaces.

The only symptom is the zombie process that gets left behind on exit. This of course hangs whatever DAW it is used in as well.

Whatever the problem is, it is deep - perhaps simple to solve once found, but it is nothing on the surface. I suspect there is a driver release problem preventing K8 from fully unspooling.

Komplete Kontrol works and exits cleanly both standalone and as a plug as long as I don't load K8.

At this point I have done a K8 root canal and will install K7 to see what happens.

Thanks to all for the feedback and ideas so far.

 

[lokeyfly]

I see Sintil8 also suggested the standalone rebuild. Sorry, I didnt mean to step on his suggestion here. : ) I didn't see that.

Is it now better?

 

[sintil8]

BobF,

just a thought and out of curiosity, in Device Manager, Sound Music and Games controllers and also Software Devices is anything changing when you load Kontakt and is any change hanging around after you have closed it?

Regards as always.

 

[Vocalpoint]

K8 is functioning perfectly both standalone and as a plugin. All libs are present and usable as are all controllers and audio interfaces.

The only symptom is the zombie process that gets left behind on exit. This of course hangs whatever DAW it is used in as well.

Bob

I documented this heavily yesterday in the v8.2.0 release thread.

There is definitely something going on with FSP (8.1.1, 8.1.2 AND now 8.2.0) when an instance of either Komplete Kontrol OR Kontakt 8 is part of any session. If this condition exists - Studio Pro.exe for certain - will be trapped in running memory once the session has been closed. Confirmed yesterday after exhaustive testing and reported to both Fender Support and my contacts at NI

This appears to be solely resting on flaws within Kontakt 8.13.1 for certain. And it also appears that this is a NI thing to address.

Until we see a v8.14 of Kontakt 8 - we need to live with this.

VP

 

[BobF]

Bob

I documented this heavily yesterday in the v8.2.0 release thread.

There is definitely something going on with FSP (8.1.1, 8.1.2 AND now 8.2.0) when an instance of either Komplete Kontrol OR Kontakt 8 is part of any session. If this condition exists - Studio Pro.exe for certain - will be trapped in running memory once the session has been closed. Confirmed yesterday after exhaustive testing and reported to both Fender Support and my contacts at NI

This appears to be solely resting on flaws within Kontakt 8.13.1 for certain. And it also appears that this is a NI thing to address.

Until we see a v8.14 of Kontakt 8 - we need to live with this.

VP

Thanks. I knew I wasn't crazy!! K7 is working flawlessly

 

[BobF]

I see Sintil8 also suggested the standalone rebuild. Sorry, I didnt mean to step on his suggestion here. : ) I didn't see that.

Is it now better?

*rebuild* of K8 was no joy. However, K7 works flawlessly as it should.

 

[Vocalpoint]

And then I found this as well:

DAW process remains stuck after closing when Kontakt and Massive X are loaded - Community

I have found a reproducible issue when Kontakt 7 or Kontakt 8 and Massive X are loaded at the same time in a DAW. The issue occurs with both VST2 and VST3 versions of Massive X. Tested systems: * Windows 10 Pro * Windows 11 Pro Tested DAWs: * Cubase 15.0.30 * Gig Performer 5.3.3 Native...

community.native-instruments.com

Massive X is also a potential trouble spot as well.

VP

 

[BobF]

And then I found this as well:

DAW process remains stuck after closing when Kontakt and Massive X are loaded - Community

I have found a reproducible issue when Kontakt 7 or Kontakt 8 and Massive X are loaded at the same time in a DAW. The issue occurs with both VST2 and VST3 versions of Massive X. Tested systems: * Windows 10 Pro * Windows 11 Pro Tested DAWs: * Cubase 15.0.30 * Gig Performer 5.3.3 Native...

community.native-instruments.com

Massive X is also a potential trouble spot as well.

VP

I saw this in my diggings, but the reported combination with MassiveX didn't fit. I did find a lot of generic hanging Kontakt process troubleshooting steps though.

I do wish the specific K8 hang was more broadly published - would've saved me days of downtime and headaches.

Oh well ... now I know to watch for a K8 update.

 

[Vocalpoint]

I do wish the specific K8 hang was more broadly published - would've saved me days of downtime and headaches.

Me too. NOW I know why I was getting a bizarre series of oddball crashes and other nonsense in FRSP 8.1.2 over the last few weeks. Could not really nail it down and now - after all this testing - the culprit has been Kontakt 8 all along.

Kontakt 8 adheres to a very specific update cadence (usually every 6 weeks) and the last was on Sept 3 - so we should see a new release here any day now..

VP

 

[Vocalpoint]

All

Just heard back from my main contact (no pun intended) from NI and he is now checking into this.

Also did a quick series of tests with Komplete Kontrol specifically - and can confirm that KK does not cause this issue - as long as it is loaded with a non-Kontakt instrument or content. I loaded up Form (Reaktor based) then Diva (u-He) and finally Jun-6 V (Arturia) and did my usual quick test with each of these.

Upon addition and then removal of all these instances from an empty test track - I exited the session, then exited FSP 8.1.2 and checked Task Manager - and there were no lingering instances of Studio Pro.exe.

This is 100% a Kontakt 8.13 issue for certain.

VP

 

[lokeyfly]

I'm going to hang with K8 v8.8.0 because with Massive loading all of the time, and every other part of Komplete Ultimate (12, I think), its a rock. But I get there are so many variables. Just thinking of the "If it works...." line. But if I hear anything that helps, I'll chime in. There's enough talent here on it.

Digging the retired life, guys. Sitting out back, animal sounds in the woods, birds chirping, geese migrating, woodoeckers pecking, mocking birds, mocking....... etc. Time to sample some of this.

 

[BobF]

All

Just heard back from my main contact (no pun intended) from NI and he is now checking into this.

Also did a quick series of tests with Komplete Kontrol specifically - and can confirm that KK does not cause this issue - as long as it is loaded with a non-Kontakt instrument or content. I loaded up Form (Reaktor based) then Diva (u-He) and finally Jun-6 V (Arturia) and did my usual quick test with each of these.

Upon addition and then removal of all these instances from an empty test track - I exited the session, then exited FSP 8.1.2 and checked Task Manager - and there were no lingering instances of Studio Pro.exe.

This is 100% a Kontakt 8.13 issue for certain.

VP

I did much of the same with non-Kontakt instruments. I'm thinking maybe 8.12 and earlier are OK. Might try it later

 

[TheMaartian]

Digging the retired life, guys. Sitting out back, animal sounds in the woods, birds chirping, geese migrating, woodoeckers pecking, mocking birds, mocking....... etc. Time to sample some of this.

Cool! If you're interested in building a library of those samples instead of just using individual samples, check out the free Decent Sampler (if you're not aware of it). FLOE is a new sampler that's very good, but creating libraries for it requires more serious LUA programming.

DecentSampler

Making DecentSampler libraries/presets/instruments

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[Vocalpoint]

I did much of the same with non-Kontakt instruments. I'm thinking maybe 8.12 and earlier are OK. Might try it later

I rolled my main DAW back to v8.12 after yesterday's debacle.

V8.1.2 behaves identical to v8.20 with Kontakt 8.

Pretty sure this has zero to do with FSP - any version. This is a Kontakt 8.13.1 issue for certain.

VP

 

[BobF]

I rolled my main DAW back to v8.12 after yesterday's debacle.

V8.1.2 behaves identical to v8.20 with Kontakt 8.

Pretty sure this has zero to do with FSP - any version. This is a Kontakt 8.13.1 issue for certain.

VP

FYI - 8.12.0 also hangs for me

 

[BobF]

I went back to 8.8.1 ( @lokeyfly ) and everything functions properly; standalone and inside FSP 8.2

I also tested KK w/K8 standalone. No problems there either

 

[Vocalpoint]

I went back to 8.8.1 ( @lokeyfly ) and everything functions properly; standalone and inside FSP 8.2

I also tested KK w/K8 standalone. No problems there either

Great work Bob.

My gut feel is that 8.13.0 is the definitive problem. Would not surprise me if 8.12 was fine too - maybe you can give that one a go too?

If it bears fruit - I would be good to revert back to 8.12. here as well.

VP

 

[BobF]

Great work Bob.

My gut feel is that 8.13.0 is the definitive problem. Would not surprise me if 8.12 was fine too.

VP

I tried 8.12 before 8.8. 8.12 was still broken for me.

 

[Vocalpoint]

I tried 8.12 before 8.8. 8.12 was still broken for me.

Whoa - OK. Thanks for that.

VP