Forum Jump
And I'm not even doing anything! It's jumping from 35% to 75% within fractions of a second, and it peaks at 100% every couple minutes for a brief moment. Once, again this is when the program (GS3) is sitting idle. The ram is sitting comfortably at 4%.
I have but five instruments loaded, each with Gigapulse, on my Xeon 3.06gHz BEAST with 2gb ram.
Is gigapulse THAT taxing on the cpu?
|
|
|
|
|
|
Yes, Gigapulse is a CPU hog, especially if you have more than one of them loaded.
I also have cpu spikes sometimes but only when rewired to my sequencer.
I guess Tascam could optimize the Gs3 engine ( including Gigapulse ), but I think they will try to fix the major bugs at first, which is good.
best regards
Przemyslaw K.
|
|
|
|
|
|
Yes, 5 gigapulses seems to be a lot -- the Groups in GS3 are useful to combine paths and use fewer gigapulses. Do you really need 5 different reverb environments?
|
|
|
|
|
|
Have you updated Gigastudio with the latest patch? I at first had the wild CPU meter fluttering that you describe, but after updating with version 3.01 it was fixed.
5 instances of Gigapulse! Wow. I feel comfortable with a max. of about three, but my comp is much less of a firebreather than yours. GP is by nature a 'real time' number cruncher, so as you send streams of data to be processed when you play your samples, you will see CPU usage change dramatically.
- David
|
|
|
|
|
|
They have got the impulses pretty efficient at this point. For the most part unless you use an impulse with room longer than 3 seconds decay time, you are not even getting into the tail modeling so its all full time DSP processing most of the time. Similar quality impulses have been known to use up a whole computer with just one instance(and nothing else running) in the past.
A good 2.8Ghz machine can usually handle a max of 4 "surround" instances at this point. More with stereo.
I can't wait to see what happens in the future when we get 64 bit and multiple processors going.
Cheers
Dave
|
|
|
|
|
|
Try blocking as many of your VST fx that you are unlikely to use (i.e. remove them from your list of available plug-ins).
I've found each plug-in, even if it is not being used, has a significant memory impact.
I've even blocked the native GS3 effects, since I never use them.
|
|
|
|
|
|
"I've found each plug-in, even if it is not being used, has a significant memory impact.
I've even blocked the native GS3 effects, since I never use them."
Thank you! Thats a new one for me. That will help alot of people.
Dave
|
|
|
|
|
|
David Govett wrote:"I've found each plug-in, even if it is not being used, has a significant memory impact.
I've even blocked the native GS3 effects, since I never use them."
Thank you! Thats a new one for me. That will help alot of people.
Dave Strange. This almost sounds like a bug to me. It seems as though simply being available for use shouldn't require a huge amount of memory. David, maybe you should ask the engineers about this?
|
|
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.