- #Native instruments action strings sustain Patch
- #Native instruments action strings sustain full
- #Native instruments action strings sustain download
The process is described in detail in the Installation Guide.
After the installation, the space used by the downloaded files can be freed. This is because the downloaded files need to be extracted.
#Native instruments action strings sustain download
The disk space required by all our collections after installation is roughly identical to their download size.ĭuring download and installation, you temporarily need to have free space twice the download size. If you intend to use a lot of microphone positions and want to use a lot of collections, 64 GB is perfect.
#Native instruments action strings sustain full
To host for example a full Berlin Strings template with all articulations we recommend 32 GB RAM. 16 GB for a medium template would be better to have headroom. To run a small to medium project with a few legato patches and some basic articulations with one or two microphone positions you should have at least 8 GB RAM. So if you use 5 positions, the samples will need 5 times as much memory compared to using a single position.Ī neat trick is to compose with one position purge all the samples when you are done, and then enable additional positions for export. Each position takes about the same amount of sample RAM. If you have little memory, try using sustain patches whenever legato is not needed.Īll our collections provide multiple microphone positions. In general Legato, patches take the most memory due to the many transition samples. Since they only need to load their script once, on systems with less RAM (less than 16 GB) they are good for saving resources. 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.
#Native instruments action strings sustain 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. 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. 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.