I'm doing a very large orchestral template now, with 20+ kontakt instances.
I left one VSL instrument at 6th place the firsts 5 kontakt instruments. I think that there's a problem in that particular position.
No problems for now. Every instance I add I save a MIR project with incremental save (now I'm to 39 saved). I don't fully load every instance with articulations, just one or two per instance.
Incremental saving let's me to revert back to the previous saves, and every 1-2 saves I close MIR and reopen and see if it opens the project. Every 10 saves I reboot my PC and see if MIR opens.
If there's a problem, for me, it's not related by kontakt itself, but with generic 3rd party plugins. And in my opinion, it's totally non-related to protected or unprotected libraries and even less to 32 bit or 64 bit libraries (since you load the samples and the original kompakt player is totally absent in this workflow).

I' m fairly happy for now but I'm very very cautious about everything I do, in MIR. Like walking on a mine camp :-) (sometimes it crashes at loading the project, but I insist, and it opens)

This thread should be renamed to:
Problems with Kontakt 4 and MIR? There may be not an easy solution! But it's worth it! :-) 

Problems even with 3rd party plugins in the 16th position... let's put a VSL instrument there... And put the kontakt plugin in the 17th place.

Are we finding a solution? :-) 

Nice - and funny too! - to read all the different experiences and assumptions. Ok, maybe it get's a bit  esoteric - included myself.  [:D]

But normal, we are artists, right?

So, to say some practically - a new Kontakt update is available (4.1.3.). NI technic support gave me the hint. Does it mean good news?

Didn't try out it yet, later the day I will giving a feedback about.

Thanks Paoling for reply - very interesting. The work arounds are good and I feel the "purge feature" in the same way. 

Have noticed too in vi-control forum your MIR example for positioning and room was the most convincing. (Did not really be surprising for me.) Anyway, very interesting comparison. When MIR pro (with the possibilty using of audio tracks) starts to release, they all will switching to it, sooner or later. - Ok, a new allegation, but it seems not to be so esoteric, doesn't it?

Then Dietz should get the Nobel Prize for Peace for the idea of MIR, cause the rowings between composers and engineers are a shady past.

Kind regards

Frank

May I ask you out for a drink or two ...?  [D][D]

;-)

Another "could not load plugin" problem at the 20th place in MIR instrument list.

Ok. I have problems in loading kontakt plugins at 6th, 16th and 20th place in the instrument list; I don't know if moving instruments is going to  solve this. I load a vienna instrument instance in that place and everything works fine :-)

Anyone can confirm this issue? In my opinion it's a very strange although simple bug.

Paolo 

 The places (6, 16, 20) I can't confirm. I can confirm that a lot of vi pro instances (or more vi pro than kontakt instances) help to mostly avoid this message  a n d  the crashs on save.

I can recieve the undesirable massage with only 4 kontakt instances in a template too.

Today, a failed load of a MIR SE instance, showed me that MIR is in reality a kind of visual interface + reverb and positioning system of a Vienna Ensemble Pro program. 
I could not do something more than what I do in MIR, because busses are disabled, but it showed me all my MIR tracks in a VEPRO, with all the plugins loaded.  

This a confirmation that every VEPRO problem with third party plugins has a kind of counterpart in MIR.

It's no big secret that the underlying VST host of MIR and VEP relies on the same code-base. - It would be some serious waste of resources to develop different solutions for the same tasks. :-)

I'm wondering about a phenomenon which is sometimes a bit annoying and could be in connection to the problems mentioned above.  

At every change of different settings, like audio buffer settings, changes in preferences or changes of venues after the click on "ok"  MIR got a MIDI signal of somewhere - for the Kontakt instances only.

Since MIR build 1810 this MIDI signal will automaticly choked  - for  u n  protected librarys.

The protected 3rd part libs like BBB have a hang note, which can be stopped only by a new incoming midi signal of my sequencer or keyboard.

Does not happens with VI (pro) instances.

Could it be a hint for the causes of all the other issues? 

Frank

Yes, we are aware of this annoying new "feature". Your developers are already looking into it.

 O.k. So thanks for quick answer.