another PT freezing problem...

  • Thread starter Thread starter madmax25
  • Start date Start date
madmax25

madmax25

New member
I'm about to put a hatchet through the (*&^* thing.
So I'm running an 002R LE 6.7 thru a Dell laptop. Decent amount of plugins. I always watch the little CPU meter and stop with the plugs at about the halfway point. Things cruise fine for a while, it doesn't feel like it's bogging down at all, then whammo! The meter pegs and the whole thing locks up.
:mad:
Any pointers?
 
Is it giving you an error message? Or just crashing/locking up?
 
sometimes it gives me the "remove some RTAS plugs" message, but most of the times it locks up the whole system so bad it can't even pop up an error message. I'll take out a bunch of plugs, to where I'm only running like 5 or 6 EQs, but it still has a weird sudden-death "too...many...plugins....aagghh" problem, even after running fine for a few minutes.
Tried trashing the prefs...next up is what, reinstall?
 
So my finger is pointing towards the stock D verb plugin...Things are ok without it, I put 1 reverb on an aux channel, and it locks up a few minutes into playback (regardless of the # of other plugins). I'll sometimes be able to very slowly remove the D Verb as it gets weird, and it'll go back to normal.
Is it possible my D verb is corrupted or something?
 
Yes it's possible.

Either reinstall Pro Tools entirely (removing ALL plugins and the programme before hand) or just reinstall D-Verb with the relevant installer from the product page on the Digidesign website.
 
Alot of times your computer is just not compatible. I tried to use pro tools on my dell 6000. Did everything every pro told me. Just buy a Mac and record like a pro...Thats what I did and I will never record with a P.C. again...For P.C. you need like 4 gigs just to get it starting to work okay. With a mac all you need is 2 gigs.
 
So things are still weird. I did a full reinstall and it seems to have gotten better on some sessions, but still just as bad on others. I even made a new session for one of the songs in case something was funky about the session--no go. Fresh reinstall, fresh session, maybe 12 tracks, no plugins at all. I throw 1 Dverb on an aux and 2 minutes later it locks up. I'm also getting a string of error messages, dunno if it's related. dae error 6088 is the most persistent, with "increase/decrease buffer" errors in close 2nd.
Never record to a laptop through a 4 pin firewire:(

As to the compatibility, I've been using this setup for 2 years now. It throws tantrums now and then, but it's worked for the most part. I've never been a mac guy, but I'm taking a recording class next year and they're running macs so I'll see how I like it...

Thanks for the help so far guys.
 
I"m having a similar issue w/ ProTools LE 5.3 and Waves Diamond Bundle 4, as soon as I load the track and apply the plugins it freezes and locks up
 
So wait - you've been running this system for 2 years with no issues? Same PT version, same hardware, same OS?


If that's the case, I would seriously consider a fresh install of XP. When I was using PCs, I had to do fresh installs every 6-8 months just to keep the damned thing running smoothly.
 
Sounds like you had something running memory resident. PT doesn't play well with others (as you probably well know). Here's a tip for a windows system:

Go Start -> Run

Type in msconfig

on the services tab, deselect all, and only reselect anything DIGI. If you must, you can reselect things having to do with your virus protection... but just make sure to turn it off before running PT.

Click OK, and restart the machine. When it comes back up, it'll give you some BS warning about how you have redone your preferences. Click "do not warn me again" (this is essential, or it'll restart and put everything back how it was).

That should remove most all of your memory resident programs... good luck.
 
How does it run without any 3rd party plug-ins in the Plug-ins folder. Just having an out-dated plug-in load at startup can cause problems... you don't need to be using it.

Rail
 
In my case it seemed as the d verb caused all the problem, regulary my pc just locked up when using d-verb. I guess d-verb may have a problem, but maybe also it has not been tested with the same hardware as I have and therefore gets the error, maybe cuz of ram or other hardware/software relationship with d-verb.

Computer specs: Protools LE 7.4, digi 002 rack, Win XP Home SP3, AMD 64 Dual Core, Mainboard; Asus M2A VM HDMI, Geforce 8600 GT, 4GB Kingston DDR2 400 mhz. 2 seagate HDs. (intern/extern)
 
Back
Top