BTW - you _did_ disable Kontakt's option for handling multi-processor usage by itself, didn't you? It should be set to "host" .... sorry, I'm not in front of my system right now and can't look up the actual wording.

-> [URL]http://community.vsl.co.at/forums/p/26942/176593.aspx[/URL]

Thanks again Dietz.  Some updates.

1.  I have the multi-processing set to "off" in Kontakt 4 (as a VST Plug-in), my choices were off, 2, 3, 4, 5, 6, 7, or 8.

2.  If I close MIR, and only use Kontakt 4 Plug-ins and a track with a local VST2 of Vienna Imperial it works perfectly (all will play in unison flawlessly).

3.  After the updates to all the software (I did EVERYTHING, VI Pro, VE Pro, Vienna Suite, eLicenser, MIR, Roompacks, Kontakt is now 4.2.3) things are slightly different now (reversed).  Now, if I open my current project with 7 instances of Kontakt 4 plug-ins they all play fine.  Once I open MIR they still work fine, but MIR doesn't work (it lags and pops and clicks).  If I close everything and only have my DAW and MIR up, load a venue and load one patch MIR pops and clicks when playing my keyboard from my DAW (Loopbe is my midi transfer method between the two).

So now it seems that MIR is the issue and Kontakt works perfect as a stand alone, and as a plug-in with or without MIR running.  However MIR simply will not run properly with my DAW at this moment.  I restarted the machine, launched MIR and loaded one cello ensemble patch.  It worked great.  I then opened my DAW and created a new song.  I created one loopbe track pointing to the MIR cello patch and now it pops and clicks.  How strange.  I traded one problem for another lol :).

What is the best order to open these in?  MIR then DAW or DAW then MIR?

Thanks,

Maestro2be

I also want to add Dietz if this is even helpful, but if I take the exact same project and set everything up that I did in MIR, in VE Pro and use it that way instead it works flawlessly at 128 (6ms) latency.  Not one glitch running 25 instruments in unison all mixed of Kontakt instruments and 15 VSL instruments.  So the behavior is definitely MIR related specific.  Hopefully we can get this going because I prefer to work with MIR only these days.

Thanks!

Maestro2be

Thanks Frank.  I tried everything.  I tried sharing the processors(cores) and every possible solution I could think of doing it on one sound card.  I just decided to install a soundblaster card with digital outputs.  Setup ASIO4ALL on it and set MIR to use that soundcard.  My DAW is using the RME Multiface 2 now.  I then routed the SPDIF output from the soundblaster card (ASIO4ALL) to the SPDIF input on my Multiface 2.  Set both sound cards to 256 samples latency and viola, it's perfect.  I couldn't take anymore trouble shooting.  This isn't a permanent fix for me but will definitely suffice until Dietz gets me MIR Pro :).

As of right now I am able to run Kontakt inside my DAW and outside as a stand alone.  I can run MIR while running Kontakt inside or outside my DAW.  I can run Vienna Imperial as a MIR Plg-in, as a stand alone or as a VST inside my DAW.  All simultaneously at the moment.  So it appears that it may be my RME Multiface driver OR it's simply the way my DAW handles that driver.  I am not 100% sure what the exact cause is but I don't have time to troubleshoot all day long on my days off.  So, ASIO4ALL it is until MIR Pro unless someone has the magical fix to this problem.

Thanks,

Maestro2be

Could it be that MIR and a second application are trying to access the same ports of the ASIO system? (... please see p. 78 of the MIR Manual for a lengthy explanation.)

Yes!  a REAL fix :)!  That did it Dietz.  I didn't realize they were sharing the same ports.  MIR said it was using Analog Outputs 1+2 and my DAW using SDPIF 1+2 Outputs (but it called them also outputs 1+2).  I set MIR to use ADAT 1+2 and viola!  It routed it through the Hammerfall Mixer and it worked perfectly!  THIS is how it's supposed to work lol.  I was getting very upset at my RME Card lol.

Thanks so much for pointing me to that page Dietz!  That really simplified my setup again (which is always my goal)!  This issue is solved, please mark accordingly.

Maestro2be

Whew! Great to hear! :-) I have to admit that you made me scratching my head quite a bit.

Enjoy your "new" setup.

Kind regards,

Dietz this completely eliminated my similar issues at my studio machine (other one was my home studio).  Everythings working great now and I am very happy!

Maestro2be

[Y]