Constant stuck MIDI notes using Kontakt VI's. Any fix...??

[Eric Lambert]

Originally Posted by innerbooty

Thanks for all these replies! Somehow I didn't get email notifications of any replies, which is odd... It is happening right now like CRAZY using the Kontakt Symphony Series Woodwind, so I was logging back in simply to vent. It happens all the time on various Session Strings intruments... Since most of you seem to be on Kontakt 8, wonder if they addressed a bunch of stuff in Kontakt 8??

My question would be - I remember being really shocked and frustrated when I upgraded from Kontakt 6 to Kontakt 7 and realized there was ZERO upward compatability. I just got messages saying Kontakt 6 not available, and it didn't bring up all my instruments and patches in the new Kontakt 7 plugin. I had to rebuild everything. That's why I haven't upgraded to 8. I can't afford to have to rebuild all my instruments and settings. Is Kontakt 7 upwardly compatible to Kontakt 8?? Thanks for the help!!

I'm not exactly sure what you mean by rebuilding instruments and settings but if you're talking about the quickload instruments, yes, unfortunately those need to be rebuilt. I've had to do it with each Kontakt upgrade and it's rather annoying because I have many. I've asked around about a way to transfer them between old and new versions but have never received a response.

[innerbooty]

Basically, unless I'm doing something wrong or mistaken, when I upgraded to Kontakt 7, it left Kontakt 6 in place and added Kontakt 7 as what was essentially a new plugin. I'm thinking that what really might have bummed me out was that maybe Kontakt 6 wasn't Silicon compatible (?), so it showed up disabled when I brought up all the old Pro Tools sessions I had been working on in my pre-silicon setup. And I was reading on the Native Instruments site yesterday about all these migration hoops you have to jump through to port your existing Kontakt instances over to your upgraded Kontakt instances. And they recommend not doing it for any Pro Tools sessions that are currently active, which does not inspire confidence. Is it just me, or is that a weird way to go about a plugin upgrade?? Am I missing something?


So it seems the only answer to my stuck note problem for now is to go through every instance of Kontakt and poke around looking for those "note off" settings? I can't risk upgrading to Kontakt 8 while in the middle of a bunch of big, Kontakt heavy projects

[Marsdy]

Originally Posted by innerbooty

Basically, unless I'm doing something wrong or mistaken, when I upgraded to Kontakt 7, it left Kontakt 6 in place and added Kontakt 7 as what was essentially a new plugin. I'm thinking that what really might have bummed me out was that maybe Kontakt 6 wasn't Silicon compatible (?), so it showed up disabled when I brought up all the old Pro Tools sessions I had been working on in my pre-silicon setup. And I was reading on the Native Instruments site yesterday about all these migration hoops you have to jump through to port your existing Kontakt instances over to your upgraded Kontakt instances. And they recommend not doing it for any Pro Tools sessions that are currently active, which does not inspire confidence. Is it just me, or is that a weird way to go about a plugin upgrade?? Am I missing something?


So it seems the only answer to my stuck note problem for now is to go through every instance of Kontakt and poke around looking for those "note off" settings? I can't risk upgrading to Kontakt 8 while in the middle of a bunch of big, Kontakt heavy projects

K8 doesn’t overwrite K7.

You could try installing K8, then move K7 out of the plug in folder. Then when you open a session with K7 instances, they will automatically get replaced with K8 instances.

[innerbooty]

Thanks, that's good intel! Still might wait till I'm done with my current projects. Can't afford to have current Kontakt instrument settings or any library stuff get messed up...

[Eric Lambert]

Yes, it was common to keep multiple versions of Kontakt present in the plugins folder for those cases where you have to open older sessions which used older versions of K. What I was saying above is that that is FINALLY no longer necessary. Ver 8 is all you need as it converts K6/K7 instances to K8. I don't know if it also handles K5 instances -- I haven't tried it.

And Kontakt 6 was before Silicon and would require Rosetta if being used on a Silicon machine. Or, just use K8!

[innerbooty]

Got it, thanks! This is all good to know. And yes, part of my problem was that switch to silicon compatability between v6 and v7, which made the upgrrade to v7 extra painful. Glad to know that's in the rear view mirror now!

[Marsdy]

Originally Posted by Eric Lambert

Yes, it was common to keep multiple versions of Kontakt present in the plugins folder for those cases where you have to open older sessions which used older versions of K. What I was saying above is that that is FINALLY no longer necessary. Ver 8 is all you need as it converts K6/K7 instances to K8. I don't know if it also handles K5 instances -- I haven't tried it.

And Kontakt 6 was before Silicon and would require Rosetta if being used on a Silicon machine. Or, just use K8!

Nope it won’t open K5 instances. At least it didn’t here!

[Eric Lambert]

Originally Posted by Marsdy

Nope it won’t open K5 instances. At least it didn’t here!

Bummer. I was hoping it extended back to that version but I'm happy it covers K6 and K7.