Running Slate+Ash in Kontakt 6 in DP11

[Chris T]

Not sure if this is a DP, OS or Kontakt issue, so I'm posting here also:

I've recently started using Slate+Ash's Choreograph on a new film, and am blown away by its scope and power. However I've been having major problems with program stability.

I'm running Choreograph in Kontakt 6.7.1 (latest), as a VI within DP11.21. Running on a 2013 MAC Trashcan (2.7 GHz 12-Core Intel Xeon E5) with 127GB of RAM, running OS Mojave (10.14.6).

I don't have that many issues with other VIs (e.g. Spectrasonics, Rob Pappen, etc), or other libraries hosted by Kontakt. However when I try playing Choreograph sounds - whether they be your presets or some I've created out of my own audio, it often works, then soon gives me pops/crackles, and very often, DP crashes. It seems to happen when I have more instruments loaded (e.g. several loaded instruments will be more problematic than if it's just a single instrument). Also it tends to often happen when responding to MIDI CC's or the internal LFOs etc.

Does anyone have advice? Is it just a "not enough processing juice" on my system issue (and/or my old OS?), or is there a setting in Kontakt I could alter to give me more bandwidth/stability without compromising latency/convenience?

I'm not maxing out computer RAM. Currently K6 is set at Multiprocesor support = 12 cores. See screenshot. Kontakt memory server = OFF. PReload bugger size = 60kb

Many thanks for your help.

[mikehalloran]

I would update DP to 11.22.

Don't know enough about your setup to determine of there's an overload.

Multiple VIs in one instance of Kontakt will utilize one core. If you run each VI in its own instance, the OS will allocate resources among the cores.

In 2017, there were tests being done between the 12 core MP 5.1, 12 core MP 6.1 and the new iMac Pro 10 core. Each had 32GB RAM. Though these were done running Logic, the comparisons give a clue. The project had 150 instances of VIs, each with a reverb plug and a convo reverb.

On the 5.1, it was choking at 150 tracks. The 6.1 was having issues at 300 tracks but it was better than the 5.1 at 150. The iMP handled 1,000 without breaking a sweat.

If you still have the original AHCI SSD, a "slow" NVMe 3 x4 SSD like the Crucial P2 will triple your RW speed for around $160 (2TB) including pin-out adapter and recommended heat sink. Takes under 5 minutes to install not counting data transfer in a 6.1. You'll need to make a Mojave USB installer. Because of its 2 Lane bus, there's no speed increase gained by using a faster SSD but those are available up to 4TB.

[Chris T]

Thanks Mike

I know my MacPro is getting quite old. I'm holding off until the new M1 Mac Pro is released though before doing any more Frankensteining - especially since I'm mid-project right now.


I tried increasing buffer size from 512 to 1024 but still have crashing problems. My sample rate is 48k (like my session). It seems like I'm only able to change these instandalone anyway - when used as a plugin you're not able to make these adjustments anyway so it does it even have an effect?



I have noticed slightly smoother running when I turned "Multiprocessor support" to OFF in K6 (since my DAW, DP11, handles MP support I believe). Still having crash issues though with this software though, especilly when triggering one or more CC in real time.



(I'm still on K6 since Mojave I understand won't run K7?) Any other K6 stability tips out there?



Thanks

[bdr]

I feel like it's the library. I have some Slate+Ash stuff also (and agreed, so deep, creative and awesome!) but I couldn't do a thing on my old MacPro (basically the same as yours). I got a MacStudio 6 months ago, and no problems at all.

[Chris T]

Thanks BDR

Yes it's the library. Their tech guy emailed me back and said that they don't recommend Xeon processors for their software. I'm glad it runs smooth on the Mac Studio. Not sure how long I can hold out on my old machine, but don't want to blow $ on the Mac Studio if the new Mac Pro is released later this year. Tough one!...

I was wondering whether it's worth trying to run it on my M1 Macbook Pro via VEPro / ethernet link. I.e. Giving Slate+Ash their own dedicated machine! Any thoughts in that regard?....

[HCMarkus]

https://www.costco.com/mac-studio---app ... 48078.html

$600 off 64GB Studio Ultra...

[James Steele]

I saw that. I already have an M1 Max Mac Studio and it got me thinking! They have a 1TB internal drive though.

[Chris T]

Thanks HCMarkus.

This is the 64GB Unified Memory model. My 2013 trashcan has (and needs) 128GB RAM for my large template.

I know that they're not equivalent metrics, so any idea if this MAC Studio (with 64 Unified Memory) has as much memory capacity as the 128GB of trad. RAM on my Mac Pro?


Thx