Post Top Ad

samedi 27 décembre 2014

SampleTank 3 pegs my CPU meter

I'm running PT 11.3 on an i7 PC with 8 Gig of RAM

After optimizing the PC per Avid's instructions, the system runs smoothly.

I can have a dozen or more Wav files loaded and running, and the cpu meter runs right around 4% peaking not more than 10%.

now about Midi files:

First, I used XPand!2 to provide instruments for 8 midi tracks (two installs - 4 instruments in each install) Still not much change in my cpu meter, several threads show activity, but just barely moving off the left edge into view.

Total usage still not much more than 4% no peaks over 10%.

Next, I used Sampletank 3 to provide instrument sounds for the same Midi tracks (Once again two instances of the plugin - 4 instruments in each case).

I watched the cpu meter as I invoked each instrument, and I noticed that the cpu meter jumped approximately 7% higher on each instrument I added - finally topping out at about 60%. If I mute an instrument, the cpu load does not drop. if the song is not playing, the cpu meter does not drop. It's as if Sampletank 3 does not dynamically allocate cpu resources. Now as I watch the cpu meter, periodically a "flare" of yellow cpu activity data seems to break away from the main yellow 60% bar line and move toward the 100% mark.

If the outlier "flare" hits the 100% mark during playback, Pro Tools will "error out" and shut down.

I'm thinking this is all Sampletank 3's problem - their program is a resource hog.

I could bounce their instruments to wav files (I do that eventually anyway) but it sure makes it hard to try various instruments "on the fly".

I'm curious if others in the PT 11 forum have insight into this situation ...

Thanks




Aucun commentaire:

Enregistrer un commentaire

We’ll never share your email address with a third-party.

Libellés

Libellés

Libellés