Tips for maximizing performance with Kompakt/DFD

[PhilAiken]

I noticed I was getting better performance with large sample libraries under certain conditions, so decided to check things out further. I have several multis set up, each with nothing but 1 instance of Receptor and a piano or Rhodes library loaded.
If Receptor boots up and loads a Kompakt patch upon boot up, it won't play as well as a fresh load. It also sometimes just simply won't load a big patch.
But....
I have a very simple multi that consists of B4 and nothing else. If I boot to that, and THEN switch to a multi with Kompakt and a big library, it loads better, and performs better as well. In this way I am able to use larger patches at the 128 buffer setting than I am otherwise. Similarly, if I want to change between large sample sets, I have better results if I load up the B4 patch in between, then switch to the other large sample patch.
Of course, this doesn't need to be B4 - but it CAN"T be another instance of Kompakt, even a blank one. I think perhaps that anything that loads samples, like SFZ doesn't work for the "palette cleansing" either.
Hope this helps someone, or gives the tech guys some leads.....

P.S.... I reccommend White Grand Jr. by Sampletekk as a comprimise mid-sized piano sample set that is VERY playable on Receptor at 128. I bought the 16 bit version. I found that you need to tweak the velocity sensitivity in Kompakt a little bit counter-clockwise to get more even results. It's downloadable and costs $80.

[DanTimis]

When I have a large sample library loaded, I always clear it before loading another one. But, I didn't know about starting Receptor with a small patch and then loading large samples. Thanks for the tip.

Do you really have to load something like B4? I think that loading a blank multi patch would be enough. There is a shortcut for that: control-click on the multi bank or patch button.

And speaking of velocity curves, what kind of MIDI controller are you using?

[PhilAiken]

When I have a large sample library loaded, I always clear it before loading another one. But, I didn't know about starting Receptor with a small patch and then loading large samples. Thanks for the tip.

Do you really have to load something like B4? I think that loading a blank multi patch would be enough. There is a shortcut for that: control-click on the multi bank or patch button.

And speaking of velocity curves, what kind of MIDI controller are you using?

I'm sure that a blank multi would do the trick. I just happened to have a multi with B4 in my 1st user created bank. So when you say "clear", I'm guessing that means you remove it within Kompakt? I guess that loading a blank (or B4) multi accomplishes the same thing. I'm trying to learn to get around without the GUI since I want to be able to just bring the rackmounted unit out for live work.
As far as controllers.....
I'm in between rigs. I just sold my Kawai MP9500 and am using my old Korg SG-1D for a bit while I decide what to get. It depends on how heavily I feel like I can lean on Receptor. Part of me wants to get another digital piano, so if worse comes to worse I can just plug it in and go. Part of me wants to just get a controller.
If I get a new D. piano, it will be either a Yamaha P90 or P250. If a controller, I'm looking forward to trying out the CME UF8, or maybe the Studiologic VMK-188. There have been many horror stories about Fatar/Studiologic reliability though.
I miss the Kawai more than I thought I would. I never loved how it sounded, but the keyboard itself is AMAZING. The wooden keys worry me for serious road use.

[DanTimis]

I have an M-Audio Pro-88. I like the price and that it has lots of knobs and sliders, but I'm not very happy with the feel of the keyboard. I'm not ready to replace it, and I don't want to pay for the synth part, just the controller. So I was just curious what you use.

[PhilAiken]

I have an M-Audio Pro-88. I like the price and that it has lots of knobs and sliders, but I'm not very happy with the feel of the keyboard. I'm not ready to replace it, and I don't want to pay for the synth part, just the controller. So I was just curious what you use.

The CME UF8 looks/sounds like it could be a steal @ $599....Craig Anderton gave a glowing review that can be found online.

[Watto]

Yeah, my local guy is raving about the UF8 - I'm definitely in line for one, assuming I can actually play piano using the Receptor...

By the way, I'll try your tips about the loading blank multi first, but I'm pretty sure I've done that anyway. I'm also thinking of editing the Old Lady down to a smaller size and seeing if that works - I love the Old Lady piano, and I'm not sure the wife will be impressed if I announce I'm buying another sampleset!

Boog.

[PhilAiken]

Yeah, my local guy is raving about the UF8 - I'm definitely in line for one, assuming I can actually play piano using the Receptor...

By the way, I'll try your tips about the loading blank multi first, but I'm pretty sure I've done that anyway. I'm also thinking of editing the Old Lady down to a smaller size and seeing if that works - I love the Old Lady piano, and I'm not sure the wife will be impressed if I announce I'm buying another sampleset!

Boog.

How do you edit it?
You can't really do that in Kompakt, can you?
Or do you own Kontakt?

