Kontakt2 behaving oddly on Receptor

[swanzoid]

Hi, just starting to diagnose a problem I'm having here and wanted to see if anyone else has encountered this. I have Kontakt v2.0.0.002 installed on my Receptor 1.5 and find two recurring problems:

(1) On occasion clicking on certain areas of Kontakt2 causes my Receptor to spontaneously reboot (happens about once a day);

(2) Most annoyingly, the virtual outputs on my one instance of Kontakt2 don't seem to reach the channels on the Receptor mixer. Specifically, I have Kontakt2 installed on Receptor channel 1, with Receptor channels 2-6 "mapped" to the outputs of the channel 1 Kontakt2 instance. Only channel 1 seems to receive any signal on the Receptor, most of the time anyway. I found that if I remove and reinstall the plugin then the behaviour can change -- sometimes it actually starts working for a while and I get signal on the mapped channels.

I'm inclined to think this is principally an NI problem, not a Muse problem, but if anyone has any experience with this I'd love to hear from you.

[rubaiyat_23]

swanzoid and I had an opportunity to examine this yesterday (each of us has a unit, with 1.5b loaded)...

To follow up on this, the problem is tied specifically to Receptor startup:

- one-shot drum samples are gated
- looped samples do not load correctly
- plug-in outputs do not route to the respective Receptor channels, even though they show up in the individual output channels within Kontakt

However, if one loads a blank Receptor mixer multi before shutdown, re-boots the machine with the blank multi loaded, and then loads the correct Receptor mixer multi (or snapshot) after the machine has already booted, everything is fine.

That is, something about the order in which Receptor multi, Receptor singles, plug-in multis, etc. are instanciated screws up when using a multi-output plug-in across several mixer channels, unless you boot up "empty", so to speak.

FWIW, all active mixer channels were saved as individual Receptor singles.

[DanTimis]

I doubt that this has to do with start-up. If you have zload enabled, the plug-in will be kept instantiated in the background and restarting would clear the plug-in.

Could you try one more test? Disable z-load. Load a blank multi patch, load the multi. Is everything correct?

[swanzoid]

Thanks for the feedback, Dan. We found that the same problem occurs regardless of the z-load setting. The workaround we're doing for now is loading a blank multi prior to shutdown, shutting down, and then after rebooting we reload the multi w/ Kontakt2. Since we've got two separate Receptors exhibiting the same exact problem, I would think this should be fairly easy to replicate on your end as well.

[rubaiyat_23]

P.S. The Kontakt single is essentially the 06 - Acoustic Drums: GM Drumkit, opened into a blank Kontakt multi with 6 stereo outs (kick, snare, toms, fx/loops/percussion, hihats, cymbals), so we are certain that it's not caused by errant samples.

I have the same problem with a PCP-80 Yamaha Electric Grand multi, at startup, also regardless of z-load setting. Both Muses had problem before and after Receptor 1.5b software update installation.