ioplord.blogg.se

You may also want to check the Send Effects as well.īelow: Editing FX for an instrument.

You should see both the group effects (“Group Insert FX”) and then the Insert Effects on the instrument level underneath. If you’re sure you don’t need certain FX in your instrument, open it up with the wrench icon, then go to the Group Editor, select “Edit All Groups” and scroll down. Whereas Instrument effects have one instance per patch, Group FX can rapidly multiply an instrument with 200 groups and a simple lowpass filter in each is actually running 200 SEPARATE filter instances! These things can quickly eat up CPU, particularly at a “group” level. Group & Instrument Effects: Kontakt comes replete with a variety of useful effects, ranging from reverbs and EQs to new additions like the Transient Master and Feedback Compressor. Generic Warning: When editing any of your Kontakt instruments, be sure to save your edited versions as NEW copies so you can always return to or restore the original library versions! However, there are other factors that can eat up CPU as well. You already know that tweaking disk streaming, audio interface buffer length, and multicore options can help improve performance. You may recall from our previous guide that Kontakt can eat up a lot of CPU with high polyphony and disk streaming (DFD). Welcome to Part 3 of our Kontakt Workflow series! This post will cover additional ways you can optimize CPU and RAM usage within Kontakt, as well as features such as RAM Purge, batch resaving and NCW compression.