Another Pro Tools question - PT performance test?

Hi all -

I've been using PT LE with a Digi001 for quite a while now, and running into a lot of issues with CPU performance. Whenever I get more than about 8-10 tracks up, I start getting the dreaded "increase buffer size" error. I'm using DVerb and the BombFactory MultiTap delay in parallel on AUX sends. Typically I'm using EQ and compression plugins on the other tracks.

I've tried all the optimizations as recommended by Digidesign to no avail.

I've seen a PT performance test but I don't know what that entails. Can anyone give me a link to what this is?

I'm running a windows PC with a 2 Gig P4, 512MB of DDR, and 2 120GB hard drives (one for programs, and one for data). The machine is networked, but there are no other apps running on the computer. Running Windows XP SP 1, and version 6.2 of PT IIRC.

I'd like to benchmark this box to find out where the bottleneck is, and hopefully find some way to improve its performance without having to totally rebuild it or buy a Mac. Any suggestions would be greatly appreciated.

I've been able to work around it by premixing and bouncing, or by applying the effects directly to the files, but this makes it more difficult to tweak the mixes and I'd really rather not have to do this. All the stuff I've read says my box should be able to do better than this, so I'm baffled.

 

I thought after I posted this that I should mention that.

Yeah, I track at 128, and increase it to 256 or 512 to mix. Above 512 I start getting another error.

 

Yeah, I think I have a bottleneck somewhere, either some application that's choking it up or something about my motherboard is not quite right. Looking over on the DuC guys are getting 32 tracks and tons of AUX tracks with the same basic setup as me.

 

I know! That's what is KILLING me! It SHOULD work!

I don't have anything else on the machine. No virus protection, no other apps other than iTunes, which I have tried leaving running or killing off with the same results.

What size partitions are you running?

 

Nah, muting channels doesn't really do much. The main issue is the plugins. You have to start using the destructive plugs on the files themselves to free up resources which forces me to commit to things earlier than I want to. Yeah, I know, the original track is still there but it's a pain in the butt to tweak a mix this way.

 

If you're interested, here's the infamous "DaveC" benchmark:

1) Open new PT session
2) Create a new mono audio track
3) Add PT stock effects Compressor, 4B-EQ, Slap delay, medium delay, long delay.
4) Open the System Usage window under the Windows menu item to see the CPU utilization.
5) With your mouse select the newly created track from step 2 above.
6) Press Alt-Shift-D (to duplicate the track)
7) Record enable the track.
8) Repeat step 6 until your CPU goes into the red.
9) If your CPU is in the RED delete the last track created. IF it's still in the red, delete another track until the CPU is back in the green. Click on the CPU meter after every deletion to reset the meter (see warning below). Going into the RED means your getting a -9128 message from PT.
10) Hit RECORD, and record for 60 sec. (it doesn't matter what you record as the file still get's created). If your CPU goes into the RED then delete a track and repeat step 10 until you can record 60 secs. without peaking.

I've applied a few more recommended tweaks for XP and managed to get it to handle 20-21 tracks, but that's about the best I think I can get.

 

Yeah.

 

Today's update:

I went and picked up 1GB of PC2700 memory. No difference. There's no appreciable gain in performance after doing this.

Now I'm truly baffled.