[Watto]

Yeah, I'll edit it in Kontakt, and hopefully come up with something usable. Might have to try the same with Scarbee, too, I think!

[Rick@MuseResearch]

I cannnot find a difference between booting with Kompakt and not.

Test Case: (Zload in enabled)
1. Boot with Kompakt test patch.
(Linux Top wine pre-loader report): mem = 10% , CPU = 56%
2. Boot with just B4 instantiated then instantiate same Kompakt test patch.
(Linux Top wine pre-loader report): Top wine pre-loader report: mem = 10% , CPU = 56%

Also I could not hear any difference when playing the patches.

Rick

I noticed I was getting better performance with large sample libraries under certain conditions, so decided to check things out further. I have several multis set up, each with nothing but 1 instance of Receptor and a piano or Rhodes library loaded.
If Receptor boots up and loads a Kompakt patch upon boot up, it won't play as well as a fresh load. It also sometimes just simply won't load a big patch.
But....
I have a very simple multi that consists of B4 and nothing else. If I boot to that, and THEN switch to a multi with Kompakt and a big library, it loads better, and performs better as well. In this way I am able to use larger patches at the 128 buffer setting than I am otherwise. Similarly, if I want to change between large sample sets, I have better results if I load up the B4 patch in between, then switch to the other large sample patch.
Of course, this doesn't need to be B4 - but it CAN"T be another instance of Kompakt, even a blank one. I think perhaps that anything that loads samples, like SFZ doesn't work for the "palette cleansing" either.
Hope this helps someone, or gives the tech guys some leads.....

P.S.... I reccommend White Grand Jr. by Sampletekk as a comprimise mid-sized piano sample set that is VERY playable on Receptor at 128. I bought the 16 bit version. I found that you need to tweak the velocity sensitivity in Kompakt a little bit counter-clockwise to get more even results. It's downloadable and costs $80.

[PhilAiken]

I cannnot find a difference between booting with Kompakt and not.

Test Case: (Zload in enabled)
1. Boot with Kompakt test patch.
(Linux Top wine pre-loader report): mem = 10% , CPU = 56%
2. Boot with just B4 instantiated then instantiate same Kompakt test patch.
(Linux Top wine pre-loader report): Top wine pre-loader report: mem = 10% , CPU = 56%

Also I could not hear any difference when playing the patches.

Rick

I noticed I was getting better performance with large sample libraries under certain conditions, so decided to check things out further. I have several multis set up, each with nothing but 1 instance of Receptor and a piano or Rhodes library loaded.
If Receptor boots up and loads a Kompakt patch upon boot up, it won't play as well as a fresh load. It also sometimes just simply won't load a big patch.
But....
I have a very simple multi that consists of B4 and nothing else. If I boot to that, and THEN switch to a multi with Kompakt and a big library, it loads better, and performs better as well. In this way I am able to use larger patches at the 128 buffer setting than I am otherwise. Similarly, if I want to change between large sample sets, I have better results if I load up the B4 patch in between, then switch to the other large sample patch.
Of course, this doesn't need to be B4 - but it CAN"T be another instance of Kompakt, even a blank one. I think perhaps that anything that loads samples, like SFZ doesn't work for the "palette cleansing" either.
Hope this helps someone, or gives the tech guys some leads.....

P.S.... I reccommend White Grand Jr. by Sampletekk as a comprimise mid-sized piano sample set that is VERY playable on Receptor at 128. I bought the 16 bit version. I found that you need to tweak the velocity sensitivity in Kompakt a little bit counter-clockwise to get more even results. It's downloadable and costs $80.

Interesting.
It definitely seems to be true for me. In fact Kompakt often won't even load. This is using large libraries. It seems to behave the same way as it does when going from one large Kompakt patch to another without clearing.
Also....
Is there a difference in the way Receptor boots when it does the short cycle after hitting the power button 3 times, or after crashing, and the normal bootup?

I'm on 1.1 until I get the drive you sent, so no Zload yet for me.....

[DanTimis]

I'm on 1.1 until I get the drive you sent, so no Zload yet for me.....

If you are still on 1.1, then let's wait until you get 1.2 and see if you still notice the same bahavior with booting with a large samples in Kompakt.

[PhilAiken]

I'm on 1.1 until I get the drive you sent, so no Zload yet for me.....

If you are still on 1.1, then let's wait until you get 1.2 and see if you still notice the same bahavior with booting with a large samples in Kompakt.

I now have 1.2 and am not experiencing that problem.
I do still need to clear out Kompakt, either by loading a non-sample based multi, or by clearing Kompakt on the GUI edit screen, in between 2 patches with large samples.