Multi Processor Support

Discussion of Digital Performer use, optimization, tips and techniques on MacOS.

Moderator: James Steele

Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
Post Reply
swpowe
Posts: 70
Joined: Sun Sep 30, 2012 12:10 pm
Primary DAW OS: Unspecified

Multi Processor Support

Post by swpowe »

Is there a way to turn off multi-processor support in DP? I'm asking mainly to see if it improves performance with Kontakt. I currently have multi-processor support turn off inside Kontakt (running as an AU inside DP) but I'm wondering if that's the best way. I've heard you can also try to turn off multi-processor support in your DAW and then turn it on inside Kontakt but I don't know that I've ever been able to try that. Suggestions? Other Kontakt users out there found the best way to do this?
bdr
Posts: 942
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Melbourne, Australia
Contact:

Re: Multi Processor Support

Post by bdr »

I don't think that will help but I'm only going from what I remember. I believe a better option is to open as many instances of Kontakt as you have cores and they will each use a different one.

I just found this article

http://www.vi-control.net/forum/viewtop ... highlight=
Mac 2.8 8-core, 20 GB RAM, Mac 10.9, DP 8, EWQLSO Platinum Play, Mach V II, Kontakt 5, Superior Drummer, AIR, Absynth 5, Plectrum, CronoX, Albino3, RMV, cup of tea.
User avatar
MIDI Life Crisis
Posts: 26279
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Multi Processor Support

Post by MIDI Life Crisis »

Separate instances of a VI will be able to access separate cores. So don't count on the VI to multi thread. Force it to by having several instantiations of your VIs (each channel/volume slider = a separate core being accessed). More complex instruments with heavy scripting or large numbers of samples should have their own instance of the VI. Multiple small instruments can coexist in the same instance. This can avoid having to farm VIs in many large projects provided you have the RAM and the OS to multi thread sufficiently.
Last edited by MIDI Life Crisis on Wed Feb 19, 2014 8:04 am, edited 1 time in total.
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
magicd
Posts: 1461
Joined: Sun Oct 31, 2004 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: Multi Processor Support

Post by magicd »

MIDI Life Crisis wrote:Desperate instances of a VI will be able to access separate cores. So don't count on the VI to multi thread. Force it to by having several instantiations of your VIs (each channel/volume slider = a separate core being accessed). More complex instruments with heavy scripting or large numbers of samples should have their own instance of the VI. Multiple small instruments can coexist in the same instance. This can avoid having to farm VIs in many large projects provided you have the RAM and the OS to multi thread sufficiently.

Perhaps the most succinct description I have heard. Dead accurate. Bravo!

Dave
User avatar
MIDI Life Crisis
Posts: 26279
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Multi Processor Support

Post by MIDI Life Crisis »

Thanks Dave. BTW, that should be "separate" not "desperate" although both are accurate.

Wow. I got something right. Can I beta test now?

Best,

mm
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
Post Reply