Big ProTools problems

[Mike Caffrey]

I'm running 7.1 (HD2) on a dual processor G5 with 2GB of RAM. I've got a session with about 30 tracks and any time I hit two keys in a row with in a second or two of each other, I get the spinning beach ball. It goes away after 3-5 minutes. This came on all of a sudden. No problems whatsoever yesterday and there was no shut down or restart.

Here's an example - I start recording and decide not to keep what's being recorded, so I hit "command ." to stop and delete and I get the hang/crash. If I hit the space bar and undo it's fine.

Or, if I hit play and then realize I need to stop it and I hit the spacebar again quickly, I get the hang.

Any suggestions?

[gsilbers]

session in an internal drive or external?

always hapens or only when too many tracks/. +24?


what sample rate?


sometimes it takes the computer some effort to stream all those files through firewire or sometmimes intenral drives.
try loadind a session on your main HD and see if it still having those prblems.

and


get HD3



also do what mac suport always tells u no matter what the problem is; run disk utility repair disk permisions, and repair disks. restart.

try different buffer size in pt

[Geert van den Berg]

Are you running the latest cs update? 7.1cs7 I believe is the latest now.

Have you tried switching to another hardware engine which uses less TDM chips? It might help.

[Jamz]

Are you using a lot of RTAS plug-ins?
Check your CPU and system uasge.

All else fails create a new session and import the tracks in one at a time. Then see if and when the problems begins in the new session. There's always a chance something became corrupted. This process could help. At least you might find out at what point or which track the problem begins.

[Joseph Hanna]

I have three systems.....two at work and one at home. They are almost identical HD 2 systems (Mac G5/ 2.3/PT 7.1cs7) with the exception of the external drives.


The external drives at work are Maxtor D-2's. I never experience drive access problems. No spinning wheel.

The drives at home are Seagates. I am constantly bogged down with drive access stuff. I configured and re-configured to no avail. Brought home a Maxor drive from work and .....no problems.

Gotta be in the drive chipset I'd guess

[Mike Caffrey]

This was zero plugins and HD2 won't struggle with under 96 tracks.

I think this was from having made 10,000 edits with beat detective and not deleting the unused regions. It must have been doing some kind of processing that invoived all of the regions when I stopped it with "command ." as opposed to the space bar. Why two hits of the space bar was a problem I don't know, but it might have been doing the same processing because it was in quick punch. When I recorded and stopped with the space bar it didn't have to automatically undo or something - it had different post processing.

Since only this session had the bloated region list, it seemed to happen overnight, although I'm not sure why I wasn't experiencing the same problem the last time I worked on it.

[C.Lambrechts]

check your setting .....


http://duc.digidesign.com/showflat.p...fpart=1#177661


energy saver settings / options / processor performance .... highest .... for example

[Jamz]

Sometimes when there are many edits....especially BD drum edits, along with several drum takes @96K...I'll copy the session to a different drive with a consolidated track of the comp'd drums.

[Rab]

Trash Digidesign Databases folder on all connected drives
Trash all Digi-related prefs:
• com.digidesign.protools.plist
• DAE Prefs
• Digisetup.OSX
• Pro Tools Preferences
Rebuild Disk Permissions

(My first guess is a corrupt Digidatabase folder.

Good luck...

[RadioMoo]

Originally Posted by Rab

Trash Digidesign Databases folder on all connected drives
Trash all Digi-related prefs:
• com.digidesign.protools.plist
• DAE Prefs
• Digisetup.OSX
• Pro Tools Preferences
Rebuild Disk Permissions

(My first guess is a corrupt Digidatabase folder.

Good luck...

• Delete caches with something like Tiger Cache Cleaner

• Run cron tasks manually with MacJanitor or something similar

• REBOOT!

[hociman]

Originally Posted by RadioMoo

Run cron tasks manually with MacJanitor or something similar

Or open up the Terminal and type the following:

sudo periodic daily weekly monthly

[3rd world order]

Originally Posted by Mike Caffrey

ThI think this was from having made 10,000 edits with beat detective and not deleting the unused regions.

sounds like time to take your edited tracks and "duplicate" em down to nice contiguous regions...

too simple?

[RadioMoo]

Also, if your drives are 90% or more full, things'll get sluggish.

[Mike Caffrey]

I guess I was not definitive enough in my last post. It was the beat detictive edits.

It may have had something to do with the automatic backup funtion, because every time I stopped recording it was doing some kind of process that involved every file. The reason I didn't expereince the problem during editing is, to state the obvious, becuase I wasn't recording.

Selecticing and removing the unused regions was all it took. 12 tracks of drums with every 8th note edited makes for a lot of regions in the region list....

[Dysanfel]

Originally Posted by Joseph Hanna

Brought home a Maxor drive from work and .....no problems.

Maxtor = Under rated. IMHO