totla bundle cpu??
-
- KVRist
- 66 posts since 17 May, 2004 from south fla
im really looking into the total bundle (mir/st/ss) how much of a cpu hog is this? what kind of pc does it take to run this well with lets say 5 instances. oh and by the way that installing post is kinda scaring me to....thanx for any help..... 
hey bud! whats yur problem?
-
- KVRist
- 267 posts since 15 Apr, 2002 from Wiltshire, UK
IK plug-ins are generally pretty CPU friendly, obviously the more advanced plug-ins (CSR/Amplitube 2) do take a CPU hit, but the workstation stuff is really efficient. I'd actually concentrate on RAM considerations over CPU when it comes to the workstations. As Sampletank 2 supports SonikSynth2 file format, I personally prefer to run that library from within the ST engine, Miroslav and Studiophonik are following suite - allowing you to consolidate all your IK/SR libraries under one roof.
I have to say, i've never experienced a single installation/performance issue with any IK/SR product - covering pretty much everything back to Sampletank 1/Sonic Synth 1.
I have to say, i've never experienced a single installation/performance issue with any IK/SR product - covering pretty much everything back to Sampletank 1/Sonic Synth 1.
-
- KVRAF
- 6272 posts since 25 Mar, 2004
The Total Bundle doesn't run as one instrument. It is 3 separate programs (Miro, ST2 and SS2) bundled into one low priced package for purchase.JAKEYBUBBA wrote:im really looking into the total bundle (mir/st/ss) how much of a cpu hog is this? what kind of pc does it take to run this well with lets say 5 instances. oh and by the way that installing post is kinda scaring me to....thanx for any help.....
Now, EACH program is multi-timbral and allows you to run up to 16 different instrument patches on different MIDI channels in your host before requiring an additional instance. You could do an entire project using only one instance of, say, Sampletank 2, with FX.
The CPU for each depends on the files you load into them. The interface tells you how big each individual patch is, so, for example, you can see that the synth lead you're using is only 2mb, while the Steinway patch is 60 mb, etc.
I have found that the biggest determiner of CPU use is the FX that you use for each patch. The sample data, as I understand it, is relatively static, requiring a moderate amount of processing power. But loading multiple FX requires your box to continually process the math to produce the effect. That tends to add up (for ANY effect program, not just these).
I would have to say that, overall, the latest versions of all these programs are very efficient.
Hope this helps.
-B
Berfab
So many plugins, so little time...
So many plugins, so little time...
