Our Multi Articulation patches allow you to load multiple articulations. The more samples and the longer the samples in a patch, the higher the memory usage will be. The more patches, the more memory.Ģ.The samples within the patch.
Error loading action strings in kontakt Patch#
Each patch reserves some memory for itself and its script. The simple rule is: The more you have, the better.ġ.The patches themselves with their scripting. System Memory (RAM) is the most important factor with sample libraries. Extensive use of Tempo-synced patches, as well as legato patches, requires a quad core CPU. In general, any mid to high-end CPU from about 2010 onwards should be able to run all our collections well. Recommended SpecsĪny dual or quad core CPU (Intel i5 or higher) will be able to run a good number of demanding legato patches without issues. Lots of demanding legato patches with multiple microphone positions are not recommended for low-end CPUs. Most regular patches will run even on low-end Intel i3 or similar CPUs.
![error loading action strings in kontakt error loading action strings in kontakt](https://i.ibb.co/Vj3JJCR/kontakt-beta-1.png)
Most adjustable settings are calculated on patch load and do not use resources at runtime. Our collections rely exclusively on sampling and do not use any extensive calculations. Regular non-legato articulations are very light. In general, Legato patches pose the greatest demands on CPU power. The demands on CPU vary greatly from patch to patch. CPU (Processor)Īll Orchestral Tools collections are highly CPU-optimized in their scripting.
![error loading action strings in kontakt error loading action strings in kontakt](https://i.ibb.co/XVHLpyG/Captura-de-pantalla-2020-09-16-a-las-11-33-53.png)
If you are not sure if your system will be able to handle a certain collection, do not hesitate to contact us. Please also see further information about SINEplayer's Requirements. This section applies equally to SINEplayer-powered and Kontakt-powered collections. This section gives pointers about specific resource areas of your system and what you will likely need to run Orchestral Tools collections with their full feature set. Resource use varies greatly by use case and workflow, so general system requirements are hard to give. Orchestral Tools produces world-class sampled collections that are highly adaptable and flexible.