Post Top Ad

jeudi 26 février 2015

Dreaded Pro Tools CPU Overload -6101

Pro Tools 10 on Mountain Lion.



I am getting this error now, when attempting to record 4 tracks of audio using Pro Tool aggregate device. The two devices aggregated are a Presonus AudioBox 22VSL and an ElevenRack. I have specified that the aggregate device use the AudioBox clock as master.



I have followed all the recommended steps I know of - disable wifi (no network interaction during recording); disable spotlight using a terminal command (verified no spotlight processes are running); eliminated all non-essential background processes; disabled Time Machine; made sure that both the audiobox and the 11r are connected via usb on the back of the mac mini.



I can replicate the error pretty easily - simply arm 4 tracks, in this case, i'm simply recording the background noise from both units - set it to record. I'm not POSITIVE about this yet, but it seems like the longest amount of time i can record *might* be about 10 minutes and then the error appears.



I tried to see, using activity monitor, if a particular task is spiking CPU when PT bombs, but nothing is standing out.



This is a quad-core i7 Mac Mini with 16GB RAM and a solid state drive, partitioned in half, one side for OS, the other for sessions. YES, i am aware of the typical recommendation that one use separate physical drives and can go that route if necessary by installing a second SSD, however I'd like to rule out any possible compatibility issues in using the AudioBox and the 11Rack. I would think the internal SSD would be able to handle 4 simultaneous tracks of audio, and has certainly been able to play back much more than that over the past year. I have been recording one or two tracks at once successfully for MONTHS - MANY MONTHS - and have never once seen this error unless i rapidly stopped/started the transport by clicking too fast or something.



In the aggregate device dialog box, i noticed that the AudioBox is set for 44.1 and indicates that it is 24bit integer, while the 11R shows 44.1 *32bit integer*. These are just displayed values, not form fields that allow change.



SHORT OF any recommendation to get a second drive specifically for sessions, what other things can I check? Is there another utility i can run that might tell me what's going on, more specifically, when Pro Tools throws the error?



I can provide additional system/software information as necessary.



Thanks!




Aucun commentaire:

Enregistrer un commentaire

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

Libellés

Libellés

Libellés