String Library problem

[Robert Sands]

Gravity Jim - Okay, I turned off the Memory Server. Now about the Preload Buffer - it's set to 60.00 kb. What should I try?

Also - you mentioned the audio buffer and sample rate. Is that in Kontakt? Where is it and what should I set it to?

Thanks for the tips. Thank you all. Maybe we're getting somewhere finally.

[Robert Sands]

Gravity Jim. Wow! Turning the Memory Server off really did wonders. My strings are finally playing nice. I just did a 3 string part little piece - 8th notes at a fast tempo and it actually didn't freak out. Played it back perfectly. Unreal! Please coach me on those other things you told me to do. See my previous post.

[dix]

Also - you mentioned the audio buffer and sample rate. Is that in Kontakt? Where is it and what should I set it to?

He means in DP if your composing and mixing (as opposed to performing live) I'm sure.

[Robert Sands]

Thanks dix. Got it.

[Gravity Jim]

No, actually, there are buffer settings just for Kontakt, inside the setting area. Check those, too, and experiment for what runs best on your machine.

That Memory Server was a pre-64-bit way of dealing with voice loading, etc., and it conflicts mightily with DP's own memory handling, so leaving it on causes a bunch of non-specific problems. Glad it worked! I've been tweaking Kontakt for so long I almost forgot those settings were there until I saw your post!

[hamburski]

Wow, someone directed me to this post after I posted elsewhere on the forum about this same issue - same problem, but with Spitfire sample libraries - and disabling the memory server seems to be doing the trick for me as well, so thanks!!

[jloeb]

That Memory Server was a pre-64-bit way of dealing with voice loading, etc., and it conflicts mightily with DP's own memory handling, so leaving it on causes a bunch of non-specific problems. Glad it worked! I've been tweaking Kontakt for so long I almost forgot those settings were there until I saw your post!

Gah. Is this universally true? Memory Server is still loved and left on here for reasons of memory persistence, not because it breaks the 4Gb limit which vanished with 64bit as you pointed out. It's just great never to have to wait for any load time when working on the same project/s for an extended period b/c all your kontakt samples just stay in memory when you close a session. Yah I have all SSD's etc, big sessions still benefit.
How does KMS conflict with DP's memory handling? Is this on MOTU's radar and can it be remedied?

[Gravity Jim]

I don't know specific programming style reasons why it doesn't work well under a 64-bit DAW, but if you are running in 64, then Memory Server is sequestering a chunk of RAM that would be better opened up to the DAW. So "off" is best.

I'm pretty sure I learned that here. Try searching on "Memory Server" to see what bobs up.

As you can see from Robert Sands' results, it's totally true.