Tweaking Kontakt 4 on Receptor

[Kevin@MuseResearch]

If the dual core option is not enabled for the Receptor is there any benefit to having a dual core CPU in the unit?

The dual core option in Receptor's setup page is really for enabling/disabling a special multicore optimization developed here at muse research. When this is disabled both cores of the processor are still in operation, but it's essentially a "free for all" which plugin uses what core. It depends on the kind of optimization that's been used by the plugin's developers.

- Kevin

[dustnic]

I experienced a little improving in performances (lower latency) with enabling the "multiproc" option.
Anyway, I have a problem.
Any option I try to change in Kontakt is set-back after receptor restarts. Seems like Kontakt is not able to save the options I change.

Can you please help me?

[kungfudrummer]

That's a function of how the Receptor handles the plug-in instruments, including the instrument sets you create within the plugin. I'm still not quite sure how it works (Kevin, can you explain this?), but it helps if you save the patches with the Receptor's SAVE function. Notice that you can save Multi's as well as Single's. Single's are for saving individual channel strips, and Multi's are for the whole set of patches.

If you save from within the plug-in (and by the way, I use Kontakt 4 also, so I'm specifically talking about that, but I assume it's the same for the other plugins too, although Kontakt has some quirks all its own, hence this thread), without saving from Receptor's SAVE function, the Receptor tends to ignore the change.

Usually, I save within the plug-in first, then save with RECEPTOR Save, then I tap the button three times and restart. That usually helps the change to hold.

Let me know if that works. And again, Kevin or anyone else with more knowledge and insight than myself, your guidance is appreciated!

m