Hi
Pro Tools system has started to act up over the last few months. . . not sure what to attribute it to. Close to unusable right now, with multiple problems per hour.
Symptoms are:
System Info:
Done all the usual, trash prefs, volumes, digi database files, did a clean OSX and ProTools install awhile ago, etc. . .
Repair permissions finds a bunch of trouble, says it Repairs, but every time you run repair perms, it is the same long list of files. . . not sure what to make of this.
Drive Genius seems to think a bunch of preference files are corrupted. . . not sure what to make of this either and I don't want to blow things up. . . it feels like a false positive.
Ran Cocktail on System
Used System for a few hours and experienced multiple loop freezes and app crashes with dumps.
Rember Memory test done - showed no problems, but it only checks unused RAM so not a great test. . .
Digitest - no problems.
Is my next move to uninstall ProTools. . . reinstall OS X 10.7.x (I had OS X 10.7.5 installed, but I just noticed compatibility is only up to 10.7.4), and reinstall ProTools 10.3.x? and if so are all my plugins and Virtual Instruments still going to work? or are there still a few more steps before that? (I am rusty at this, and I have not seen a comprehensive document with the step-by-steps).
I need to get stable, hopefully without a fresh install of everything. . . which, with all plugins, virtual instrument, and libraries, takes about 30 hours + of my time. . . really hoping to avoid that colossal waste of time.
Any suggestions on best next steps, or pointer to comprehensive info, would be appreciated. . .
Pro Tools system has started to act up over the last few months. . . not sure what to attribute it to. Close to unusable right now, with multiple problems per hour.
Symptoms are:
- Randomly goes into a loop for about 5 second, while recording or playing back, and then display an error - 9128 (running out of CPU power), but CPU is basically at 5% or less.
- Random error - 9162
- ProTools Crash with Dump/Log. . . sometimes in the middle of using ProTools, or when exiting ProTools. Restart always required because a restart of ProTools will result in a total freeze up.
- Beachball forever, often when editing with Elastic time.
- Playback just stops working. . . press Play and light goes green, but will not roll.
- Just had some very loud noise show up on a bunch of tracks that previously played fine. Did a recalc of waveforms and it showed that the waveform was totally spiked across about 6 different tracks. . . .audio was fine minutes earlier, as it was days ago.
System Info:
- ProTools HD 10.3.8
- HD 3 PCI-e with 2 x 192i/o + ADAT bridge (to 02R for cue mixes)
- OS X 10.7.5
- Mac Pro 2.66 (Quad Core Original) with SSD system disk (OWC), 8GB RAM, sessions on separate drive on internal sled.http://ift.tt/1hz8DXu
Done all the usual, trash prefs, volumes, digi database files, did a clean OSX and ProTools install awhile ago, etc. . .
Repair permissions finds a bunch of trouble, says it Repairs, but every time you run repair perms, it is the same long list of files. . . not sure what to make of this.
Drive Genius seems to think a bunch of preference files are corrupted. . . not sure what to make of this either and I don't want to blow things up. . . it feels like a false positive.
Ran Cocktail on System
Used System for a few hours and experienced multiple loop freezes and app crashes with dumps.
Rember Memory test done - showed no problems, but it only checks unused RAM so not a great test. . .
Digitest - no problems.
Is my next move to uninstall ProTools. . . reinstall OS X 10.7.x (I had OS X 10.7.5 installed, but I just noticed compatibility is only up to 10.7.4), and reinstall ProTools 10.3.x? and if so are all my plugins and Virtual Instruments still going to work? or are there still a few more steps before that? (I am rusty at this, and I have not seen a comprehensive document with the step-by-steps).
I need to get stable, hopefully without a fresh install of everything. . . which, with all plugins, virtual instrument, and libraries, takes about 30 hours + of my time. . . really hoping to avoid that colossal waste of time.
Any suggestions on best next steps, or pointer to comprehensive info, would be appreciated. . .
Aucun commentaire:
Enregistrer un commentaire