If you get stuck or need help to complete any of the steps listed above, feel free to contact our Support Center.
SWAM ENGINE 토렌 UPGRADE
To complete the checkout and purchase one of the options listed, click on the UPGRADE button next to it. There, you’ll see the options available for you.Īll options and prices are automatically calculated according to the products you already purchased. After logging in to your account, navigate to the tab “Only for you”. The portal shows the products you already own and the available products. Upgrades and bundle completions can be done automatically from your account in our Customer Portal.
However it’s not too late! We offer convenient upgrade prices to our loyal customers to complete any bundle: Bundles completionīundle prices are reserved for ALL-AT-ONCE purchases only. If you are a proud owner of any of Solo Woodwinds v2 (Saxophones, Clarinets, Flutes and Double Reeds) or Solo Strings v2 (Violin, Viola, Cello and Double Bass), you can upgrade to the v3 for a discounted price. And this again (a wild guess of mine) might be an issue of the VST3 vs VST2 specification.Īnyway first step should be to measure the load of each single CPU during the performance.Solo Woodwinds and Solo Strings v3 upgrade for v2 owners That might be a shortcoming of Kontakt itself, but it also might be a shortcoming of the VST host not assigning multiple CPUs to a single track. OTOH, I really don't understand why a single Kontakt instance with multiple libraries should necessarily perform worse than multiple instances with the same libraries loaded one by one.Īs discussed that might be an issue of a single instance not using multiple CPUs. (As they did with SWAM which is a lot less Sample-driven and more physical modeling than the Kontakt based instruments.) But I feel that in times of ever increasing CPU resources, it is very viable to base such an instrument on a solid base such as Kontakt instead of implementing everything from scratch. I see that libraries using extremely versatile / complex scripting might bring up Kontakt's CPU hunger decently, especially, as obviously scripts of any kind are less efficient than native programming.
SWAM ENGINE 토렌 64 BIT
If the OP wants to use 32 Bit Kontakt, he can just d/l same from NI.īTW3.: If he uses a 64 Bit host, it is not granted that it can run 32 Bit VSTs "out of the box". So using the 32 Bit Kontakt should make things greatly worse.īTW2.: AFAIK, there is no 32 bit / 64 Bit version of Kontakt libraries. (I suppose by "kill my CPU" the OP did not claim that his box only has one, nor did he say how he did a measurement.)īTW.: especially Kontakt should benefit form running it as 64 Bit, as it uses a huge amount of memory to hold the samples, and this can be organized a lot better with the 64 bit instruction set. That could be the case if Kontakt only uses a single CPU per instance (would be silly but possible).īut there should be means to see the used CPU performance per CPU. It is more efficient and works better when you assign each instrument to its own window.īy "Window" you mean "instance of the Kontakt VSTi" ?
0 kommentar(er)
