KVR Audio

XL · Post by XL » Thu Apr 01, 2010 7:32 am

I cannot make a song with NI plug-ins only. The more important plug-ins for mixing, in particular Waves, UAD etc., are x32 only.

umd · Post by **umd** » Thu Apr 01, 2010 1:16 pm

Ok thanks for the info, I am going to run some tests here with K3.5 and K4 player and see if I can find anything.

Elfen · Post by **Elfen** » Thu Apr 01, 2010 8:40 pm

Hi, I'm getting some dispatching opcode error on "Kontakt 8outs" sometimes, but it's working after that.

But I'd really wish to use East West "Play". It shows but the GUI flash and mostly disappear after I click anything on it.

I tried all options but the only one working is the Switch to seperate GUI mode which is not usable for me

XL · Post by XL » Thu Apr 01, 2010 9:11 pm

I have switched off all settings (like Force whole GUI refresh and Sluggish GUI hack and so on) and now Kontakt 4 works correctly. But, for some reason, the Play engine x64 does not work (which worked before, at least with older jbridge versions). It crashes everytime I open the plug-in after the very first time the GUI has shown up and has been closed again. What is going on here?

standalone · Post by **standalone** » Thu Apr 01, 2010 9:23 pm

I need to use separate GUI and dirty close with PLAY.

umd · Post by **umd** » Thu Apr 01, 2010 10:45 pm

Hi.

@Elfen:
Which opcode code error are you getting? Does the "force whole gui refresh" option make any difference? Also, which VST host are you using?

@XL:
Try the "prevent main host control when the GUI window is closed" option.

The separate GUI mode is usually more compatible, although understandably not as practical.

Regarding Play, it has always needed the "dirty close" option enabled in my tests with this implementation, otherwise its auxhost will be left hanged, hogging the cpu.

Elfen · Post by **Elfen** » Thu Apr 01, 2010 11:09 pm

Hi umd, dispatcher opcode number 1 and 222222 for Kontakt8out.32 with Cubase 5.1 32 bits on W7 64 bits.

I'm trying the 1.19 demo, really wish that Play would work in that configuration, I tried everything but the Gui keep disappearing.

umd · Post by **umd** » Fri Apr 02, 2010 4:28 pm

Hi, Elfen.

Try the "dirty close" option for Kontakt.

Regarding Play, check issue nº 11 here:

http://jstuff.wordpress.com/jbridge/jbr ... eshooting/

Any difference with that?

Cheers.

XL · Post by XL » Sat Apr 17, 2010 2:14 pm

umd wrote:@XL:
Try the "prevent main host control when the GUI window is closed" option.

The separate GUI mode is usually more compatible, although understandably not as practical.

I am running KONTAKT now with separate GUI and it freezes (crashes) very often when loading or unloading big sample sets.

I have "auto-close GUI", "GUI always on top", "audioMasterGetTimeHack", "Dirty close", "Sluggish GUI hack", "Use thread safety measures in auxhost", "I am getting an opcode 19 error message" on.

There seems to be no "prevent main host control when the GUI window is closed" option in separate GUI mode?

XL

ADDED: It seems to be a KONTAKT problem since with the sample sets for the NI Kontakt player (all those "official" Kontakt sample set products), there seem to be almost no problems. And after having loaded and deleted one of those sets in Kontakt (full versino), like NI Akoustik Piano Bechstein, also the "custom" NKI files work with much less problems. Strange. But of course NI wants people to buy "official" libraries since they get license fees for them, rather than for any freely distributed NKI files.

standalone · Post by **standalone** » Sat Apr 17, 2010 3:01 pm

I can run Kontakt with everything unchecked. Doesn't it work for you this way?.

umd · Post by **umd** » Sat Apr 17, 2010 5:46 pm

Hi.

From my experience, Kontakt doesn't require the "thread safety measures" option ( In fact, that option can cause hangs with some plugins ), and runs fine with the integrated GUI mode.

Try running it only with the "audiomastergettime hack" option on, if you experience any hangs, try the "i am getting an opcode 19 error message" option.

The "prevent main host control when the GUI window is closed" is only available for the integrated GUI mode, because it's a specific workaround for that mode only.

Hope this helps.

XL · Post by XL » Sun Apr 18, 2010 8:33 am

I have tried different settings, and today it is again much worse than yesterday. I have tried with some settings (as recommended), then with everything unchecked, both with separate GUI mode and integrated GUI mode.

As soon as I click on an NKI patch, the "progress" window of Kontakt 4 opens. Unlike using Kontakt x64 in Reaper x64, the bridged version takes some time until it starts to load samples effectively. This could be a hint, but for itself it is not the problem. The problem is that after loading the samples, the "progress" window disappears and nothing happens. Hourglass, and the machine hangs. Today, out of 20 tries, I could successfully load a library in about 2 tries. I have mostly tried the "Bechstein" from Akoustik Piano.

Then again, I cannot unload a library which has been successfully loaded. Clicking on the "x" in Kontakt's patch sub-window to close the patch, and everything hangs. Looks like a problem to release the memory used by the patch, or whatever.

I have 48 GB of RAM and I am using 2 XEON X5570 CPUs with 4 cores/8 threads each. Maybe it is a multi-core issue?

umd · Post by **umd** » Sun Apr 18, 2010 8:58 am

Hi.

Which variant of Kontakt is, the 64, 16 or 8 output?

Also, when the hang occurs, how much RAM is the correspondent auxhost process using?

If want email me so we can check that more in depth with an experimental test version.

draft14 · Post by **draft14** » Mon Apr 19, 2010 3:42 pm

Don't open a window with presets Arturia Jupiter and Arturia Brass2 in Presonus Studio One x64,please fix it

umd · Post by **umd** » Mon Apr 19, 2010 10:16 pm

Hi.

You mean the preset window disappears shortly after? Any difference with the separate GUI mode?

Need testers for my x86 to x64 vst adapter